agentleFS
chajahmedchajahmed/claude-seo-agent/.claude/skills/seo-status/SKILL.md

seo-status

Skill0 starsChanged 4 months agoMITView on GitHub

Show the current SEO status — rankings trend, index coverage, open issues, opportunities. Use when the user asks "how is my SEO doing", "seo status", or wants a progress report.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run npm run report from the repo root and read its output.

    line 10

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

SEO Status

Give the user a concise status report from the collected data.

  1. Run npm run report from the repo root and read its output.
  2. Optionally query data/seo.db (SQLite) for extras:
    • SELECT * FROM site_totals ORDER BY date DESC LIMIT 28 — clicks/impressions/position trend
    • SELECT severity, COUNT(*) FROM issues WHERE status='open' GROUP BY 1 — open issues
    • SELECT coverage_state, COUNT(*) FROM index_status WHERE date=(SELECT MAX(date) FROM index_status) GROUP BY 1 — index coverage
  3. Summarize: traffic direction vs. last period, indexation health, top opportunity keywords (position 4–25 with impressions), open issue counts, and the single most impactful next action.
  4. Point the user to the dashboard for graphs: npm run dashboard → http://localhost:3005.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.