CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

89%

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

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 architecture skill with a clear overview, strong progressive disclosure into one-level-deep reference files, and concrete actionable guidance including a sequenced 12-consideration framework. The main weakness is mild reiteration of the core silo/kitchen-sink/matched framing across multiple sections and two closings, which slightly dilutes token efficiency.

Suggestions

Consolidate the duplicated silo/kitchen-sink/matched framing: define it once in its dedicated section and reference it from the anti-patterns section rather than restating the definitions, and merge the two 'Closing' sections into one.

Provide an inline fill-in segment x stage matrix template (9-15 cells) so the practitioner can produce the architecture artifact directly rather than reconstructing it from prose.

Tighten the intro paragraphs (lines 13-21), which re-explain the 'tools vs architecture' distinction already covered by the keystone framing section, to reduce reiteration.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes audience intelligence, but the silo/kitchen-sink/matched framing is restated across the intro, the dedicated section, the anti-patterns section, and two separate 'Closing' sections, which is mild reiteration rather than essential new content.

4 / 5

Actionability

Concrete, specific guidance throughout (3-5 audiences x 3 stages = 9-15 cells, six entry points with routing logic, the B2B SaaS pricing worked example, tool-to-stage mapping, a 12-consideration checklist); minor gap is the absence of any inline fill-in matrix/template, though the skill is instruction-only so missing code is not penalized.

4 / 5

Workflow Clarity

A clear sequenced 12-consideration framework for designing or auditing, an explicit 'When to use' entry condition set, and an 'If required data is unavailable' gap-stating checkpoint; no explicit validate-fix-retry loop is present, but this is design work rather than a destructive/batch operation so the cap-3 rule does not apply.

4 / 5

Progressive Disclosure

SKILL.md is a clear overview with each major section ending in a well-signaled one-level-deep 'Detail in references/X.md' link; all 9 referenced files exist and reference only siblings (no 2+ level nesting), and a bottom 'Reference files' index aids navigation.

5 / 5

Total

17

/

20

Passed

Description

100%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, third-person description that concretely names the domain, enumerates comprehensive natural trigger terms, and cleanly separates this skill from the five sibling tool-design skills. It fully answers both what the skill does and when to invoke it.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions spanning the funnel architecture domain ('Landing page to lead magnet to nurture sequence to offer to advanced funnels', 'audience-and-stage segmentation, entry-point architecture, tool-to-funnel mapping, nurture sequence architecture, cross-tool data flow') with comprehensive coverage.

5 / 5

Completeness

Explicitly answers both 'what' ('Architecting cross-tool conversion flows that match audience and stage') and 'when' ('Triggers on...' plus 'Also triggers when the team's growth tools are working individually but not together...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases a growth lead would actually say: 'funnel design, conversion architecture, marketing funnel, growth funnel, lifecycle architecture, nurture sequence design, multi-tool funnel orchestration' plus situational triggers.

5 / 5

Distinctiveness Conflict Risk

Clear niche ('cross-tool conversion flows') that explicitly distinguishes itself from the 5 sister skills it orchestrates ('those skills zoom into specific tool design, this skill zooms out'), giving minimal conflict risk.

5 / 5

Total

20

/

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.

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