CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

70

Quality

88%

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

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.

An exemplary orchestration skill body: per-command numbered workflows, exact file paths with accurate on-disk counts, a smart selective-loading policy for the 21-prompt optimize stage, and a concrete error-recovery table. The only deductions are minor — a duplicated load instruction/attribution text and a sync-script reference that does not resolve within the provided bundle.

Suggestions

State the flow-framework.md load-on-activation instruction once — it currently appears in both the 'Runtime context' note and the 'Reference Files' section.

Resolve or qualify the sync reference: the body points to ${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo (sync_flow.py) but no scripts/ directory ships in this skill bundle; either bundle the script or note that it lives at the plugin root so the reference is verifiable.

DimensionReasoningScore

Conciseness

The body is a tight, table-driven orchestration guide with no explanations of concepts Claude already knows and an explicit anti-dump policy ("The optimize stage has 21 prompts. Dumping all 21 is noise"). Minor trimming is possible: the instruction to load references/flow-framework.md on every activation is stated twice ("Runtime context" and "Reference Files"), and the attribution text appears both inline and again verbatim in its own section — fitting the 'efficient; minor instances that could be trimmed' anchor rather than the every-token-earns-its-place anchor at 5.

4 / 5

Actionability

Guidance is fully executable: exact per-subcommand numbered sequences, exact file paths per stage, a copy-paste sync invocation ("${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run sync_flow.py), concrete cross-reference syntax (e.g., "see /seo cluster <seed-keyword>"), and a priority-ordered prompt-selection rule (industry vertical → prior skill output → URL signals). For an orchestration skill this is copy-paste-ready command guidance covering all cases, matching the top anchor.

5 / 5

Workflow Clarity

Every sub-command has a clearly sequenced numbered workflow, and the Error Handling table provides explicit recovery loops (missing reference → "Run /seo flow sync"; network error → check "gh api rate_limit"; auth error → "Run gh auth login then retry"). The optimize flow adds a checkpoint constraint ("Always surface exactly 2-3 prompts. State which prompts you chose and why"), matching the anchor for clear sequences with explicit validation steps and feedback loops for error recovery.

5 / 5

Progressive Disclosure

The body is overview-only with a dedicated Reference Files section giving per-reference load conditions ("load on every /seo flow activation", "load when citing studies", "load selectively") and an explicit on-demand policy; all referenced paths and prompt counts verified against the actual bundle (find=5, leverage=1, optimize=21, win=3, local=11, total 41 — all exact). The one gap: the sync workflow references ${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo and sync_flow.py, but no scripts/ directory exists in the skill bundle, leaving that referenced path unverifiable — a minor organization gap that keeps it below the top anchor.

4 / 5

Total

18

/

20

Passed

Description

86%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 strong description: third-person, concrete about the FLOW loop and the 41-prompt knowledge base, with an exemplary explicit trigger clause covering multiple natural phrasings. The main weakness is that only one concrete capability (surfacing prompts) is stated — the stage-level analyses and the sync capability go unnamed — leaving the 'what' slightly under-specified relative to the excellent 'when'.

Suggestions

Enumerate one or two concrete stage-level capabilities in the description (e.g., keyword research and gap analysis, backlink strategy, GBP/local optimization) so the 'what' lists several specific actions rather than the single 'surfaces stage-specific AI prompts' action.

Briefly mention the sync capability (pulling the latest prompts from the FLOW repo) so users know the prompt library can be refreshed, closing the coverage gap without adding verbosity.

DimensionReasoningScore

Specificity

"Surfaces stage-specific AI prompts from the FLOW knowledge base (41 prompts, CC BY 4.0)" names the domain (evidence-led SEO) and one concrete action framed by the Find → Leverage → Optimize → Win loop, but does not enumerate the stage-level analyses or the sync capability — matching the anchor for 1-2 concrete actions that is not comprehensive. It falls short of 4 because only one specific action (surfacing prompts) is actually listed.

3 / 5

Completeness

It clearly answers both: what ("evidence-led SEO using the Find → Leverage → Optimize → Win loop", "Surfaces stage-specific AI prompts ... (41 prompts)") and when ("Use when user says 'FLOW', 'FLOW framework', 'seo flow', 'evidence-led SEO', 'find leverage optimize win', or wants stage-specific SEO prompts"). This matches the anchor for explicitly answering both what AND when with concrete trigger phrases, and is in third-person voice throughout.

5 / 5

Trigger Term Quality

The explicit clause "Use when user says 'FLOW', 'FLOW framework', 'seo flow', 'evidence-led SEO', 'find leverage optimize win', or wants stage-specific SEO prompts" covers comprehensive natural phrasings with synonyms and variations a user would actually say. No common natural term for this skill is missing, so it exceeds the 'a few natural terms missing' anchor at 4.

5 / 5

Distinctiveness Conflict Risk

Triggers like "FLOW", "FLOW framework", and "find leverage optimize win" are highly distinctive, giving a clear niche with minimal conflict for those terms. However "wants stage-specific SEO prompts" and "evidence-led SEO" are broad enough to overlap with closely related SEO skills (the body cross-references /seo cluster, /seo backlinks, /seo content siblings), matching the 'mostly distinct; minor overlap risk' anchor rather than the minimal-risk anchor at 5.

4 / 5

Total

17

/

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