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

audit

Skill432 starsChanged 11 days agoMITView on GitHub

Reads the latest Site Audit result or runs one, then turns its issues into fixes and code.

193 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use delight, teach-impeccable and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • HK-hubSkill

    delight

    Add moments of joy, personality, and unexpected touches that make interfaces memorable and enjoyable to use. Elevates functional to delightful. Use when the user asks to add polish, personality, animations, micro-interactions, delight, or make an interface feel fun or memorable.

    Also in 32 projects that use this

  • HK-hubSkill

    teach-impeccable

    One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.

    Also in 19 projects that use this

  • zwy123zwySkill

    normalize

    将用户随意输入的提示词规范化为结构清晰、便于大模型执行的标准化提示词。适用于需要整理、统一提示词格式时调用。

    Also in 19 projects that use this

  • SkillPilotCHSkill

    level-up

    Eine Automatisierung pro Woche finden, scopen, shippen. Output landet als proposed-Eintrag in cadence.md mit konkreten Implementations-Schritten.

    Also in 12 projects that use this

  • ww-w-aiSkill

    pm-discovery

    PM Agent Team - Automated product discovery, strategy, and PRD generation. Runs PM analysis workflow to produce comprehensive PRD before PDCA Plan phase.

    Also in 3 projects that use this

  • +7 more from HK-hub

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 172 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read only these, for the page or site the person names:

    line 17
  2. Very specific:

    Use list_brands only when no brand is selected, and open_page to link Site Audit.

    line 23
  3. Very specific:

    When the page has an audit from the last 30 days, use it.

    line 31
  4. Distinctive:

    Never change the site or publish: the fixes are the person's to apply.

    line 46
  5. Distinctive:

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

    line 47

“Common” is measured: kept by at least 6 in 10 of the 172 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

Improve with audit

The playbook of the /audit shortcut ("Run an audit on …"): a page's Site Audit issues, turned into fixes ready to apply.

Data plan

Read only these, for the page or site the person names:

  1. get_site_audit_summary: the brand's recent audits, to find the page's latest.
  2. list_site_audit_issues: that audit's checks, passed and failed.
  3. fetch_page for the page, to write fixes against what is on it now.

Use list_brands only when no brand is selected, and open_page to link Site Audit.

Questions

  • None about the audit itself. Reading an existing result uses nothing.

Steps

  1. When the page has an audit from the last 30 days, use it. Otherwise start one with run_site_audit on that one page; the app shows the person what it uses of the month's audits first.
  2. Audit the whole site only when the person says so; that card shows its cost too.
  3. Order the failed checks by what matters for AI answers: whether AI crawlers can reach the page, then direct answers, structured data, titles and descriptions, then the rest.
  4. For each: why it matters, and the fix, ready to apply: the corrected markup, text or setting as code.

Output

A table of the issues (Issue, Why it matters for AI, Fix, Effort), then the fixes as code.

Next moves

Two or three, such as "Send fixes to Action Center" or checking again after the fix.

Don't

  • Never change the site or publish: the fixes are the person's to apply.
  • Don't fix what the audit didn't find without saying so.

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.