BC dodaf
Knowledge base from DoD Architecture Framework (DoDAF) 2.02 — Volume II: Architectural Data and Models. Use for DoDAF viewpoints, DM2 meta-model, capability modeling, operational architecture, systems architecture, services architecture, data/information modeling, standards compliance, project/portfolio integration, and fit-for-purpose model selection. Does not cover DoDAF Volume I (policy/governance) or Volume III (enterprise-level guidance); also does not substitute for the live DISR or DARS registries.
Knowledge base from DoD Architecture Framework (DoDAF) 2.02 — Volume II: Architectural Data and Models. Use for DoDAF viewpoints, DM2 meta-model, capability…
As a process C 62/100 · Has gaps — weak spots: result and completion, failures and branches, running it twice
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 · 0
✓ No critical or high findings
Files scanned: 17. 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 62/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 48 steps, 3 vague phrases
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2819 tokens
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
- +2Single-language instructions
- +3Description length 510: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 48 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.