BD opsec.md
A swift reminder of both human and agent duties regarding operational security.
As a process D 47/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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
-
medium Broad scope
meta-agent-memory-dumpheartbeat.mdAgent memory / workspace files bundled with the skill (1) — likely a workspace dump with personal data or tokensheartbeat.md
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "ai_generated" - note
frontmatter-keyunknown frontmatter key "standards" - note
frontmatter-keyunknown frontmatter key "shoutout" - note
frontmatter-keyunknown frontmatter key "wulfcorp" - note
frontmatter-keyunknown frontmatter key "server_invite" - note
frontmatter-keyunknown frontmatter key "discord" - note
frontmatter-keyunknown frontmatter key "matrix"
Process rating: all ten parameters 47/100
- 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
- 40Consistency. Frontmatter name (opsec.md) differs from the folder (opsecmd)
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70Failures and branches. 4 branches
- 75Steps. 3 steps
- 100Execution cost. Instruction body is 1075 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
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)
- +3Description length 79: 120–800 characters recommended
- +4Structure: 1 headings, hard to scan
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Step-by-step instructions: 3 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 53.