agentleFS
ai-search-guruai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool/skills/audit-fix/SKILL.md

audit-fix

Skill432 starsChanged 12 days agoMITView on GitHub

Turns site audit findings into fixes you approve.

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never change the site, and never publish yourself: the app decides whether a page goes live, and asks the person unless an Admin allowed …

    line 41
  2. Distinctive:

    Don't fix what the audit didn't find without saying so.

    line 42
  3. Distinctive:

    Never promise rankings or citations.

    line 43

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “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

Site audit fixes

The site audit's findings, ordered by what matters most for AI answers, each turned into a fix ready to apply.

When to use

  • "Fix our site audit", "What should we fix first for AI?", "Site audit fixes."
  • To rewrite one page so AI quotes it, the Answer-first rewrite skill fits better.

What to read

  1. get_site_audit_summary: the latest audit, its date and its scores.
  2. list_site_audit_issues: the findings, with the pages each one affects.
  3. fetch_page for the pages behind the top findings: what is on them now.
  4. list_drafts and get_draft: drafts already open for those pages.

Steps

  1. Start from the latest audit. When there is none, or it is old, offer run_site_audit; the app asks the person first. A page with an audit running gets that audit back, with no new audit used. A page audited in the last 10 minutes isn't started again: ask whether to open that audit or audit it again, and only then run it again with force.
  2. Order the findings by what matters for AI answers: whether AI crawlers can reach the pages, then missing direct answers, structured data, titles and descriptions, then the rest.
  3. For each of the top findings: why it matters for AI answers, and the fix, ready to apply: the corrected markup, text or setting.
  4. When the person wants a page change kept, save it as a draft with create_draft; the app asks them first when it should. In an agent's run nobody is there to ask: always save it with its tool, and the app holds it for approval where the agent's mode needs it.
  5. Settings outside the page, such as the robots file or the CMS, are the person's to change: write the change for them.

Output

  1. A table: Finding, Pages, Why it matters for AI, Fix, Effort.
  2. The fixes, ready to paste.

Don't

  • Never change the site, and never publish yourself: the app decides whether a page goes live, and asks the person unless an Admin allowed this agent to go live on its own.
  • Don't fix what the audit didn't find without saying so.
  • Never promise rankings or citations.

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.