CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

funnel-flow-architecture

Architecting cross-tool conversion flows that match audience and stage. Landing page to lead magnet to nurture sequence to offer to advanced funnels. Honest about silo-funnels (every tool standalone), kitchen-sink-funnels (every audience squeezed through one path), and matched-funnels (architecture matched to audience-and-stage) patterns. Triggers on funnel design, conversion architecture, marketing funnel, growth funnel, lifecycle architecture, nurture sequence design, multi-tool funnel orchestration. Also triggers when the team's growth tools are working individually but not together, when audience segments share one nurture path, or when a funnel is being architected from scratch.

Quality

79%

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/funnel-flow-architecture/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 architecture skill with a clear keystone framing, concrete diagnostic tools (litmus test, 12-consideration framework, refine/redesign criteria), and exemplary one-level-deep reference signaling to 9 existing detail files. The main weaknesses are repetition of the three-pattern framing, re-explanation of concepts Claude already knows, and the absence of an explicit end-to-end workflow or worked architecture template.

Suggestions

Collapse the duplicated silo/kitchen-sink/matched-funnel definitions into a single keystone section and trim the second closing section, which restates the intro nearly verbatim.

Convert the topic sections into one explicitly ordered design/audit procedure (segment -> map entry points -> map tools -> design sequences -> integrate data flow -> measure -> iterate) so the workflow sequence is stated, not inferred.

Drop or compress explanations of generic concepts (common entry-point types, awareness/consideration/decision stage definitions) that Claude already knows, keeping only the skill's own framing.

DimensionReasoningScore

Conciseness

Sections are mostly efficient pointer-style with detail deferred to references, but the silo/kitchen-sink/matched-funnel definitions are repeated in the keystone framing and again in the closing, generic concepts (entry-point types, awareness/consideration/decision stages) are re-explained, and two closing sections pad the ending.

3 / 5

Actionability

Concrete instruction-only guidance throughout: the litmus test ('Pick a recent visitor... can the team explain which segment...'), the refine-vs-redesign criteria lists, the worked entry-point routing example, and the 12-consideration framework. Falls short of 5 because no segmentation-matrix template or complete worked architecture example is provided.

4 / 5

Workflow Clarity

Sections progress logically from segmentation through entry points, tool mapping, sequences, data flow, measurement, and iteration, and the 12-consideration framework plus litmus test and closing diagnostic questions serve as explicit checkpoints. The step ordering is inferable rather than stated as one explicit numbered workflow.

4 / 5

Progressive Disclosure

Every topic section signals 'Detail in [references/...]', all 9 referenced files exist and are one level deep, and a consolidated reference index aids navigation. The body is heavier than a lean overview, carrying framing content (pattern definitions, anti-pattern summaries) duplicated across sections.

4 / 5

Total

15

/

20

Passed

Description

83%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 that clearly and explicitly states both what the skill does and when to use it, with concrete trigger phrases and scenario-based triggers. Keyword coverage is good with natural synonyms; the main gaps are a few missing common variants ('conversion funnel', 'email nurture') and framing language where concrete actions would be stronger.

Suggestions

Add common trigger variants such as 'conversion funnel', 'lead funnel', or 'email nurture sequence' to broaden natural keyword coverage.

Replace the framing clause 'Honest about silo-funnels...' with a concrete action verb form (e.g., 'Diagnoses silo-funnel vs kitchen-sink-funnel vs matched-funnel patterns') to sharpen the capability list.

DimensionReasoningScore

Specificity

'Architecting cross-tool conversion flows that match audience and stage. Landing page to lead magnet to nurture sequence to offer to advanced funnels' names the domain and enumerates concrete scope, with concrete diagnostic scenarios ('when the team's growth tools are working individually but not together'). Falls short of 5 because 'Honest about... patterns' is framing rather than an action, and the action verbs are otherwise limited to architecting/matching.

4 / 5

Completeness

Explicitly answers both what ('Architecting cross-tool conversion flows that match audience and stage...') and when ('Triggers on... Also triggers when... a funnel is being architected from scratch') with concrete trigger phrases.

5 / 5

Trigger Term Quality

'Triggers on funnel design, conversion architecture, marketing funnel, growth funnel, lifecycle architecture, nurture sequence design, multi-tool funnel orchestration' provides good natural keyword coverage with synonyms. Falls short of 5 because common user phrasings like 'conversion funnel', 'lead funnel', or 'email nurture' are missing.

4 / 5

Distinctiveness Conflict Risk

'Cross-tool conversion flows' and 'multi-tool funnel orchestration' carve a clear niche with distinct triggers, but the description shares vocabulary (lead magnet, landing page, nurture sequence) with closely related sister skills, creating minor overlap risk.

4 / 5

Total

17

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

rampstackco/claude-skills

Path

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