CtrlK
BlogDocsLog inGet started
Tessl Logo

structured-research-workflow

Use this skill when conducting research on a topic from scratch — literature review, competitive analysis, technical due diligence, or fact-finding. Apply before starting any open-ended research task.

70

Quality

86%

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

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

A lean, well-organized instruction-only workflow that respects token budget and needs no external references. It loses points only on actionability and workflow clarity, where steps stay abstract and lack explicit validation checkpoints.

Suggestions

Add concrete methods or examples to abstract steps — e.g., for 'Search broadly first', list specific source types or query-expansion tactics so guidance is executable rather than directive.

Insert an explicit validation checkpoint, such as a step verifying the original question is answered before synthesis, to convert the implicit 'Flag uncertainty' step into a real feedback loop.

Tighten the most abstract steps ('Filter ruthlessly', 'Read deeply') with one concrete acceptance criterion each so Claude can judge when to proceed.

DimensionReasoningScore

Conciseness

Each step is a terse one-line imperative with a compact rationale and zero concept exposition Claude already knows — every token earns its place.

3 / 3

Actionability

Steps give concrete directives ('Write the specific question', 'Record source URL/DOI at time of reading'), but several remain directive-level abstraction ('Search broadly first') with no executable methods, so it is not fully copy-paste ready.

2 / 3

Workflow Clarity

A clear numbered 7-step sequence is present, but there are no explicit validation checkpoints or feedback loops; step 7 ('Flag uncertainty') is only an implicit checkpoint.

2 / 3

Progressive Disclosure

Under 50 lines with no need for external references, and well organized as a numbered list plus an anti-pattern callout — meeting the rubric's allowance for short, self-contained skills.

3 / 3

Total

10

/

12

Passed

Description

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

A strong, concise description that covers what and when, uses natural trigger terms, names concrete research types, and stays in third person. It is among the better examples in the reference set.

DimensionReasoningScore

Specificity

Names multiple concrete research modalities — 'literature review, competitive analysis, technical due diligence, or fact-finding' — matching the anchor for listing several specific actions.

3 / 3

Completeness

Explicitly states both what it does ('conducting research on a topic from scratch') and when to use it ('Use this skill when...', 'Apply before starting any open-ended research task').

3 / 3

Trigger Term Quality

Uses natural terms a user would actually say — 'research', 'literature review', 'competitive analysis', 'fact-finding' — giving good coverage of common phrasings.

3 / 3

Distinctiveness Conflict Risk

The 'from scratch' framing plus four named research types carve a clear niche unlikely to trigger for unrelated skills, though minor overlap with generic analysis remains.

3 / 3

Total

12

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

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