If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionseo-auditExecute the skills CLI command in your project's root directory to begin installation:
Fetches seo-audit from anthropics/knowledge-work-plugins and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate seo-audit. Access via /seo-audit in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
11.0K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
11.0K
stars
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Audit a website's SEO health, research keyword opportunities, identify content gaps, and benchmark against competitors. Produces a prioritized action plan a marketer can execute immediately.
User runs /seo-audit or asks for an SEO audit, keyword research, content gap analysis, technical SEO check, or competitor SEO comparison.
Gather the following from the user. If not provided, ask before proceeding:
URL or domain — the site to audit, or a topic/keyword if running in keyword research mode
Audit type — one of:
If not specified, default to full site audit.
Target keywords or topics (optional) — specific keywords the user is already targeting or wants to rank for
Competitors (optional) — domains or companies to compare against. If not provided and the audit type requires competitor data, use web search to identify 2-3 likely competitors based on the user's domain and keyword space.
Research keywords related to the user's domain, topic, or target keywords.
If ~~SEO tools are connected:
If ~~product analytics are connected:
If tools are not connected:
For each keyword opportunity, assess:
For each key page (homepage, top landing pages, recent blog posts), evaluate:
Identify what's missing from the user's content strategy:
Evaluate technical foundations that affect crawlability and rankings:
For each competitor, compare:
Open with a 3-5 sentence summary of overall SEO health. Highlight:
| Keyword | Est. Difficulty | Opportunity Score | Current Ranking | Intent | Recommended Content Type |
|---|
Opportunity score: high, medium, or low — based on the combination of search demand, difficulty, and relevance to the user's business.
Include 15-25 keyword opportunities, sorted by opportunity score.
| Page | Issue | Severity | Recommended Fix |
|---|
Severity levels:
For each content gap identified, provide:
| Check | Status | Details |
|---|
Status: Pass, Fail, or Warning.
| Dimension | Your Site | Competitor A | Competitor B | Winner |
|---|
Include rows for: keyword count, content depth, publishing frequency, backlink signals, technical score, SERP feature presence.
Split recommendations into two categories:
Quick Wins (do this week):
Strategic Investments (plan for this quarter):
For each action item, include:
After presenting the audit, ask:
"Would you like me to:
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
kostja94/marketing-skills
anthropics/knowledge-work-plugins
kostja94/marketing-skills
shadcn/improve
laguagu/claude-code-nextjs-skills
sickn33/antigravity-awesome-skills
Solid pick for teams standardizing on skills: seo-audit is focused, and the summary matches what you get after install.
seo-audit reduced setup friction for our internal harness; good balance of opinion and flexibility.
seo-audit is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend seo-audit for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
seo-audit has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for seo-audit matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in seo-audit — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added seo-audit from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: seo-audit is the kind of skill you can hand to a new teammate without a long onboarding doc.
seo-audit has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 68