funnel-analysis-builder
Funnel Analysis Builder - Auto-activating skill for Data Analytics. Triggers on: funnel analysis builder, funnel analysis builder Part of the Data Analytics skill category.
34
Quality
3%
Does it follow best practices?
Impact
88%
1.04xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/12-data-analytics/funnel-analysis-builder/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a placeholder with no substantive content. It only states the skill name, repeats it as a trigger, and mentions a broad category. It completely fails to describe what the skill does, what specific capabilities it offers, or when Claude should select it over other analytics skills.
Suggestions
Add specific actions the skill performs, e.g., 'Builds conversion funnels, calculates drop-off rates between stages, identifies bottlenecks in user journeys, visualizes funnel metrics'
Add a 'Use when...' clause with natural trigger terms like 'conversion funnel', 'drop-off analysis', 'user journey stages', 'funnel visualization', 'conversion rates'
Include context about data inputs (e.g., 'from event data, user sessions, or transaction logs') to distinguish from other analytics skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Funnel Analysis Builder') without describing any concrete actions. There are no verbs indicating what the skill actually does - no mention of creating funnels, analyzing conversion rates, visualizing drop-offs, or any specific capabilities. | 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 is just the skill name repeated, not meaningful trigger conditions. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('funnel analysis builder, funnel analysis builder'). This is redundant and misses natural user phrases like 'conversion funnel', 'drop-off analysis', 'user journey', 'conversion rates', or 'funnel visualization'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'funnel analysis' is a somewhat specific domain, the lack of detail about what distinguishes this from general data analytics or other analysis skills creates moderate conflict risk. The category mention 'Data Analytics' is too broad to differentiate. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template with no substantive content. It describes what a funnel analysis skill should do but provides zero actionable guidance, code examples, SQL patterns, or workflow steps. The content is entirely generic boilerplate that could apply to any skill topic.
Suggestions
Add concrete SQL examples showing funnel query patterns (e.g., conversion between steps, drop-off analysis, cohort funnels)
Include a clear workflow: define funnel steps → write conversion query → visualize results → identify drop-off points
Provide specific funnel metrics and calculations (conversion rate formulas, time-between-steps analysis)
Remove generic boilerplate sections ('Capabilities', 'Example Triggers') and replace with executable code and real examples
| 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. | 1 / 3 |
Workflow Clarity | No workflow steps are defined. Claims to provide 'step-by-step guidance' but includes zero actual steps. No validation checkpoints or process sequence for building funnel analyses. | 1 / 3 |
Progressive Disclosure | No references to detailed documentation, examples, or related files. The content is a shallow placeholder with no structure for discovery or navigation to deeper materials. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
0c08951
- 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.