agentleFS
Sign inStart free
malinskibeniaminmalinskibeniamin/skills/hook-audit/SKILL.md

hook-audit

Skill4 starsChanged 10 days agoMITView on GitHub

Analyze hook effectiveness and session telemetry. Use when auditing hook latency, violations, zero-fire rules, severity, manifest drift, skill firing, session trends, or retrospectives.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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. Very specific:

    Before deletion, shadow via HOOK_SHADOW_RULES in a representative, version-qualified trial.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Repeated corrections/skill improvements: read Poteto.

Audit ~/.claude/hook-metrics/ per REFERENCE.md.

Modes: default/--hooks activity; --retro adds flow/environment; --all also adds latency, skill firing and drift.

Flow

  1. Inventory hooks/date range; separate evals from real runs. Cohort by harness version/model; split or exclude mixed-model sessions using model-switches.jsonl.
  2. Aggregate blocks, warnings, nudges, denials, sessions, trend; compute P50/P95 and wall time when requested.
  3. Compare scripts, observed keys, and enforcement; distinguish true zero-fire candidates, untested hooks, and advisory rules.
  4. Retro: follow Session-environment retrospective; add available retro metrics. Missing telemetry does not block transcript findings.
  5. All: inspect skill-fires.jsonl; run bash scripts/generate-hook-configs.sh --check.
  6. Model-switch policy: use /quantify-impact; success/rework is primary, cache-write cost a guardrail.
  7. Rank at most five actions by telemetry/session impact. Recommend only unless edits were requested.

Before deletion, shadow via HOOK_SHADOW_RULES in a representative, version-qualified trial; compare outcomes/violations. Never shadow strict safety/permission.

Done

Report metrics/values, sample size, 7-day trend, next action; name gaps. Below five comparable real sessions is preliminary. Cite source files and exact harness_version + model cohort for prune/severity changes.

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