funnel-analysis-builder
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill funnel-analysis-builderFunnel Analysis Builder - Auto-activating skill for Data Analytics. Triggers on: funnel analysis builder, funnel analysis builder Part of the Data Analytics skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially serving as a placeholder rather than a functional skill description. It provides no concrete capabilities, no meaningful trigger terms beyond the skill name, and no guidance on when Claude should select this skill. The repeated trigger term suggests auto-generated or template content that was never properly filled in.
Suggestions
Add specific capabilities: 'Builds conversion funnels, calculates drop-off rates between stages, identifies bottlenecks in user journeys, visualizes funnel performance metrics.'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user mentions conversion funnels, drop-off analysis, user flow optimization, checkout abandonment, or wants to track progression through multi-step processes.'
Add varied trigger terms users would naturally say: 'conversion funnel', 'drop-off rates', 'user journey', 'checkout flow', 'signup funnel', 'sales pipeline analysis'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Funnel Analysis Builder') without describing any concrete actions. There are no specific capabilities listed like 'create conversion funnels', 'track drop-off rates', or 'visualize user journeys'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. The 'Triggers on' section just repeats the skill name rather than providing meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are the skill name itself repeated twice ('funnel analysis builder, funnel analysis builder'). Missing natural user terms like 'conversion funnel', 'drop-off', 'user flow', 'conversion rates', 'checkout funnel', etc. | 1 / 3 |
Distinctiveness Conflict Risk | While 'funnel analysis' is a somewhat specific domain within data analytics, the lack of detail about what distinguishes this from general analytics skills or other data visualization tools creates moderate overlap risk. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template with no actual funnel analysis content. It claims capabilities without demonstrating any - no SQL examples for funnel queries, no conversion rate calculations, no visualization guidance, and no concrete workflow. The content would be identical if you replaced 'funnel analysis' with any other topic.
Suggestions
Add concrete SQL examples showing funnel query patterns (e.g., step-by-step conversion with window functions or self-joins)
Include a clear workflow: define funnel steps → write conversion query → calculate drop-off rates → visualize results
Provide specific output formats (e.g., expected table schema for funnel data, chart type recommendations)
Remove generic boilerplate sections ('Capabilities', 'Example Triggers') and replace with actionable content like common funnel patterns or validation checks
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about funnel analysis. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, SQL queries, examples, or specific instructions are provided. The content describes what the skill does abstractly but never shows how to actually build a funnel analysis - no schemas, no query patterns, no visualization guidance. | 1 / 3 |
Workflow Clarity | No workflow is defined. 'Provides step-by-step guidance' is claimed but no actual steps are given. There's no sequence for building funnels, no validation checkpoints, and no process to follow. | 1 / 3 |
Progressive Disclosure | The content is a flat, generic template with no meaningful structure. No references to detailed materials, no examples file, no SQL patterns document - just placeholder sections that don't organize any real content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.