BF paper-reading-field-map
Use when the user is new to a research direction and wants to scan papers to understand branches, representative works, common methods, benchmarks, metrics, saturated areas, and unclear areas.
Use when the user is new to a research direction and wants to scan papers to understand branches, representative works, common methods, benchmarks, metrics…
As a process F 55/100 · Will not run — References files that are not bundled: references/field-boundary-template.md, references/workspace-structure.md, references/paper-position-record-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/field-boundary-template.md - warning
missing-refreference to a missing file: references/workspace-structure.md - warning
missing-refreference to a missing file: references/paper-position-record-template.md - warning
missing-refreference to a missing file: references/search-strategy-template.md - warning
missing-refreference to a missing file: references/research-clusters-template.md - warning
missing-refreference to a missing file: references/research-opportunities-template.md - warning
missing-refreference to a missing file: references/html-report-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 55/100
- 0Tools and files. 7 referenced file(s) missing: references/field-boundary-template.md, references/workspace-structure.md, references/paper-position-record-template.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 7 mutating operations with no state check
- 40Consistency. Frontmatter name (paper-reading-field-map) differs from the folder (01-field-map)
- 60Result and completion. Output format stated, no completion criterion
- 70Failures and branches. 6 branches
- 100Steps. 65 steps
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 1708 tokens
- 100Progress reporting. Reports progress
- 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)
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 192: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 65 items
- +3Output format is stated explicitly
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.