BF program-derivation
Formale Programmableitung / Formal Program Derivation: Architektur-Ermittlung, Abstraktionsschichten, Metriken (CC, LCOM, Kopplung, Kohäsion, Vendor Lock-in, SoC, Leaky Abstractions). Lade diesen Skill wenn der Nutzer eine Architekturanalyse, Programmableitung, formale Ableitung, Abstraktionsschichten, Interface-Design, Komplexitätsmessung, Refactoring-Planung oder Software-Qualitätsbewertung anfordert. / Load this skill when the user requests architecture analysis, program derivation, formal derivation, abstraction layers, interface design, complexity measurement, refactoring planning or software quality assessment.
Formale Programmableitung / Formal Program Derivation: Architektur-Ermittlung, Abstraktionsschichten, Metriken (CC, LCOM, Kopplung, Kohäsion, Vendor Lock-in…
As a process F 55/100 · Will not run — References files that are not bundled: references/boundary-checklist.md, references/interface-templates.md, references/metrics-examples.md
How to improve
- 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 · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Formale Programmableitung / Formal Program Derivation: Architektur… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
missing-refreference to a missing file: references/boundary-checklist.md - warning
missing-refreference to a missing file: references/interface-templates.md - warning
missing-refreference to a missing file: references/metrics-examples.md
Process rating: all ten parameters 55/100
- 0Tools and files. 3 referenced file(s) missing: references/boundary-checklist.md, references/interface-templates.md, references/metrics-examples.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 52 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1561 tokens
- 100Running it twice. No mutating operations
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)
- +1No license
- +2Single-language instructions
- +3Description length 624: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 52 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.