CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

octopus-research

Thorough research across multiple sources — use for complex topics needing broad synthesis

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 ./.claude/skills/skill-deep-research/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 strongly operational enforced-execution skill: the five-step workflow is unambiguous, gate-driven, and backed by executable bash with a real validation loop. Its weaknesses are verbosity from repeating the same enforcement contract multiple times and a broken bundle reference (skill-security-framing.md) that leaves the security step unactionable.

Suggestions

State the orchestrate.sh-only execution contract once (e.g., in the HARD-GATE block) and remove the repeated prohibition lists in Step 3, Step 4, and the Error Handling section, which restate the same constraint four times.

Fix or inline the security guidance: skill-security-framing.md does not exist in the skill's bundle (no references/ directory), so either ship that file or inline the URL-validation rules (HTTPS only, no localhost/private IPs) it is meant to provide.

Remove the duplicated banner line ('🟡 Antigravity CLI' / '🧭 Antigravity CLI' both render ${agy_status}) and consider moving the AskUserQuestion payload and banner template to a reference file to slim the main body.

DimensionReasoningScore

Conciseness

The body is mostly efficient procedural content (executable bash, intensity resolution rules), but the orchestrate.sh-only prohibition is restated four or more times ('You MUST call orchestrate.sh via the Bash tool. Do NOT research the topic yourself', 'You are PROHIBITED from: ❌ Researching directly without calling orchestrate.sh', 'This is NOT optional', 'Never fall back to direct research') and the banner duplicates a line ('🟡 Antigravity CLI' and '🧭 Antigravity CLI' both render ${agy_status}). It fits anchor 3 (could be tightened) rather than 2 because no space is spent explaining concepts Claude already knows, and rather than 4 because the redundant enforcement repetition is substantial, not minor.

3 / 5

Actionability

Guidance is nearly fully executable: the Step 3 bash block (mktemp run marker, orchestrate.sh invocation, workflow-result.sh validation, 'cat "$SYNTHESIS_FILE"'), the complete AskUserQuestion payload, and the intensity resolution rules are copy-paste ready, with concrete error paths ('Show logs from ~/.claude-octopus/logs/'). It falls short of anchor 5 on minor gaps: TaskUpdate({taskId: "..."}) is an unresolved placeholder, and the security step points to skill-security-framing.md with no inline guidance; it is above anchor 3 because nothing is pseudocode and commands are complete.

4 / 5

Workflow Clarity

Steps 1-5 are clearly sequenced with explicit blocking gates ('DO NOT PROCEED TO STEP 2 until all questions are answered'), a dedicated validation gate requiring 'a fresh synthesis owned by its invocation in the current host session's results directory', and per-step error recovery with feedback loops (report error, show logs, never substitute). This matches anchor 5's explicit validation steps and error-recovery loops; anchor 4 would require missing or only implicit checkpoints, which is not the case.

5 / 5

Progressive Disclosure

Sections are well organized, but the body instructs 'apply security framing from skill-security-framing.md' while no references/ directory (or that file) exists in the bundle — a dangling, unresolvable reference. Additionally, ~60 lines of template content (the AskUserQuestion payload and banner template) are inlined in a 210-line file, so the single-file exception for short skills does not apply. This fits anchor 3 (references present but not resolvable, content that could be separate is inline) rather than 2, since structure is genuinely good, and rather than 4, since the one reference present cannot be located.

3 / 5

Total

15

/

20

Passed

Description

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

The description correctly answers both 'what' and 'when' and names a recognizable domain, but it stays at a high level of abstraction: no concrete actions or outputs, thin trigger keyword coverage, and a circular 'when' clause. Trigger phrases that would fix this (like 'research this topic', 'investigate how X works') already exist in the frontmatter trigger field but are absent from the description itself.

Suggestions

Add concrete actions and outputs to the description, e.g., 'Runs multi-provider research across external AI providers and produces a synthesis report' instead of the abstract 'thorough research... broad synthesis'.

Replace the circular 'use for complex topics needing broad synthesis' with concrete user phrasings — 'research this topic', 'investigate how X works', 'what are the options for Z' — several of which already exist in the frontmatter trigger field.

Add distinguishing terms (multi-provider, orchestrate.sh, synthesis report) so the description is less likely to be confused with generic research or exploration skills.

DimensionReasoningScore

Specificity

The description names the domain ('Thorough research across multiple sources') but its only actions are the generic 'research' and 'broad synthesis' — no concrete actions or outputs (e.g., what is produced or how). This matches anchor 2 (domain named, actions minimal/generic); it is above anchor 1 because a specific domain is named, and below anchor 3 because neither 'research' nor 'synthesis' is a concrete action like 'extracts content'.

2 / 5

Completeness

Both parts are explicitly stated: what ('Thorough research across multiple sources... broad synthesis') and when ('use for complex topics needing broad synthesis'). The when clause is present but generic and circular — it restates 'broad synthesis' rather than giving concrete trigger conditions — fitting anchor 4 (both present, when could be more explicit); not 3 because the when is explicitly stated rather than merely implied, not 5 because there are no concrete trigger phrases like 'when the user asks to research a topic'.

4 / 5

Trigger Term Quality

'Thorough research across multiple sources' supplies the relevant keyword 'research', and 'use for complex topics' gives a rough usage cue, but common natural variations users would say — 'investigate', 'look into', 'explore', 'deep dive' — are missing (several of which already exist in the frontmatter trigger field). This fits anchor 3 (some relevant keywords, missing variations/synonyms); not 2 because more than one domain-relevant term is present, not 4 because coverage is thin with no synonyms.

3 / 5

Distinctiveness Conflict Risk

'complex topics needing broad synthesis' carves a rough niche (multi-source research/synthesis) but 'research' is a crowded trigger domain and nothing in the description distinguishes it from generic research or exploration skills. This fits anchor 3 (somewhat specific, could overlap with similar skills); not 2 because it is more specific than 'helps with documents'-level breadth, not 4 because no distinctive triggers (e.g., multi-provider, synthesis report) are named.

3 / 5

Total

12

/

20

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.

Validation — 15 / 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

nyldn/claude-octopus

Path

.claude/skills/skill-deep-research/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.