CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

flow-spec

NLSpec authoring — use when you need a structured specification from multi-AI research and consensus

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-spec/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.

The skill delivers a highly structured, gate-driven workflow with executable commands and strong error-recovery guidance. Its weaknesses are token-heavy enforcement repetition and a monolithic layout with no bundle files to offload the template and large script blocks.

Suggestions

Trim the redundant enforcement banners and consolidated prohibition restatements into a single 'Non-negotiables' list to reduce token cost.

Move the NLSpec template and the Step 6.5 challenge staging script into reference files (e.g., references/nlspec-template.md, references/challenge.sh) with clearly signaled links.

Define or inline the behavior of sourced helpers (octo_result_launcher_status, octo_result_framed_sections) so the challenge snippet is fully self-contained.

DimensionReasoningScore

Conciseness

The body is dense with actionable bash but padded with redundant enforcement language ("STOP - SKILL ALREADY LOADED", repeated "MANDATORY"/"CANNOT SKIP" banners) and prohibitions restated multiple times (e.g., 'DO NOT substitute with direct research' appears in Steps 4, 5, and Prohibited Actions). This fits 'Mostly efficient but includes some unnecessary explanation or could be tightened'.

3 / 5

Actionability

Provides concrete, mostly copy-paste-ready bash (orchestrate.sh probe, jq receipt validation, challenge staging with error handling) matching 'Mostly executable guidance; concrete code or commands with minor gaps'. Minor gaps: '<project name>' placeholders and sourced functions like octo_result_launcher_status used without definition.

4 / 5

Workflow Clarity

A clearly sequenced 8-step workflow with explicit validation gates (Step 5 receipt check, Step 7 completeness validation), a per-step error-handling section, and feedback loops (challenge failure warns and continues; validation failure blocks progress). This matches 'Clear sequence with explicit validation steps; feedback loops for error recovery'.

5 / 5

Progressive Disclosure

Section headers are clear, but ~470 lines are monolithic in SKILL.md: the NLSpec template and large bash blocks belong in separate reference files, and the single reference (skills/blocks/codex-host-adapter.md) is buried in a blockquote with no organized references section. This fits 'Some structure but could be better organized; content that should be separate is inline'.

3 / 5

Total

15

/

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 is concise, third-person, and explicitly pairs a what with a use-when clause, avoiding fluff and over-claims. Its main weaknesses are thin action coverage and missing natural trigger synonyms like "spec" or "requirements".

Suggestions

Enumerate 2-3 concrete capabilities (e.g., generating NLSpec sections from multi-provider research, adversarial completeness challenge, validation scoring) to lift specificity.

Add natural trigger variations such as "spec", "requirements", or "when starting a new project or feature" to broaden keyword coverage.

Sharpen the 'when' clause with concrete contexts (project kickoff, feature design) rather than the generic 'when you need a structured specification'.

DimensionReasoningScore

Specificity

Names the domain ("NLSpec authoring") and one concrete outcome ("structured specification from multi-AI research and consensus"), equivalent to 'Processes PDF files and extracts content'. It does not list several specific actions, so it falls short of anchor 4.

3 / 5

Completeness

Both what ("NLSpec authoring") and when ("use when you need a structured specification from multi-AI research and consensus") are explicitly present. The 'when' clause lacks concrete trigger contexts (e.g., starting a new project or feature), so it does not reach anchor 5.

4 / 5

Trigger Term Quality

"structured specification" is a phrase users would naturally say, but common variations such as "spec", "requirements", or "write a spec" are missing, matching 'Some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

The "NLSpec" term and multi-AI research framing carve a mostly distinct niche with a clear trigger; minor overlap risk remains with generic spec-writing or planning skills, keeping it below anchor 5.

4 / 5

Total

14

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

nyldn/claude-octopus

Path

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