CtrlK
BlogDocsLog inGet started
Tessl Logo

stat-research-orchestrator

Orchestrate a statistical research pipeline centered on formal problem formulation, method proposal, theoretical analysis, experimental evaluation, comparison, and final result synthesis.

68

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

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 concise, fully actionable orchestration guide with a clearly sequenced pipeline, explicit validation gating, and well-organized sections requiring no external bundle files.

DimensionReasoningScore

Conciseness

The body is lean — a pipeline diagram, terse per-step 'Provide / Wait for / Read' directives, and compact markdown templates — with no explanatory padding of concepts Claude already knows, matching the score-3 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

It gives concrete executable guidance: exact progress file paths, what to provide and wait for at each stage, full markdown templates with named fields, and an explicit gate ('Do not proceed if the target or assumptions are undefined'), matching the score-3 'fully executable; copy-paste ready' anchor rather than the pseudocode-level score-2 example.

3 / 3

Workflow Clarity

The seven steps are clearly sequenced with explicit validation checkpoints (PASS/FAIL status fields, the Step 0 gating rule, and a dedicated quality-audit step that checks prior stages), matching the score-3 anchor for clear sequence plus explicit validation and checklists; it is not a 2 because checkpoints are explicit rather than implicit.

3 / 3

Progressive Disclosure

No bundle files exist (references/scripts/assets are absent) and the single SKILL.md is well-organized into Overview, Pipeline, per-step Workflow, Progress File Specification, and Key Conventions sections; per the rubric's simple-skill note, well-organized sections with no need for external references can score 3, so this is not the disorganized score-2 case.

3 / 3

Total

12

/

12

Passed

Description

67%Weight 40%Scale 1-3

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 specific and distinctive about the statistical research pipeline, but it omits explicit 'Use when' trigger guidance, leaving the 'when' only implied and capping completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when' clause naming natural user phrasings (e.g., 'Use when the user asks to run a statistical study, design and analyze an experiment, or compare methods with theory') to lift completeness and trigger_term_quality to 3.

Surface one or two plain-language keywords users actually say ('statistical study', 'experiment design', 'compare methods') in the description rather than only in metadata.trigger-keywords.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions ('formal problem formulation, method proposal, theoretical analysis, experimental evaluation, comparison, and final result synthesis'), matching the score-3 anchor for enumerating several distinct concrete actions rather than vague language.

3 / 3

Completeness

It clearly answers 'what' (the full pipeline of stages) but provides no explicit 'when'/'Use when...' guidance, and the rubric caps completeness at 2 when trigger guidance is missing; it is not a 1 because the 'what' is strong and specific.

2 / 3

Trigger Term Quality

The description relies on technical pipeline jargon ('orchestrate', 'theoretical analysis', 'result synthesis') and omits the natural trigger terms a user would actually say, which appear only in metadata.trigger-keywords rather than the description; it is not below 2 because the named stages are domain-relevant, but it lacks common natural variations for a 3.

2 / 3

Distinctiveness Conflict Risk

The niche is clear and specific — a statistical research pipeline requiring formal formulation and theory — making it unlikely to trigger for unrelated skills; it matches the score-3 'clear niche with distinct triggers' anchor rather than the overlapping score-2 example.

3 / 3

Total

10

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
aiming-lab/AutoResearchClaw
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.