agentleFS
chonts5615chonts5615/Claude-Code/coverage-audit/SKILL.md

coverage-audit

Skill2 starsChanged 5 months agoNo licenceView on GitHub

Audit the coverage between any two talent management artifacts — interview questions vs. behavioral indicators, competency models vs. essential functions, assessment batteries vs. leadership enablers, job analysis task statements vs. selection tool content, success profiles vs. 360 instruments, or any pairing where one artifact should systematically map to another. Use this skill whenever the user asks to "audit coverage," "check coverage," "coverage matrix," "map these to those," "what's missing," "gap analysis," "check alignment between," "verify indicator coverage," "behavioral indicator coverage," "are all competencies covered," "do these questions hit all the indicators," "what gaps exist," "content validity check," "crosswalk these," or uploads two artifacts and asks whether one adequately addresses the other. Also trigger when the user is building or reviewing interview guides, structured assessment protocols, competency-to-tool mappings, or any content validity exercise. Even if the user doesn't say "coverage" explicitly, use this skill whenever two HR/talent artifacts need systematic alignment verification. This skill produces a paired Excel workbook (coverage matrix with PASS/PARTIAL/GAP scoring) and Word executive summary as deliverables.

5 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

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 0

    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.