CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

flow-discover

Multi-AI research using available external providers (Double Diamond Discover phase)

Quality

73%

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 ./skills/flow-discover/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The content is a well-engineered orchestration contract: executable bootstrap and root-resolution blocks, a strictly ordered four-phase workflow with explicit stop conditions and validation gates, and a clean one-level reference structure. Its only flaws are mild repetition around run-ID preservation and a dangling second-level reference from security.md to a file not shipped in the bundle.

DimensionReasoningScore

Conciseness

The body is dense, imperative, and free of concepts Claude already knows; both bash blocks carry real logic. Minor repetition slightly pads it: run-ID/literal-assignment preservation is restated in three places ("Preserve these printed literal assignments...", "use the same literal run ID in every child prompt", "Include its literal assignment in each new shell invocation") and compaction handling appears twice, which keeps it below the every-token-earns-its-place anchor 5.

4 / 5

Actionability

Both bash blocks are complete and executable (root resolution with fallbacks, bootstrap generating RUN_ID via /dev/urandom, state-manager and handoff calls), and every phase names exact scripts and subcommands ("build-fleet.sh", "orchestrate.sh probe-single", "orchestrate.sh agent-summary") plus concrete helpers ("validate_external_url", "transform_twitter_url", "wrap_untrusted_content"). This is copy-paste-ready guidance covering the common path.

5 / 5

Workflow Clarity

Four phases are numbered and ordered (prepare → dispatch → synthesize → complete), each bound to a named resource with explicit stop conditions ("Stop on a missing resource", "stop if neither source resolves", "Do not report completion when dispatch, evidence, or presentation is missing"), explicit validation ("Wait for all dispatched agents", "at least two usable provider outputs", "Verify a nonempty synthesis"), and a recovery path ("If the saved values are unavailable, stop and recover the task context"). Checkpoints and error handling match the top anchor.

5 / 5

Progressive Disclosure

The body is a lean overview that clearly signals six one-level-deep references, all of which exist in the bundle (prepare.md, dispatch.md, synthesize.md, complete.md, guidance.md, security.md) with their purpose stated inline. However, security.md:49 points to "skill-security-framing.md" for "complete documentation", a second-level reference that is absent from the bundle — a dangling nested pointer that keeps this below anchor 5.

4 / 5

Total

18

/

20

Passed

Description

48%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 is concise and identifies a distinct niche (multi-AI research during the Double Diamond Discover phase), but it names no concrete capabilities and relies on a parenthetical phase label instead of explicit "Use when..." trigger guidance. It reads more like a title than an invocation-oriented description.

Suggestions

List 2-3 concrete actions in the description, e.g. "Dispatch parallel research across multiple AI providers, collect and verify outputs, and synthesize cited findings".

Add an explicit trigger clause such as "Use when the user requests multi-model or multi-AI research, wants several providers compared, or begins the Discover phase of a Double Diamond workflow".

Include natural synonyms users would say (multi-model research, parallel AI research, compare providers) to improve trigger-term coverage beyond the jargon-adjacent "Multi-AI".

DimensionReasoningScore

Specificity

"Multi-AI research using available external providers" names the domain but the only action is the generic verb "research"; no concrete actions (dispatch, probe, synthesize, cite) are listed. It sits between the vague anchor 1 and the "domain plus 1-2 concrete actions" of anchor 3, matching anchor 2 ("Processes PDF files"-level generality).

2 / 5

Completeness

The "what" is stated (multi-AI research via external providers) but the "when" exists only as the terse parenthetical "(Double Diamond Discover phase)" with no "Use when..." clause or equivalent explicit trigger guidance, capping this dimension at 3 per the judging guidelines. Anchor 4 is not reached because the when-portion is not an explicit usage clause.

3 / 5

Trigger Term Quality

"research" and "Double Diamond Discover phase" are relevant keywords a user in this workflow would plausibly say, but common variations like "multi-model", "parallel research", "search multiple AIs", or provider names are absent. It is noticeably above the single-generic-keyword anchor 2 but lacks the synonym coverage of anchor 4.

3 / 5

Distinctiveness Conflict Risk

The combination of "Multi-AI", "external providers", and "(Double Diamond Discover phase)" carves out a fairly distinct niche with clear phase-specific triggers. Minor overlap risk remains with closely related research/orchestration skills and sibling Double Diamond phase skills, keeping it below anchor 5.

4 / 5

Total

12

/

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

14

/

16

Passed

Repository

nyldn/claude-octopus

Path

skills/flow-discover/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.