CtrlK
BlogDocsLog inGet started
Tessl Logo

aris-idea-discovery

Workflow 1: Full idea discovery pipeline. Orchestrates research-lit → idea-creator → novelty-check → research-review to go from a broad research direction to validated, pilot-tested ideas. Use when user says "找idea全流程", "idea discovery pipeline", "从零开始找方向", or wants the complete idea exploration workflow.

64

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/aris-idea-discovery/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-sequenced, highly actionable orchestration skill with strong checkpoints and feedback loops. Its main weaknesses are length/verbosity from inlined templates and the absence of progressive disclosure into separate reference files.

Suggestions

Move the REF_PAPER_SUMMARY.md, IDEA_REPORT.md, and IDEA_CANDIDATES.md markdown templates into separate files under references/ and link to them, reducing body length and improving progressive_disclosure.

Trim the verbatim checkpoint dialogue blocks to a short description of what to present and ask, rather than full quoted strings.

Add a brief explicit note on how parallel pilot experiments are launched and resource-constrained (e.g., the actual command or delegation target), since 'run parallel pilot experiments on available GPUs' is currently underspecified.

DimensionReasoningScore

Conciseness

Mostly procedural and necessary for a complex pipeline, but verbatim checkpoint dialogue blocks and full inlined report templates (REF_PAPER_SUMMARY, IDEA_REPORT, IDEA_CANDIDATES) could be tightened or externalized.

3 / 5

Actionability

Provides copy-paste-ready sub-skill invocations ('/aris-research-lit "$ARGUMENTS"'), concrete constants, and explicit output templates, with minor gaps where delegated steps like parallel pilot execution are underspecified.

4 / 5

Workflow Clarity

Clear Phase 0→5.5 sequence with explicit 🚦 checkpoints, feedback loops ('Repeat until the user is satisfied', lite-mode fallback when reviewer score < 6), and batch-operation validation (PILOT_TIMEOUT, GPU budget caps, novelty elimination).

5 / 5

Progressive Disclosure

Well-sectioned into Overview/Constants/Pipeline/Rules, but it is a monolithic ~316-line file with no bundle references and substantial inlined templates that would fit better in separate reference files.

3 / 5

Total

15

/

20

Passed

Description

87%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 states both capability and trigger conditions with concrete, natural (bilingual) phrases. Minor gaps in action coverage and synonym terms keep specificity and trigger quality just below the top anchor.

DimensionReasoningScore

Specificity

Names four concrete sub-skills it orchestrates ('research-lit → idea-creator → novelty-check → research-review') and the transformation ('broad research direction to validated, pilot-tested ideas'), but omits the refine-pipeline stage that the body includes, leaving a minor coverage gap.

4 / 5

Completeness

Explicitly answers both 'what' (full idea discovery pipeline orchestrating named sub-skills) and 'when' (concrete 'Use when user says...' trigger phrases), matching the top anchor.

5 / 5

Trigger Term Quality

Provides several natural trigger phrases a user would say ('找idea全流程', 'idea discovery pipeline', '从零开始找方向', 'complete idea exploration workflow'), but misses common synonyms like 'find research ideas' or 'brainstorm research topics'.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (a specific multi-stage idea-discovery pipeline) with distinctive bilingual trigger phrases, making conflict with other skills unlikely.

5 / 5

Total

18

/

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.

Validation14 / 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

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.