BF self-improving-intent-security-agent
Documentation-first skill and workflow toolkit for intent-based security. Provides templates, examples, and local helper scripts for capturing intent, reviewing actions, documenting rollbacks, and recording learnings. Use when: (1) designing or prototyping intent validation workflows, (2) documenting high-risk operations, (3) creating audit trails and rollback records, (4) building your own runtime enforcement layer.
As a process F 43/100 · Will not run — References files that are not bundled: references/hooks-setup.md, references/api.md, scripts/intent-capture.sh
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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Risky intent
intent-offensive-securityreferences/architecture.md:666Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Privilege escalation (agent expands permissions)
Files scanned: 35. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/hooks-setup.md - warning
missing-refreference to a missing file: references/api.md - warning
missing-refreference to a missing file: scripts/intent-capture.sh - warning
missing-refreference to a missing file: scripts/action-validator.sh - warning
missing-refreference to a missing file: scripts/learning-capture.sh - warning
missing-refreference to a missing file: references/multi-agent.md
Process rating: all ten parameters 43/100
- 0Tools and files. 6 referenced file(s) missing: references/hooks-setup.md, references/api.md, scripts/intent-capture.sh
- 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. 6 mutating operations with no state check
- 70Execution cost. Instruction body is 4630 tokens
- 100Steps. 90 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 25 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
- -33 of 4 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 420: enough signal without eating the budget
- +4Structure: 49 headings
- +3Step-by-step instructions: 90 items
- +4Has examples (18 code blocks)
- +4Reference files are cited in the instructions (3 of 5)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.