BD fpf-problem-solving
Use the First Principles Framework (FPF) Library, Core plus 36 domain frameworks (DPFs) stored locally, to think more rigorously than the situation's default: decompose problems, architect systems, generate real alternatives, decide under uncertainty, reconsider decisions, establish causality, design control loops, recover and improve methods, steer, hand off or resume agent work, check sources and evidence, explain, rewrite text plainly, define quality, and apply field methods for strategy, goals/OKR, operations, management, research, decision design, systems engineering, knowledge access, mathematics, notation, narrative and human capability. Triggers: FPF, DPF, fpf.tools, Levenchuk, a pattern ID such as F.19, C.11.DUA, A.15.10, GOALS.7 or STR.18, bounded contexts, assurance, SoTA packs, operational parsimony, causal/temporal reasoning, modularity, lexical discipline. Not for simple task planning, general philosophy, or Agile unrelated to FPF.
Use the First Principles Framework (FPF) Library, Core plus 36 domain frameworks (DPFs) stored locally, to think more rigorously than the situation's default…
As a process D 46/100 · Unfinished process — References files that are not bundled: references/core-router.md, README.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: 80. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/core-router.md - warning
missing-refreference to a missing file: README.md
Process rating: all ten parameters 46/100
- 0Tools and files. 2 referenced file(s) missing: references/core-router.md, README.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 8 mutating operations with no state check
- 55Failures and branches. 1 branches
- 70Execution cost. Instruction body is 4296 tokens
- 100Steps. 26 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
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
- +3Description length 959: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +4Structure: 13 headings
- +3Step-by-step instructions: 26 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.