CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

71

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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 highly actionable, well-sequenced orchestrator skill with clear gates and validation feedback loops, but it is long and inlines reference-grade material that the progressive-disclosure links suggest should live in separate files. Tightening and moving bulk mechanics into the referenced files would materially improve it.

Suggestions

Move the full 'Resumable runs' and 'Overnight heartbeat: stall detection' sections into the already-referenced shared-references files, keeping only a short pointer plus the exact accept/gate rule in SKILL.md to cut the inline token load.

Collapse the Constants block into a compact table (flag | default | where it is passed through) instead of one verbose bullet per constant, preserving the override example.

Confirm the referenced shared-references and templates files actually ship with the skill bundle; the body links to ../shared-references/*.md and templates/RESEARCH_BRIEF_TEMPLATE.md but none are present in references/, scripts/, or assets/.

DimensionReasoningScore

Conciseness

It avoids explaining concepts Claude already knows, but the ~350-line body inlines substantial mechanics (the Constants block, the full Resumable runs section, and the complete heartbeat stall-detection bash) that could be tightened or offloaded to references.

2 / 3

Actionability

Provides copy-paste-ready invocations ("/idea-discovery \"$ARGUMENTS\""), concrete run_state.py / iteration_log.py commands with exact arguments, and explicit artifact paths — fully executable guidance throughout.

3 / 3

Workflow Clarity

Stages 1–5 are clearly sequenced with two explicit gates (Gate 1 human checkpoint, Gate 2 writing checkpoint), a per-phase accept table, and a validation/feedback loop (re-validate done-but-unaccepted stages on resume, never accept on the executor's own say-so).

3 / 3

Progressive Disclosure

Shared-reference links (external-cadence.md, resumable-runs.md, output-versioning.md) are one-level-deep and clearly signaled, but no bundle files exist in references/scripts/assets and large blocks of content that belong in those references (resumable runs, heartbeat detection) are inlined rather than split out.

2 / 3

Total

10

/

12

Passed

Description

100%

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

The description is concise, specific, and uses third-person voice while clearly stating both capabilities and explicit natural-language triggers in two languages. It is a strong, well-scoped description that distinguishes this orchestrator skill from its component sub-skills.

DimensionReasoningScore

Specificity

Lists multiple concrete pipeline stages — "idea discovery, experiments, and review all the way to a polished paper PDF" — rather than vague language, matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers both what (full end-to-end research pipeline from direction to paper PDF) and when ("Use when user says...") with an explicit trigger clause.

3 / 3

Trigger Term Quality

Provides natural trigger phrases a user would actually say in both English and Chinese ("full pipeline", "end-to-end research", "全流程", "从找idea到投稿"), giving good coverage rather than jargon.

3 / 3

Distinctiveness Conflict Risk

The niche is clearly the complete autonomous research lifecycle with distinct triggers like "full pipeline" and "全流程", making it unlikely to fire for a narrower single-stage skill.

3 / 3

Total

12

/

12

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

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

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 6 suspicious

Warning

Total

13

/

16

Passed

Repository
wanshuiyin/Auto-claude-code-research-in-sleep
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.