CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seo-flow

FLOW framework integration: evidence-led SEO using the Find → Leverage → Optimize → Win loop. Surfaces stage-specific AI prompts from the FLOW knowledge base (41 prompts, CC BY 4.0). Use when user says "FLOW", "FLOW framework", "seo flow", "evidence-led SEO", "find leverage optimize win", or wants stage-specific SEO prompts.

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 well-structured orchestration skill: concrete commands, per-subcommand step sequences, a genuine error-recovery table, and bundle references that match the real file tree exactly with disciplined on-demand loading. The only improvements are trimming the duplicated load-rule statements and clarifying what 'apply each prompt' should produce.

Suggestions

Consolidate the load rules: the Reference Files section repeats what the orchestration steps and runtime-context note already state — merge them into one authoritative section.

Clarify what 'Apply each prompt to the URL or topic' should produce (e.g., a structured finding per prompt) so the analysis step is fully executable without inferring output format.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no SEO concept explanations), but load rules are stated three times (runtime note, orchestration steps, Reference Files section) and the attribution notice appears twice. These minor duplications keep it just below the every-token-earns-its-place score-5 anchor.

4 / 5

Actionability

Guidance is largely executable: exact file paths, the exact sync command ('${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo' run sync_flow.py'), verbatim cross-reference strings, and an explicit 'Always surface exactly 2-3 prompts' rule. 'Apply each prompt to the URL or topic' delegates specifics to the prompt files, leaving a minor gap in what the output should look like.

4 / 5

Workflow Clarity

Every sub-command has a clearly numbered sequence, and the Error Handling table provides explicit feedback loops (auth error → 'gh auth login' then retry; network error → check 'gh api rate_limit'). It lacks proactive validation checkpoints on analysis output, so it fits the score-4 anchor rather than the score-5 anchor with explicit validation steps.

4 / 5

Progressive Disclosure

Verified against the actual bundle: all referenced paths exist and prompt counts match exactly (find=5, leverage=1, optimize=21, win=3, local=11 = 41). References are one hop deep, each with an explicit load condition, load-on-demand is mandated, and the optimize stage uses two-phase disclosure (list filenames, then load only 2-3 selected). This matches the score-5 anchor.

5 / 5

Total

17

/

20

Passed

Description

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

A well-constructed description with an explicit 'Use when' trigger list and a clear statement of what the skill does. Its main weakness is capability specificity: it names the framework and one action (surfacing prompts) rather than enumerating the concrete analyses it enables.

Suggestions

Enumerate 2-3 concrete capabilities in the description (e.g., 'keyword research, backlink strategy, conversion audits') instead of the single generic action 'Surfaces stage-specific AI prompts', to raise specificity.

Add a few more natural trigger variations such as individual stage names ('find stage', 'optimize stage') or 'FLOW prompt library' to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ('evidence-led SEO using the Find → Leverage → Optimize → Win loop') and one concrete action ('Surfaces stage-specific AI prompts from the FLOW knowledge base (41 prompts)'), but does not list several specific capabilities. It sits between the generic score-2 anchor and the several-actions score-4 anchor.

3 / 5

Completeness

Explicitly answers both 'what' (evidence-led SEO via the FLOW loop; surfaces stage-specific AI prompts) and 'when' ('Use when user says...') with concrete quoted trigger phrases. This directly matches the score-5 anchor pattern rather than the score-4 anchor, whose 'when' is less explicit.

5 / 5

Trigger Term Quality

The quoted trigger list ("FLOW", "FLOW framework", "seo flow", "evidence-led SEO", "find leverage optimize win") gives good natural-phrase coverage including the expanded loop wording. A few natural variations (individual stage names, 'FLOW prompts', 'SEO prompt library') are missing, keeping it below the comprehensive score-5 anchor.

4 / 5

Distinctiveness Conflict Risk

'FLOW' and 'FLOW framework' establish a clear niche with distinct triggers, but 'evidence-led SEO' and 'wants stage-specific SEO prompts' could overlap with closely related SEO skills in the same plugin. Mostly distinct with minor overlap risk, fitting the score-4 anchor.

4 / 5

Total

16

/

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: 12 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

AgriciDaniel/claude-seo

Path

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