AF paper-reading-method-commitment
Use when the user has a selected Candidate Method, multiple Candidate Methods to merge, a user-authored rough method, or a reconstructed chat method and wants to converge on one human-owned method outcome before experiment design, research framing, or risk review.
Use when the user has a selected Candidate Method, multiple Candidate Methods to merge, a user-authored rough method, or a reconstructed chat method and wants…
As a process F 59/100 · Will not run — References files that are not bundled: references/workspace-structure.md, references/method-reconstruction-template.md, references/source-method-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: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/workspace-structure.md - warning
missing-refreference to a missing file: references/method-reconstruction-template.md - warning
missing-refreference to a missing file: references/source-method-template.md - warning
missing-refreference to a missing file: references/method-attack-transcript-template.md - warning
missing-refreference to a missing file: references/method-decision-log-template.md - warning
missing-refreference to a missing file: references/committed-method-design-template.md - warning
missing-refreference to a missing file: references/provisional-method-design-template.md - warning
missing-refreference to a missing file: references/method-redesign-brief-template.md - warning
missing-refreference to a missing file: references/method-rejection-note-template.md - warning
missing-refreference to a missing file: references/method-commitment-summary-template.md
Process rating: all ten parameters 59/100
- 0Tools and files. 10 referenced file(s) missing: references/workspace-structure.md, references/method-reconstruction-template.md, references/source-method-template.md
- 30Running it twice. 47 mutating operations with no state check
- 40Consistency. Frontmatter name (paper-reading-method-commitment) differs from the folder (06-method-commitment)
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Failures and branches. 4 branches
- 100Steps. 135 steps
- 100Execution cost. Instruction body is 2733 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)
- +1No license
- +2Single-language instructions
- +3Description length 264: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 135 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.