BC guardian-angel
This skill should be used when the user asks to 'run alignment check', 'check my agent alignment', 'get a safety reminder', 'guardian angel check', or when an agent wants to review its own behavior for safety and alignment best practices. Also activates on agent startup if configured.
This skill should be used when the user asks to 'run alignment check', 'check my agent alignment', 'get a safety reminder', 'guardian angel check', or when an…
As a process C 54/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
How to improve
- 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 Secrets in code
secret-high-entropy-tokenSKILL.md:86High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)> **`0x64…AC7`** (Base network)
quoted
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 54/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Consistency. Frontmatter name (guardian-angel) differs from the folder (guardian-angel-protocol)
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 35 steps
- 100Execution cost. Instruction body is 1090 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 285: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 35 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.