agentleFS
ansvisoransvisor/ansvisor/skills/quality/SKILL.md

quality

Skill233 starsChanged 5 months agoMITView on GitHub

E-E-A-T, Trust and Readability fixes. Leaves only what you alone can give.

12 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use debug, review and 1 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.
  • AnthropicSkill

    debug

    Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.

    Also in 4 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 5 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 4

    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:

    E-E-A-T: no author, no first-hand experience, no examples.

    line 29
  2. Distinctive:

    Don't invent quotes, authors, credentials, studies, customers or figures to pass a check.

    line 41
  3. Distinctive:

    Keep the passages AI quotes word for word.

    line 42
  4. Distinctive:

    Don't change what a passage claims: only how it says it.

    line 43

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

Quality pass

Make the fixes a draft's Quality checks ask for (E-E-A-T, Trust and Readability), and leave a short list of what only the person can add.

When to use

  • "Run a quality pass on the drafts under 60", "Fix this draft's readability", "What does this draft still need?"
  • The Quality tab in the Content Editor shows each draft's scores. When the person names no drafts, ask which ones, or list the drafts and let them pick.

What to read

  1. list_drafts: the brand's drafts, latest changed first.
  2. get_draft for each draft you work on, at most three in one run: its passages, its sources, and which passages AI quotes (locked).

Steps

  1. For each draft, find what the checks look for:
    • Readability: sentences over about 25 words, paragraphs over about 5 sentences, jargon without a definition.
    • Trust: claims without a source, figures without a date, a missing disclosure where the brand compares itself or recommends its own product.
    • E-E-A-T: no author, no first-hand experience, no examples.
    • Structure: headings that don't say what the section answers, a missing FAQ or schema.
  2. Fix what you can fix from the draft itself: split sentences, reorder, add headings, define terms, mark claims that need a source.
  3. Give the fixes as Before and After for each passage. When the person wants them kept as a new draft, save it 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.
  4. List what only the person can give: quotes, first-hand data, customer examples, the author and their credentials, sources for marked claims.

Output

For each draft: the fixes made, then "Only you can add" as a short to-do list.

Don't

  • Don't invent quotes, authors, credentials, studies, customers or figures to pass a check.
  • Keep the passages AI quotes word for word.
  • Don't change what a passage claims: only how it says it.

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.