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

readiness-pack

Skill95 starsChanged 6 days agoMITView on GitHub

Drafts the audit-readiness pack - verdict, gaps with owners and actions, clause map, evidence index - from the contract payload. Use when the user says "draft the readiness pack", "prep the audit binder", or after gap-check in a readiness run.

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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:

    Every row cites the engine output.

    line 21

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

Readiness Pack

Purpose

Terminal artifact: the pack rendered from templates/pack-template.md, populated only from the contract payload.

When to use

End of every readiness run.

Inputs

gaps.json (full payload).

Steps

  1. Validate against the contract; major gaps lead the pack.
  2. Fill the template: verdict, gap table (clause, status, severity, owner, action, due), clause map, evidence index.
  3. Mark DRAFT - the quality director owns the plan; nothing is filed and no evidence is fabricated or reworded into existence (#5).

Output

READINESS-<audit_id>.md - terminal artifact.

Grounding requirements

Every row cites the engine output; the verdict cites #4.

Constraints

  • Draft-first; nothing in the pack that is not in the contract payload.
  • A not_ready verdict is presented as not_ready, whatever the meeting on Monday wants to hear.

Escalation / uncertainty

Majors within 14 days of the audit date get an explicit call-out to the quality director.

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