CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aris-research-pipeline

Full research pipeline: Workflow 1 (idea discovery) → implementation → Workflow 2 (auto review loop). Goes from a broad research direction all the way to a submission-ready paper. Use when user says "全流程", "full pipeline", "从找idea到投稿", "end-to-end research", or wants the complete autonomous research lifecycle.

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

73%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-structured orchestrator skill with an exemplary gated workflow: explicit sequencing, human checkpoints with defined branches, a bounded auto-review feedback loop, and concrete skill-invocation commands and templates. Its weaknesses are token efficiency — duplicated sub-skill descriptions, a flavor timeline section, and a time-sensitive model reference — and slightly vague Stage 2 implementation guidance.

Suggestions

Trim the Stage 3/4 "What this does" bullet lists to one line each (the invoked sub-skills' own SKILL.md files own that detail), and cut the "Typical Timeline" table and "sweet spot" narrative to save tokens.

Remove or abstract the time-sensitive "GPT-5.4 xhigh" model reference (e.g., make the reviewer model a config constant like REVIEWER_DIFFICULTY) so the skill does not go stale.

Make Stage 2 concrete: link an experiment scaffold/template (e.g., a seeded, argparse-configured training script skeleton in a references/ file) instead of generic directives like "extend pilot code to full scale".

Fix the fragile external reference by moving RESEARCH_BRIEF_TEMPLATE.md into this skill's own folder (e.g., references/RESEARCH_BRIEF_TEMPLATE.md) so the link resolves within the skill bundle.

DimensionReasoningScore

Conciseness

The body is mostly operational (constants, stages, gates, rules) but includes unnecessary material: the "What this does" bullet lists for Stages 3–4 re-describe sub-skills that own their own documentation, the "Typical Timeline" table and "sweet spot" bedtime advice are flavor, and "GPT-5.4 xhigh" is a time-sensitive version reference not in a deprecated section. This fits anchor 3 (mostly efficient, some unnecessary explanation or could be tightened) better than anchor 4's 'minor instances'.

3 / 5

Actionability

Provides concrete, copy-paste-ready artifacts: exact skill invocations (`/aris-idea-discovery "$ARGUMENTS"`, `/aris-auto-review-loop "$ARGUMENTS — [chosen idea title], difficulty: $REVIEWER_DIFFICULTY"`), a Gate 1 presentation template, and a full final-report markdown template. Stage 2's implementation guidance ("Extend pilot code to full scale", "Follow existing codebase conventions") remains high-level and idea-dependent, leaving minor gaps that fit anchor 4.

4 / 5

Workflow Clarity

The five stages are clearly sequenced with explicit validation checkpoints and feedback loops: Gate 1 branches (approve / pick different / request changes → re-run with refined constraints / reject / stop), AUTO_PROCEED semantics, Stage 2's self-review checklist, Stage 3's "Verify experiments started successfully" plus monitoring, and Stage 4's bounded retry loop ("repeat until score ≥ 6/10 or 4 rounds") with a stop rule if round 4 ends negative. This matches anchor 5's explicit validation, error-recovery loops, and checklists; anchor 4 would require missing checkpoints, and validation is present so no destructive/batch cap applies.

5 / 5

Progressive Disclosure

The skill has no bundle files; the body is organized into clear sections (Constants, Overview, Pipeline, Key Rules, Timeline) and its one external reference — `RESEARCH_BRIEF_TEMPLATE.md` via a clearly signaled one-level-deep markdown link — is appropriately placed. It falls short of anchor 5 because the reference points outside the skill folder (`../aris-infra/`), which is fragile, and the ~170-line body inlines presentation/report templates that could be split out, fitting anchor 4's 'minor organization gaps'.

4 / 5

Total

16

/

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: it states the concrete pipeline stages and end deliverable, provides an explicit 'Use when...' clause with natural bilingual trigger phrases, and is written in third person. The main improvement opportunities are dropping the internal "Workflow 1/2" labels in favor of plain stage names and adding a few more trigger synonyms.

DimensionReasoningScore

Specificity

The description lists several concrete pipeline stages — "Workflow 1 (idea discovery) → implementation → Workflow 2 (auto review loop)" and the deliverable "submission-ready paper" — which goes beyond naming the domain. It is not fully comprehensive since "implementation" is generic and the internal "Workflow 1/2" labels add little, fitting anchor 4 (several specific actions, minor gaps) better than anchor 5.

4 / 5

Completeness

Explicitly answers both questions: what it does ("Goes from a broad research direction all the way to a submission-ready paper") and when to use it ("Use when user says ... or wants the complete autonomous research lifecycle") with concrete trigger phrases. This matches the anchor-5 example structure exactly; anchor 4 would require the 'when' to be less explicit than it is.

5 / 5

Trigger Term Quality

Includes multiple natural trigger phrases a user would actually say: "全流程", "full pipeline", "从找idea到投稿", "end-to-end research", "complete autonomous research lifecycle", with bilingual synonyms. A few natural variations are missing (e.g., "research pipeline", "automated research"), so it fits anchor 4 rather than the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The full-lifecycle triggers ("full pipeline", "从找idea到投稿") carve out a clear niche distinct from generic research skills, and the description is written in third person. However, it overlaps with the individual sub-skills it orchestrates (idea discovery, auto review), which a user might invoke separately — minor overlap risk with closely related skills, fitting anchor 4.

4 / 5

Total

17

/

20

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.

Validation — 13 / 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: 1 suspicious

Warning

Total

13

/

16

Passed

Repository

OpenLAIR/dr-claw

Path

skills/aris-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.