BF dodaf
Create, verify, and document DoDAF 2.0/2.1 architecture models with comprehensive completeness and consistency checks. Guides users step-by-step through professional defense architecture design. Outputs consolidated PDF/Word report with all views integrated.
As a process F 42/100 · Will not run — References files that are not bundled: path, references/dodaf-terminology.md, references/dodaf-best-practices.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Secrets in code
secret-high-entropy-tokenscripts/verify_dodaf.py:54High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"OV-3": ["OV-3…rix"],
detector -
low Secrets in code
secret-high-entropy-tokenscripts/verify_dodaf.py:58High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"CV-3": ["CV-3…ies"],
quoted
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: path - warning
missing-refreference to a missing file: references/dodaf-terminology.md - warning
missing-refreference to a missing file: references/dodaf-best-practices.md
Process rating: all ten parameters 42/100
- 0Tools and files. 3 referenced file(s) missing: path, references/dodaf-terminology.md, references/dodaf-best-practices.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 55Failures and branches. 1 branches
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 4882 tokens
- 85Steps. 166 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- low 10 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)
- -233 emoji in the instructions: noise for the model
- -32 of 2 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 258: enough signal without eating the budget
- +4Structure: 27 headings
- +3Step-by-step instructions: 166 items
- +3Output format is stated explicitly
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.