CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

research-pipeline

Full end-to-end research pipeline: from a broad research direction through idea discovery, experiments, and review all the way to a polished paper PDF. Use when user says "全流程", "full pipeline", "从找idea到投稿", "end-to-end research", or wants the complete autonomous research lifecycle.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/skills-codex/research-pipeline/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 an actionable, well-gated orchestration guide with explicit stop conditions, validation steps, and a resume protocol, but it is padded by repeated AUTO_PROCEED semantics and confusing stage numbering. Its referenced shared files are absent from the bundle, weakening its navigation structure.

Suggestions

State the AUTO_PROCEED checkpoint rule once in "Checkpoint execution rule" and reference it from Gate 1, Gate 2, and "Key Rules" instead of restating it; likewise state the queue-routing rule (≤5 vs ≥10 jobs) only once.

Fix the dangling "same as before" in Stage 4 Step 1 by specifying the report contents inline or linking to a template, and collapse the "Stage 5 / Stage 6" dual numbering into a single consistent numbering.

Move the bash helper-resolution block and the reviewer-routing preamble into a bundled reference file (e.g., the already-linked resumable-runs.md) and include the referenced shared-references files in the skill's bundle so links resolve.

DimensionReasoningScore

Conciseness

The body is mostly operational with no tutorial padding, but AUTO_PROCEED semantics are restated in roughly five places ("Checkpoint execution rule", Gate 1, "Key Rules", Gate 2, and the Constants entry), and the queue-routing rule ("≤5 jobs → /run-experiment, ≥10 jobs... → /experiment-queue") appears twice. This redundancy fits anchor 3 — could be tightened — rather than anchor 4's "minor instances".

3 / 5

Actionability

Concrete executable guidance dominates: exact sub-skill invocations ("/idea-discovery \"$ARGUMENTS\" — AUTO_PROCEED: $AUTO_PROCEED"), runnable CLI calls ("python3 \"$RUN_STATE\" start . \"$RUN_ID\" --executor ... --phases ..."), explicit output filenames, and a report template. Minor gaps — $RUN_ID provenance, "--artifact <path>", and "Track total GPU-hours" with no mechanism — keep it below anchor 5.

4 / 5

Workflow Clarity

The pipeline is clearly sequenced with explicit validation and feedback loops ("runs the smallest experiment first to verify the environment; auto-debugs failures (up to 3 attempts)", "repeat until score ≥ 6/10 or 4 rounds", "Do not loop forever") and explicit gate behavior for both AUTO_PROCEED modes. It falls below anchor 5 because Stage 4 Step 1's "same as before" is a dangling reference to behavior defined nowhere in this file, and the "Stage 5 / Stage 6" dual-numbering header introduces avoidable confusion.

4 / 5

Progressive Disclosure

The body is well-sectioned and defers detail via clearly signaled one-level-deep links ("[resumable-runs.md](../shared-references/resumable-runs.md)", "[Output Versioning Protocol](../shared-references/output-versioning.md)"), but no referenced files exist in this bundle — the links point outside it and don't resolve. The inlined 13-line bash helper-resolution block and dense reviewer-routing preamble are also content that belongs in reference files, fitting anchor 3.

3 / 5

Total

14

/

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 that clearly communicates the full-lifecycle scope with explicit, natural trigger phrases in both English and Chinese. The only improvements are enumerating a few more concrete actions and adding one or two common synonyms.

DimensionReasoningScore

Specificity

The description lists several concrete pipeline stages — "from a broad research direction through idea discovery, experiments, and review all the way to a polished paper PDF" — covering the full lifecycle. It stops short of anchor 5 because it names stages rather than enumerating the concrete actions within each (e.g., generating ranked ideas, deploying GPU experiments).

4 / 5

Completeness

It explicitly answers both what ("Full end-to-end research pipeline: from a broad research direction... to a polished paper PDF") and when ("Use when user says...") with concrete trigger phrases. This matches the anchor-5 example structure of clear what plus explicit when.

5 / 5

Trigger Term Quality

Good natural trigger coverage including "full pipeline", "end-to-end research", "complete autonomous research lifecycle", and bilingual variants ("全流程", "从找idea到投稿"). A few natural synonyms (e.g., "research workflow", "autonomous research") are missing, keeping it below anchor 5.

4 / 5

Distinctiveness Conflict Risk

The scope is clearly the complete lifecycle, distinct from single-stage siblings whose triggers are narrower, so conflict risk is minor. It sits below anchor 5 because the skill orchestrates closely related sub-skills (idea-discovery, paper-writing, research-lit) in the same crowded research family.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 7 suspicious

Warning

Total

15

/

16

Passed

Repository

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

Path

skills/skills-codex/research-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.