agentleFS
tidycatc132tidycatc132/claude-skills/skills/content-quality-auditor/SKILL.md

content-quality-auditor

Skill0 starsChanged 36 days agoNo licenceView on GitHub

Use when the user asks to audit content quality, run an E-E-A-T or CORE-EEAT analysis, check whether a page or draft is ready to publish, score a product review, guide, comparison or landing page, find trust, experience, expertise or authority gaps in one piece, flag AI-slop writing, or rerun an audit after fixes. Audits one page, draft or article against the 80-item CORE-EEAT benchmark and returns a SHIP, FIX, BLOCK or UNDECIDED verdict. scripts/score_eeat.py applies the profile weights, vetoes, 59 cap and unknown rules and shows the arithmetic. Do NOT use for site-wide technical health such as crawling, indexing or Core Web Vitals (use technical-seo-checker), for topics competitors cover and you do not (use content-gap-analysis), for what a query's results page rewards (use serp-analysis), for benchmarking rival domains (use competitor-analysis), or for writing, rewriting or proofreading the content itself.

4 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, 0 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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.