Welcome and how to use this board

[adunn08]

Quick orientation.

Where things go:

• Announcements: release notes and major changes. Maintainer-posted. Subscribe for notification of new versions.
• Skill requests: skills you'd like to see in the catalog. Lower bar than a full PR. Describe the gap, the audience, and the rough shape. I evaluate against the catalog roadmap and either pick it up, point at an existing skill that covers it, or invite you to PR it yourself.
• Q&A: installation, compatibility, how do I use this with X questions. Use this category specifically (not General) so questions get the answer-marking workflow and become reference for future visitors.
• General: open conversation, introductions, "I tried this and learned X." Lowest formality.
• Reference file feedback: targeted improvement requests for specific reference files inside skills. Smaller scope than a skill request, bigger scope than a typo fix (those go straight to PR).
• Show and tell: what you've built using these skills.

Response cadence:

• Q&A: usually within a few days
• Skill requests: evaluated within a week with response either way
• Show and tell: I read everything; I respond when I have something useful to add

A few things worth saying upfront.

The skills are MIT licensed. Use them however. Fork, modify, ship products with them. Attribution appreciated but not required.

The audit suite assumes the Ahrefs MCP. Other audit-suite-style integrations may show up over time as more MCPs mature.

Real workflow patterns help more than abstract critique. "Here's what didn't work for my team" is much more useful than "this is bad."