CtrlK
BlogDocsLog inGet started
Tessl Logo

ds-idea

Use when a quest needs concrete hypotheses, limitation analysis, candidate directions, or a selected idea relative to the active baseline.

58

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/ds-idea/SKILL.md
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 highly actionable with concrete tool calls, thresholds, and explicit validation gates, and it correctly links to real one-level reference files, but its main weakness is severe verbosity and redundancy across repeated sections and a monolithic main file that underuses progressive disclosure.

Suggestions

Consolidate the repeated 5-10 paper floor, 6-12/2-3 frontier, and literature/memory-search guidance into a single authoritative section and reference it instead of restating it in Non-negotiable rules, Related-work mandate, Memory rules, and Workflow §2.

Move the detailed ideation lenses, failure-mode recovery table, and durable-output templates into existing reference files so SKILL.md becomes a lean overview pointing to them.

Tighten prose by converting enumerated rule lists that restate the same constraint into a single checklist, cutting roughly half the body while preserving every distinct rule.

DimensionReasoningScore

Conciseness

The body is substantive and does not explain concepts Claude already knows, but at ~1290 lines it is heavily padded with repetition — the 5-10 paper floor, the 6-12/2-3 frontier numbers, and the literature/memory-search guidance each recur across multiple sections and could be dramatically tightened.

2 / 3

Actionability

It provides concrete, executable guidance throughout — specific tool calls like `artifact.arxiv(paper_id=..., full_text=False)` and `artifact.submit_idea(mode='create', lineage_intent='continue_line'|'branch_alternative', ...)`, concrete file paths, and explicit numeric thresholds (5-10 papers, 6-12 raw ideas, 7/10 gate).

3 / 3

Workflow Clarity

It offers a sequenced numbered Workflow (§1-§8) plus Phases A/B/C, with explicit validation checkpoints such as the §7.1 quality gate (do not promote below 7/10), the narrative defensibility precheck, and concrete 'do not exit if...' exit criteria.

3 / 3

Progressive Disclosure

All seven referenced bundle files exist and are signaled one level deep ('Use references/... for ...'), but SKILL.md itself is a monolithic ~1290-line wall of text holding most detail inline rather than acting as a lean overview that points out to those references.

2 / 3

Total

10

/

12

Passed

Description

60%

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 a strong, explicit trigger clause with concrete deliverables, but it folds the 'what' into the 'when' rather than stating the capability separately and uses a somewhat narrow, technical set of trigger terms.

Suggestions

Add a distinct leading capability clause (e.g. 'Generates concrete, literature-grounded research directions from the active baseline.') before the 'Use when' trigger so 'what' and 'when' are both explicit.

Broaden trigger terms with more natural phrasings users would actually say, such as 'brainstorm research ideas', 'come up with a research direction', or 'find a new approach'.

Sharpen distinctiveness from the 'scout' skill by framing idea as the selection/decision step rather than overlapping on literature and novelty.

DimensionReasoningScore

Specificity

Names multiple concrete deliverables — 'concrete hypotheses, limitation analysis, candidate directions, or a selected idea' — which lists several specific outputs rather than a vague domain.

3 / 3

Completeness

The 'when' is explicit and strong ('Use when a quest needs...'), but the 'what does this do' is only implied through the trigger list rather than stated as its own distinct capability clause.

2 / 3

Trigger Term Quality

It includes relevant research-domain keywords a target user might say ('candidate directions', 'limitation analysis') but coverage is narrow and leans technical ('relative to the active baseline'), missing common natural variations like 'brainstorm' or 'research ideas'.

2 / 3

Distinctiveness Conflict Risk

It targets a reasonably specific niche (direction selection tied to an 'active baseline') but could overlap with companion skills like 'scout' that also handle literature and novelty, so it is not a fully conflict-free niche.

2 / 3

Total

9

/

12

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.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (1291 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

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.