AF guardian-audit
Tamper-evident audit logger that pairs with Guardian safety skill. Captures safety decisions (halts, approvals, escalations) in an append-only, hash-chained log. Use when Guardian makes a safety decision. Use for compliance audit trails. Does NOT activate on general logging requests like 'log this' or routine queries. Requires explicit safety context or compliance intent to trigger.
As a process F 35/100 · Will not run — References files that are not bundled: references/LOG-SCHEMA.md, references/COMPLIANCE-MAPPING.md, references/REPLAY.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/LOG-SCHEMA.md - warning
missing-refreference to a missing file: references/COMPLIANCE-MAPPING.md - warning
missing-refreference to a missing file: references/REPLAY.md - note
frontmatter-keyunknown frontmatter key "Support"
Process rating: all ten parameters 35/100
- 0Tools and files. 3 referenced file(s) missing: references/LOG-SCHEMA.md, references/COMPLIANCE-MAPPING.md, references/REPLAY.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 7 mutating operations with no state check
- 40Consistency. Frontmatter name (guardian-audit) differs from the folder (data-guardian-audit)
- 55Failures and branches. 1 branches
- 100Steps. 32 steps
- 100Execution cost. Instruction body is 1634 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 14 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 385: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 32 items
- +4Has examples (5 code blocks)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.