agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/cat-agent-skills/submissions/audit-readiness/skills/scope-map/SKILL.md

scope-map

Skill95 starsChanged 6 days agoMITView on GitHub

Maps the audit scope to the standard's clauses and required evidence types with the deterministic clause_map engine. Use when the user says "we have an audit coming", "map the audit scope", "what clauses apply", or when an audit-readiness run begins.

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Start of every audit-readiness run.

    line 11
  2. Very specific:

    Run python3 scripts/clause_map.py --audit audit.json --clauses references/clause-table.json --out mapped.json from this skill's folder, …

    line 16
  3. Distinctive:

    Every clause row cites the clause table.

    line 21
  4. Distinctive:

    No readiness opinions here.

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “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

Scope Map

Purpose

Deterministic scope-to-clause mapping: which clauses apply, what evidence each requires, how fresh it must be.

When to use

Start of every audit-readiness run.

Inputs

Audit notice (standard, date, scope areas, active roles); clause table reference. Emits the entry hop of mfg.audit-readiness.v1 (schema in contracts/).

Steps

  1. Extract audit_id, standard, audit_date, scope[], active_roles, clause owners from the notice.
  2. Run python3 scripts/clause_map.py --audit audit.json --clauses references/clause-table.json --out mapped.json from this skill's folder, using workspace paths for the audit input and generated output.
  3. Quote the clause list verbatim.

Output

mapped.json - the {clause_map} hop.

Grounding requirements

Every clause row cites the clause table; scope comes from the audit notice verbatim.

Constraints

  • No readiness opinions here; mapping only.

Escalation / uncertainty

Unknown standard or ambiguous scope: ask the audit lead; record in escalations[].

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.

Check your setup, free