CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

flow-define

Multi-AI requirements scoping using available external providers (Double Diamond Define phase). Priority triggers: octo define, octo scope, co-define, co-scope. DO NOT use for implementation, research, review/validation, or built-in commands.

Quality

66%

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-define/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 delivers strong actionability and a well-gated execution sequence with real validation and error recovery, making the operational core trustworthy. Its main flaws are severe redundancy (duplicated banner, workflow, and example sections) and a monolithic structure that inlines material better split into reference files.

Suggestions

Remove the duplicated sections — the banner spec in "Visual Indicators", the "How It Works" stages, and the repeated cost estimates — and keep the Execution Contract as the single source of truth to improve conciseness.

Move the fully worked Example 1 and the Problem Definition Format template into a separate reference file, and resolve the unresolved `{{PREAMBLE}}` placeholder, to tighten progressive disclosure.

Reconcile the Stage A orchestrate.sh invocation with the mandated Step 4 command (same arguments and snapshot machinery) so the two paths cannot be confused, and define or drop $USER_REQUEST.

DimensionReasoningScore

Conciseness

The ~780-line body is noticeably padded: the banner spec appears twice (Execution Contract STEP 1 and the "Visual Indicators" section), the "How It Works" stages restate the Execution Contract, cost figures are repeated, a ~100-line fully worked example duplicates the Problem Definition Format template, and version-sensitive notes ("Claude Code v2.1.16+", "v7.16.0+") add time-bound detail that will age.

2 / 5

Actionability

The skill provides concrete, mostly copy-paste-ready bash with traps, fallbacks, recovery commands, exact banner text, and a structured AskUserQuestion specification. Minor gaps keep it from the top anchor: $USER_REQUEST is never defined, and the task-management snippet uses placeholder pseudocode like TaskUpdate({taskId: "..."}).

4 / 5

Workflow Clarity

Seven blocking steps with explicit "DO NOT PROCEED" gates, verification of the synthesis file, per-step error handling, a recovery flow, and a quality checklist are exemplary. However, "Stage A" shows a conflicting simplified orchestrate.sh invocation (single argument) versus the mandated three-argument Step 4 command, creating a minor coherence gap.

4 / 5

Progressive Disclosure

No bundle files (references/, scripts/, assets/) exist, and while plugin-block references like `skills/blocks/engineering-method-selection.md` are clearly signaled one level deep, the monolithic 780-line body inlines content that belongs in separate files (the worked example, the output-format template, the ~40-line provider-check script), and the `{{PREAMBLE}}` placeholder is left unresolved.

3 / 5

Total

13

/

20

Passed

Description

62%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 clearly identifies the skill's niche and includes both positive trigger commands and explicit exclusions, giving it good completeness and distinctiveness. Its weaknesses are trigger terms framed as command invocations rather than natural user phrases, and a thin enumeration of concrete capabilities.

Suggestions

Add natural situational trigger phrases users would actually say (e.g., "define requirements", "clarify scope", "problem definition") alongside the command triggers to improve trigger_term_quality.

Enumerate the concrete actions the skill performs (e.g., clarifies requirements, defines scope, identifies constraints and edge cases) to raise specificity beyond a single core action.

DimensionReasoningScore

Specificity

"Multi-AI requirements scoping using available external providers" names the domain and one core action but does not enumerate multiple concrete capabilities (e.g., clarifying requirements, defining scope, identifying constraints), matching the anchor for domain plus 1-2 concrete actions rather than a list of several specific actions.

3 / 5

Completeness

Both a clear "what" ("Multi-AI requirements scoping using available external providers") and explicit "when" guidance ("Priority triggers: octo define, octo scope...") plus negative boundaries are present, but the "when" is command-based rather than concrete situational trigger phrases, so it does not reach the fully explicit top anchor.

4 / 5

Trigger Term Quality

The triggers "octo define, octo scope, co-define, co-scope" contain relevant keywords but are command invocations rather than natural phrases a user would say, and common variations like "define requirements", "clarify scope", or "problem definition" are missing.

3 / 5

Distinctiveness Conflict Risk

The "Double Diamond Define phase" niche, distinct command triggers, and explicit "DO NOT use for implementation, research, review/validation" exclusions make it mostly distinct, with only minor overlap risk against sibling workflow skills in the same suite.

4 / 5

Total

14

/

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 (783 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

nyldn/claude-octopus

Path

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