DF architecture-decision-records-(adrs)
(no description)
Lightweight documentation capturing the context, decision, and consequences of significant technical choices.
As a process F 33/100 · No process to follow — References files that are not bundled: 0001-use-postgresql.md, 0002-caching-strategy.md, 0003-mongodb-user-profiles.md
ProcedurePostgreSQLMongoDBMySQLSoftware developmentWriting and documentstype and topics are labelled automatically from the skill text
How to improve
- Add a description to the frontmatter: without it the skill never triggers.
- The text references files that are not there: add them or drop the references.
For the model run — optional
- 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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-missingSKILL.md: no `description` — the skill can never trigger - warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
missing-refreference to a missing file: 0001-use-postgresql.md - warning
missing-refreference to a missing file: 0002-caching-strategy.md - warning
missing-refreference to a missing file: 0003-mongodb-user-profiles.md - warning
missing-refreference to a missing file: 0020-deprecate-mongodb.md - note
edit-residuethe text marks something as outdated (lines 35, 52, 219, 232): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 33/100
Will not run. References files that are not bundled: 0001-use-postgresql.md, 0002-caching-strategy.md, 0003-mongodb-user-profiles.md
- 0Tools and files. 4 referenced file(s) missing: 0001-use-postgresql.md, 0002-caching-strategy.md, 0003-mongodb-user-profiles.md
- 0When it triggers. No condition that starts the skill
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 1 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 40Consistency. Frontmatter name (architecture-decision-records-(adrs)) differs from the folder (architecture-decision-records)
- 100Steps. 23 steps
- 100Execution cost. Instruction body is 1911 tokens
- 100Progress reporting. Reports progress
- 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)
- +3Description length 0: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 17 headings
- +3Step-by-step instructions: 23 items
- +4Has examples (9 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 19.
External checks
ClawHub: suspicious
The skill content is ordinary ADR documentation, but its install instructions use an unpinned npx command from a mutable GitHub path that should be reviewed before use.
LLM: suspicious (high) · VirusTotal: suspicious · 10 Sept 2026