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.
32
0%
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
0%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 template placeholder with no substantive content. It repeats the skill name as its own trigger term, provides no concrete actions or capabilities, and lacks any explicit guidance on when Claude should select this skill. It would be nearly useless for skill selection among multiple available skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Builds multi-step conversion funnels, calculates stage-by-stage drop-off rates, identifies bottlenecks in user journeys, and visualizes funnel metrics.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about conversion funnels, drop-off analysis, funnel visualization, user journey stages, conversion rates, or step-by-step funnel metrics.'
Remove the redundant repeated trigger term and replace with diverse natural language variations users would actually say, such as 'conversion funnel', 'funnel chart', 'drop-off rate', 'purchase funnel', 'signup funnel'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('funnel analysis') but describes no concrete actions. There are no specific capabilities listed like 'build conversion funnels', 'calculate drop-off rates', or 'visualize funnel stages'. It only states it's an 'auto-activating skill for Data Analytics' which is vague. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause. The 'Triggers on' line is just the skill name repeated, not meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'funnel analysis builder' repeated twice. There are no natural keyword variations a user might say such as 'conversion funnel', 'drop-off analysis', 'funnel visualization', 'user journey', 'conversion rates', or 'funnel steps'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is too generic to be distinguishable. 'Data Analytics' is extremely broad and could overlap with many analytics-related skills. Without specific actions or clear scope boundaries, this could easily conflict with other data analysis skills. | 1 / 3 |
Total | 4 / 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 essentially a placeholder template with no actual content. It contains no actionable instructions, no code examples, no funnel analysis concepts, and no workflow guidance. Every section repeats the phrase 'funnel analysis builder' without teaching Claude anything it doesn't already know.
Suggestions
Add concrete SQL examples for building funnel queries (e.g., step-by-step conversion funnels using window functions or sequential event joins with specific schema examples).
Define a clear workflow: identify funnel stages → write conversion queries → calculate drop-off rates → visualize results, with specific code at each step.
Include at least one complete, executable example showing a funnel analysis from raw event data to final output (e.g., a signup-to-purchase funnel with sample SQL and expected output format).
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill rather than teaching the task—these waste tokens without adding value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual knowledge or instructions. Every section restates the same vague information about 'funnel analysis builder' without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no SQL queries, no funnel stage definitions, no code examples, no specific commands, no data schemas. The content describes rather than instructs, offering only vague promises like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive structure with no meaningful organization. There are no references to detailed materials, no links to examples or advanced topics, and the sections are redundant rather than progressively informative. | 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
4dee593
- 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.