agentleFS
MicrosoftKnown publishermicrosoft/cat-agent-skills/submissions/content-quality-auditor/SKILL.md

content-quality-auditor

Skill95 starsChanged 6 days agoMITView on GitHub

Use this skill when the user asks to assess, audit, score, review, improve, prioritise, or quality-check content, documents, pages, posts, decks, or reusable artefacts.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 7

    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:

    Use this skill to assess content quality in a repeatable, evidence-led way and produce a prioritised improvement plan.

    line 8
  2. Distinctive:

    Do not infer missing facts, usage statistics, or business impact.

    line 22
  3. Distinctive:

    If you cannot access a referenced artefact, state that limitation and assess only what is available.

    line 23
  4. Distinctive:

    If the user supplies a different rubric, use their rubric instead.

    line 49
  5. Distinctive:

    If auditing multiple artefacts, provide a comparative summary and prioritised backlog.

    line 59
  6. Distinctive:

    Use this format unless the user requests another structure:

    line 63
  7. Distinctive:

    No inaccessible content is treated as reviewed.

    line 119

“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.

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

Content Quality Auditor

Use this skill to assess content quality in a repeatable, evidence-led way and produce a prioritised improvement plan.

What to audit

The skill can be used for:

  • Individual documents, pages, posts, decks, scripts, or templates.
  • Groups of related artefacts.
  • Content libraries where consistency and reuse matter.
  • Draft material before publication.

Evidence rules

  • Base the audit only on content the user provides or content available through the agent's connected sources.
  • Do not infer missing facts, usage statistics, or business impact.
  • If you cannot access a referenced artefact, state that limitation and assess only what is available.
  • Separate observed evidence from suggested improvements.

Default seven-dimension rubric

Score each dimension from 0 to 5.

ScoreMeaning
0Not present or unusable.
1Present but weak, confusing, or incomplete.
2Basic but inconsistent or hard to reuse.
3Usable with moderate improvement needed.
4Strong with minor refinement needed.
5Publication-ready or operationally robust.

Assess these dimensions:

  1. Purpose and audience clarity - Is the content clear about who it is for and what it helps them do?
  2. Structure and navigation - Is the content logically organised and easy to scan?
  3. Evidence and specificity - Are claims supported by examples, data, sources, or concrete detail?
  4. Practical usefulness - Does the content help the reader make a decision or take action?
  5. Consistency and standards alignment - Does it follow the expected terminology, design, tone, and formatting conventions?
  6. Reusability and modularity - Can the content be reused, adapted, or maintained without excessive rework?
  7. Completeness and next action - Are important gaps, dependencies, risks, and follow-up actions visible?

If the user supplies a different rubric, use their rubric instead.

Workflow

  1. Identify the artefact or artefacts being audited.
  2. Confirm the intended audience and purpose from the available material.
  3. Apply the rubric dimension by dimension.
  4. Note specific evidence for each score.
  5. Identify priority fixes, separating major blockers from polish.
  6. Recommend a practical sequence of improvements.
  7. If auditing multiple artefacts, provide a comparative summary and prioritised backlog.

Output format

Use this format unless the user requests another structure:

## Audit summary

Overall assessment: [Short judgement]
Overall score: [Average]/5
Priority: [High / Medium / Low]

## Scorecard

| Dimension | Score /5 | Evidence | Recommended improvement |
|---|---:|---|---|
| Purpose and audience clarity |  |  |  |
| Structure and navigation |  |  |  |
| Evidence and specificity |  |  |  |
| Practical usefulness |  |  |  |
| Consistency and standards alignment |  |  |  |
| Reusability and modularity |  |  |  |
| Completeness and next action |  |  |  |

## Highest-value fixes

1. [Fix]
2. [Fix]
3. [Fix]

## Suggested next version

[Concise recommended direction]

Multi-artefact output

For multiple artefacts, add:

## Prioritised improvement backlog

| Priority | Artefact | Issue | Recommended action | Effort | Impact |
|---|---|---|---|---|---|

References

This skill includes supporting reference material. Read the relevant reference file when the task needs additional structure, rubric detail, examples, or checklist support.

  • references/scoring-rubric.md - use this when additional structure, examples, or checks are useful for the task.

Quality checklist

Before responding, check:

  • Scores are justified by evidence.
  • Recommendations are specific and actionable.
  • No inaccessible content is treated as reviewed.
  • The output helps the user decide what to improve next.

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.