CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured orchestration skill: a clearly sequenced five-phase pipeline with genuine validation gates and feedback loops, concrete output paths, and copy-paste templates. Weakest points are mild redundancy across the outputs/template/summary sections and heavy inline reviewer-routing policy whose referenced shared files are absent from the bundle.

Suggestions

Reduce repetition of the output file list: the Default Outputs, Phase 4 template, and Phase 5 summary block each restate the same refine-logs paths — state them once and reference that list from the template and summary.

Trim the reviewer-routing blockquote to a two-line pointer to ../shared-references/reviewer-backends.md and move the routing-resolution policy detail into that reference file.

Add a short worked example of a completed Phase 2 gate check (thesis, dominant contribution, rejected complexity, residual reviewer concerns) so the gate is executable rather than only a question list.

DimensionReasoningScore

Conciseness

The body is mostly efficient — tight bullet lists per phase, a core rule stated in two sentences, and templates instead of prose. Minor redundancy keeps it below 5: the output file names are repeated across Default Outputs, the Phase 4 template, and the Phase 5 summary block, and the dense reviewer-routing blockquote inlines policy detail that belongs in its referenced shared file. It is well above the 'noticeably verbose' level of 2.

4 / 5

Actionability

Guidance is concrete and executable for an orchestration skill: exact output paths, explicit stage exit criteria ('Exit this stage only when these are explicit: ...'), decisive triage rules ('If in doubt, prefer re-running research-refine'), and a copy-paste-ready PIPELINE_SUMMARY.md template. It falls short of 5 only because stage execution itself is delegated to sibling skills and the Phase 2 gate check has questions but no worked example — minor gaps, not the vague abstraction of level 2.

4 / 5

Workflow Clarity

The Phase 0-5 sequence is clearly ordered with explicit validation checkpoints and feedback loops: Phase 0 triages whether the existing FINAL_PROPOSAL.md is missing/stale/mismatched with reuse-vs-rerun rules, Phase 1 defines explicit exit criteria, and Phase 2 is a planning gate that loops back ('If these answers are not crisp, tighten the final proposal first'). This matches the anchor-5 pattern of clear sequence, explicit validation steps, and error-recovery loops.

5 / 5

Progressive Disclosure

Structure is good: stage-specific detail is deferred to sibling skills 'only when needed' (one level deep, clearly signaled), and shared protocols are consolidated in an Output Protocols section. It falls short of 5 because the referenced bundle files (../research-refine/SKILL.md, ../experiment-plan/SKILL.md, ../shared-references/*.md) are not present in the provided bundle so the links cannot be verified, and the reviewer-routing policy block is inlined rather than kept in its referenced file — but the body itself is well-sectioned, well above the buried-reference problems of level 3.

4 / 5

Total

17

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it states the concrete capability (chaining two workflows into a one-shot pipeline), names the deliverables, and gives an explicit 'Use when...' clause with natural trigger phrases in both English and Chinese. The only room for improvement is slightly broader trigger synonym coverage.

DimensionReasoningScore

Specificity

The description names concrete actions — 'Run an end-to-end workflow that chains research-refine and experiment-plan' — and concrete deliverables ('focused final proposal plus detailed experiment roadmap'). It lists several specific actions with minor coverage gaps (e.g., review history and pipeline summary outputs are not mentioned), so it sits at 4 rather than the comprehensive 5, and is well above the 1-2-action level of 3.

4 / 5

Completeness

It explicitly answers both 'what' ('Run an end-to-end workflow that chains research-refine and experiment-plan... final proposal plus detailed experiment roadmap') and 'when' ('Use when the user wants a one-shot pipeline... or asks to "串起来", build a pipeline, do it end-to-end...'), matching the anchor-5 pattern of concrete trigger phrases attached to an explicit capability statement.

5 / 5

Trigger Term Quality

Natural trigger phrases are present: 'one-shot pipeline', 'build a pipeline, do it end-to-end', 'generate both the method and experiment plan together', and even a bilingual synonym '"串起来"'. Coverage is good but a few natural variants are missing (e.g., 'combine'/'integrate the stages', 'whole workflow'), placing it just below the comprehensive anchor of 5 and clearly above 3.

4 / 5

Distinctiveness Conflict Risk

The niche is clear — the integrated pipeline as distinct from its two component skills — and disambiguating triggers like 'one-shot', 'chains', 'both together', and '串起来' are present. However, it shares trigger vocabulary ('method', 'experiment plan', 'research') with its closely related sibling skills '/research-refine' and '/experiment-plan', leaving minor overlap risk, which fits anchor 4 better than the minimal-conflict anchor 5.

4 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

relative_links

Relative link issues: 4 suspicious

Warning

Total

14

/

16

Passed

Repository

wanshuiyin/Auto-claude-code-research-in-sleep

Path

skills/research-refine-pipeline/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.