BC research-refine-pipeline
Run an end-to-end workflow that chains `research-refine` and `experiment-plan`. Use when the user wants a one-shot pipeline from vague research direction to focused final proposal plus detailed experiment roadmap, or asks to "串起来", build a pipeline, do it end-to-end, or generate both the method and experiment plan together.
Run an end-to-end workflow that chains research-refine and experiment-plan.
As a process C 71/100 · Has gaps — References files that are not bundled: ../shared-references/reviewer-backends.md, ../../shared-references/output-versioning.md, ../../shared-references/output-manifest.md
The same skill appears in 1 more place: Auto-claude-code-research-in-sleep
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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../shared-references/reviewer-backends.md - warning
missing-refreference to a missing file: ../../shared-references/output-versioning.md - warning
missing-refreference to a missing file: ../../shared-references/output-manifest.md - warning
missing-refreference to a missing file: ../../shared-references/output-language.md
Process rating: all ten parameters 71/100
- 0Tools and files. 4 referenced file(s) missing: ../shared-references/reviewer-backends.md, ../../shared-references/output-versioning.md, ../../shared-references/output-manifest.md
- 30Inputs and preconditions. Does not say what the process needs to start
- 70When it triggers. States when to use, but not when not to
- 100Steps. 50 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1630 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
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 325: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 50 items
- +3Output format is stated explicitly
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.