Content
0%Scale 1-3Reviews 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 persona description or role profile rather than an actionable skill document. It lists dozens of business analysis topics and capabilities without providing any concrete code, templates, frameworks, or executable guidance. The content is extremely verbose, explaining concepts Claude already understands, while failing to deliver the specific, actionable instructions that would actually help Claude perform business analysis tasks.
Suggestions
Replace the extensive capability listings with 2-3 concrete, executable examples (e.g., a Python script for cohort analysis, a SQL query template for churn prediction, a KPI dashboard specification template).
Add specific workflow sequences with validation checkpoints for common tasks like 'building a revenue dashboard' or 'running an A/B test analysis', including what to verify at each step.
Create actual bundle files (e.g., resources/implementation-playbook.md, resources/kpi-templates.md, resources/sql-patterns.md) with detailed reference material, and keep SKILL.md as a concise overview pointing to them.
Remove the 'Capabilities', 'Behavioral Traits', 'Knowledge Base', and 'Example Interactions' sections entirely — these describe what Claude should be rather than teaching Claude how to do specific tasks.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose and padded with content Claude already knows. The massive 'Capabilities' section is essentially a resume listing topics like 'Advanced dashboard creation with Tableau, Power BI, Looker' and 'Machine learning for predictive analytics' — none of which teach Claude anything actionable. The 'Behavioral Traits', 'Knowledge Base', and 'Example Interactions' sections add further bloat without providing executable guidance. | 1 / 3 |
Actionability | The skill contains zero concrete code, commands, templates, or executable examples. It is entirely descriptive — listing capabilities and topics rather than providing specific steps, formulas, SQL queries, Python snippets, dashboard configurations, or any copy-paste-ready artifacts. The 'Response Approach' is a generic 8-step process with no specifics. | 1 / 3 |
Workflow Clarity | The 'Response Approach' lists 8 high-level steps but they are vague abstractions ('Execute comprehensive analysis with statistical rigor') with no validation checkpoints, no error handling, no feedback loops, and no concrete sequencing. There is no guidance on what to do when data quality is poor, when analysis fails, or how to verify results. | 1 / 3 |
Progressive Disclosure | The skill references `resources/implementation-playbook.md` but no bundle files are provided, making this a dead reference. The content is a monolithic wall of bullet-point lists with no meaningful structure separating overview from detail. All the capability listings are inline rather than organized into navigable reference files. | 1 / 3 |
Total | 4 / 12 Passed |