CtrlK
BlogDocsLog inGet started
Tessl Logo

ds-full-pipeline

Full DeepScientist research pipeline: scout → baseline → idea → experiment → analysis → optimize → write → review → finalize. End-to-end autonomous research lifecycle.

55

Quality

61%

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/ds-full-pipeline/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 content is a tight, well-sequenced pipeline overview that assumes Claude's competence and delegates stage detail cleanly to sibling skills via explicit commands. Its main gap is that the autonomous middle stages (4-9) lack explicit per-stage validation or failure-handling checks, relying on a general 'fail gracefully' rule rather than stage-specific checkpoints.

DimensionReasoningScore

Conciseness

The body is lean: each stage is a one-line purpose, a command invocation, and a one-line output description, with no padded explanations of concepts Claude already knows — every token earns its place, fitting the 'lean and efficient; assumes Claude's competence' anchor.

5 / 5

Actionability

Each stage gives a concrete, copy-pasteable slash command (e.g. `/ds-scout "$ARGUMENTS"`) and a clear output, which is executable guidance; it stops short of a full 5 because the commands delegate to other skills rather than providing the runnable details inline, leaving minor gaps for first-time use.

4 / 5

Workflow Clarity

The nine stages are explicitly sequenced with two labeled gate checkpoints (Gate 1, Gate 2) and an explicit re-review loop ('If review identifies critical issues → fix and re-review, max 2 rounds'), but validation between the autonomous stages 4-9 is implicit rather than spelled out, so it sits just below the top anchor.

4 / 5

Progressive Disclosure

The SKILL.md is a clean overview that delegates per-stage detail to nine sibling skills via one-level-deep slash-command references, with no inlined bulk content and no nested reference chains; for a skill under 50 lines with no external bundle files needed, the well-organized section structure fits the top anchor.

5 / 5

Total

18

/

20

Passed

Description

38%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.

The description clearly communicates a multi-stage research pipeline with a distinct identity, but it omits any explicit 'Use when' trigger guidance and relies on generic keywords, which limits discoverability. Adding natural trigger phrases and a 'when to use' clause would substantially raise the completeness and trigger-term scores.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to run a full end-to-end research study, generate a paper from scratch, or chain DeepScientist stages automatically.'

Include natural user-facing keywords and synonyms such as 'research study', 'run experiments', 'write a paper', and 'autonomous research'.

State in one phrase what the pipeline produces (e.g. 'produces a complete paper with reproducible experiments') so the 'what' is concrete rather than just a stage list.

DimensionReasoningScore

Specificity

It names the domain (DeepScientist research pipeline) and lists concrete stage actions (scout, baseline, idea, experiment, analysis, optimize, write, review, finalize), but these are stage labels rather than fully elaborated capabilities, so coverage is broad but not deeply concrete — fits the 'names domain and 1-2 concrete actions, but not comprehensive' anchor adjusted upward for the enumerated stage list.

3 / 5

Completeness

It clearly answers 'what' (the chained research pipeline) but provides no 'when' / 'Use when...' clause at all, and the rubric explicitly caps completeness at 3 when trigger guidance is missing; combined with the vague 'what' framing it sits at 2 rather than 3.

2 / 5

Trigger Term Quality

Phrases like 'research pipeline' and 'autonomous research lifecycle' are domain-relevant but generic; it lacks the natural trigger phrases a user would actually say (e.g. 'run a research study', 'generate a paper', 'run experiments') and includes no file extensions or synonyms, leaving only a couple of generic keywords.

2 / 5

Distinctiveness Conflict Risk

The 'DeepScientist' name and the specific stage chain give it a clear niche with minimal overlap risk against unrelated skills, though 'research lifecycle' is broad enough to risk minor overlap with sibling DeepScientist skills.

4 / 5

Total

11

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
OpenLAIR/dr-claw
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.