CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

flow-develop

Multi-AI implementation using available external providers (Double Diamond Develop phase). DO NOT use for simple code edits, reading/reviewing code, built-in commands, or trivial single-file changes.

Quality

60%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/flow-develop/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 skill is strong on executable commands and mandatory validation gates, but it is severely bloated: the same context-detection, banner, and step-sequence content is restated three times with conflicting step numbering, and hundreds of lines of examples and checklists are inlined instead of moved to reference files. Consolidating to a single authoritative step sequence and offloading examples/banners to bundle files would improve both conciseness and workflow clarity.

Suggestions

Collapse the three restatements of the workflow (EXECUTION CONTRACT, 'How It Works', 'Implementation Instructions') into one authoritative numbered sequence, and make the later sections cross-reference it instead of renumbering steps.

Deduplicate the context-detection indicators and provider banners — keep one banner template and one indicator list — and remove the ASCII-art and 'Visual Indicators' repetition.

Move the long worked examples (authentication/API endpoint usage), subtype supplement tables, and checklists into a references/ bundle file with clearly signaled one-level links, keeping SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

The ~800-line body is heavily padded with duplication: the Dev/Knowledge context indicators appear verbatim twice ("Deliverable terms: 'PRD', 'proposal'..." in EXECUTION CONTRACT Step 1 and again under 'MANDATORY: Context Detection'), the provider banner is rendered in three near-identical variants (Steps 2, 'Output Context-Aware Banner', and 'Visual Indicators'), and the workflow steps are renumbered and restated three times (EXECUTION CONTRACT Steps 1-7, 'How It Works' Steps 1-5, 'Implementation Instructions' Steps 1-6). This matches 'noticeably verbose; several unnecessary explanations or padded sections' (2) — not 1, since it does not explain basic concepts Claude already knows, but the redundancy wastes a large share of the token budget.

2 / 5

Actionability

Most guidance is executable: exact bash invocations with full fallback chains ("bash \"$OCTO_ROOT/scripts/helpers/feature-workflow.sh\" boundary develop \"${OCTOPUS_FEATURE:-}\""), a complete Step 4 run/validation block including marker and report handling, concrete subtype supplement texts ("Help text via --help flag. Meaningful exit codes (0 success, 1 user error, 2 system error)"), and a worked implementation-plan example. It falls short of 5 because some blocks are placeholders rather than copy-paste ready ("orchestrate.sh develop \"<user prompt>...\"", the Agent(...) and TaskCreate(...) pseudo-calls), matching 'mostly executable guidance; concrete code or commands with minor gaps' (4).

4 / 5

Workflow Clarity

A clear 7-step mandatory sequence with validation checkpoints exists (Steps 4-5 validate the synthesis report; 'If validation fails: 1. Report error... 4. DO NOT substitute with direct implementation'; post-develop checkpoint requires fresh tests to pass), so validation is not the weak point. However, the body then repeats two conflicting step numberings — 'How It Works' redefines Step 1 as invoking orchestrate.sh (contradicting the contract's Step 4) and 'Implementation Instructions' lists its own Steps 1-6, while the second banner block shows a different provider list (no 🧭 line, adds session ID) — leaving the model to reconcile which sequence governs. This sits between 'sequence present but checkpoints missing or implicit' (3) and 'clear sequence with most checkpoints present' (4); the duplication and contradiction pull it to 3.

3 / 5

Progressive Disclosure

The body has section headers and does point to external materials ("Load `skills/blocks/engineering-method-selection.md`", "For host tool equivalents, see `skills/blocks/codex-host-adapter.md`") plus template includes ({{PREAMBLE}}, {{VISUAL_INDICATORS}}, {{QUALITY_GATES}}), but no bundle files ship with the skill (no references/, scripts/, or assets/ exist), so those references are not verifiable from the skill itself. Meanwhile ~800 lines of material that clearly belongs in separate files (usage examples, subtype tables, banner templates, checklists) are inlined. This matches 'some structure but could be better organized; references present but not clearly signaled' (3) — not 2 because headers and one-level references do exist, not 4 because the bulk of detail content is inline rather than split out.

3 / 5

Total

12

/

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 has a clear, distinct 'what' and good negative boundary guidance, but it lacks any positive 'use when' trigger phrase and names only one concrete capability. Adding a positive trigger clause and one or two more concrete actions would lift completeness and trigger-term quality.

Suggestions

Add a positive trigger clause, e.g. "Use when the user asks to build, implement, or develop a feature or deliverable and multi-provider analysis is wanted".

Name one or two concrete workflow actions beyond 'implementation' (e.g., 'generates and synthesizes multiple implementation approaches and presents a plan').

Include natural synonyms such as "build", "develop", and "feature" so users' phrasing matches the description.

DimensionReasoningScore

Specificity

Quotes: "Multi-AI implementation using available external providers (Double Diamond Develop phase)" — it names the domain (multi-AI orchestration, Develop phase) and one concrete action (multi-AI implementation), but coverage of capabilities stops there; the rest of the description is exclusions ("DO NOT use for simple code edits, reading/reviewing code, built-in commands, or trivial single-file changes"), not actions. This matches the anchor 'names domain and 1-2 concrete actions, but not comprehensive' (3), not score 2 because the action named is specific rather than generic, and not score 4 because it never lists what the workflow actually does (synthesize approaches, quality gates, present an implementation plan).

3 / 5

Completeness

The 'what' is clear ("Multi-AI implementation using available external providers"), but the 'when' is expressed only as exclusions ("DO NOT use for...") with no 'Use when...' clause or equivalent positive trigger guidance. Per the judging guidelines, a missing 'Use when...' clause caps completeness at 3, matching the anchor 'has a clear what but when is missing or only weakly implied'. It does not reach 4 because the negative list leaves the user to infer when the skill actually applies.

3 / 5

Trigger Term Quality

Relevant keywords present: "implementation", "code edits", "reading/reviewing code", "single-file changes" — but common natural phrases users would say when they need this skill ("build a feature", "implement X", "develop") are missing, and all trigger language is negative (when NOT to use) rather than positive. This fits 'some relevant keywords but missing common variations or synonyms' (3); it is above score 2 ('one or two generic keywords') because the terms are domain-relevant, and below score 4 because there is no positive trigger phrasing at all.

3 / 5

Distinctiveness Conflict Risk

The niche is fairly distinct — "Multi-AI implementation using available external providers (Double Diamond Develop phase)" plus explicit exclusions for "simple code edits, reading/reviewing code, built-in commands, or trivial single-file changes" separates it from general coding skills. This fits 'mostly distinct; minor overlap risk with closely related skills' (4); it is below 5 because "implementation" is broad and other implementation/build workflows in the same plugin family could still compete for the same prompts.

4 / 5

Total

13

/

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

skill_md_line_count

SKILL.md is long (822 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

nyldn/claude-octopus

Path

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