AF paper-reading-problem-reality-check
Use when the user wants to stress-test whether one selected Research Question Card's problem is real, evidence-backed, externally grounded, safely motivated, and worth keeping as a research motivation.
Use when the user wants to stress-test whether one selected Research Question Card's problem is real, evidence-backed, externally grounded, safely motivated…
As a process F 49/100 · Will not run — References files that are not bundled: references/source-card-template.md, references/workspace-structure.md, references/source-research-questions-template.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
missing-refreference to a missing file: references/source-card-template.md - warning
missing-refreference to a missing file: references/workspace-structure.md - warning
missing-refreference to a missing file: references/source-research-questions-template.md - warning
missing-refreference to a missing file: references/interrogation-transcript-template.md - warning
missing-refreference to a missing file: references/problem-reality-check-report-template.md - warning
missing-refreference to a missing file: references/problem-reality-checks-summary-template.md - note
edit-residuethe text marks something as outdated (lines 15): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 49/100
- 0Tools and files. 6 referenced file(s) missing: references/source-card-template.md, references/workspace-structure.md, references/source-research-questions-template.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 40Consistency. Frontmatter name (paper-reading-problem-reality-check) differs from the folder (03-problem-reality-check)
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Failures and branches. 9 branches
- 100Steps. 115 steps
- 100Execution cost. Instruction body is 3179 tokens
- low 13 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)
- +1No license
- +2Single-language instructions
- +3Description length 201: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 115 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.