business-analyst
tessl i github:sickn33/antigravity-awesome-skills --skill business-analystMaster modern business analysis with AI-powered analytics, real-time dashboards, and data-driven insights. Build comprehensive KPI frameworks, predictive models, and strategic recommendations. Use PROACTIVELY for business intelligence or strategic analysis.
Activation
50%The description attempts to cover business analysis capabilities but relies heavily on buzzwords ('AI-powered', 'data-driven', 'Master modern') that add little discriminative value. While it includes a trigger clause, the guidance is too broad to help Claude distinguish this skill from related analytics or data skills. The description would benefit from more concrete actions and specific user-facing trigger terms.
Suggestions
Replace buzzwords with concrete actions (e.g., 'Calculate ROI, analyze revenue trends, build financial forecasts' instead of 'AI-powered analytics, data-driven insights')
Expand the 'Use when...' clause with specific trigger terms users would say: 'Use when user mentions business metrics, revenue analysis, market trends, competitive analysis, or asks for executive summaries'
Add file types or deliverables to increase distinctiveness (e.g., 'business reports, executive presentations, quarterly reviews')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names domain (business analysis) and some actions (KPI frameworks, predictive models, strategic recommendations), but uses vague buzzwords like 'AI-powered analytics' and 'data-driven insights' without concrete specifics on what actions are actually performed. | 2 / 3 |
Completeness | Has a 'what' (analytics, dashboards, KPI frameworks) and includes 'Use PROACTIVELY for...' which provides some trigger guidance, but the 'when' is vague ('business intelligence or strategic analysis') rather than explicit user-facing triggers. | 2 / 3 |
Trigger Term Quality | Includes some relevant terms like 'business intelligence', 'strategic analysis', 'KPI', 'dashboards', but missing common user variations like 'metrics', 'reports', 'forecasting', 'business metrics', or specific file types users might mention. | 2 / 3 |
Distinctiveness Conflict Risk | Terms like 'analytics', 'dashboards', and 'data-driven insights' could easily overlap with data science, reporting, or general analytics skills. 'Business analysis' is somewhat distinctive but not clearly differentiated from adjacent domains. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
20%This skill content functions more as a persona description or job posting than an actionable skill guide. It extensively lists capabilities Claude already has without providing concrete methods, code examples, or specific workflows. The content would benefit from dramatic reduction and replacement with executable examples and specific analytical frameworks.
Suggestions
Replace capability lists with 2-3 concrete, executable examples showing actual analysis workflows (e.g., a complete cohort analysis code snippet with sample output)
Add specific tool commands or code for at least one analytics platform (e.g., SQL queries for KPI calculations, Python code for churn prediction)
Move the extensive capability and knowledge lists to a reference file, keeping only a concise overview in the main skill
Add validation checkpoints to the Response Approach (e.g., 'Verify data quality before proceeding: check for nulls, outliers, date ranges')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive lists of capabilities, knowledge bases, and behavioral traits that Claude already possesses. The content reads like a job description rather than actionable instructions, with significant padding that doesn't add operational value. | 1 / 3 |
Actionability | No concrete code, commands, or executable examples provided. The content describes capabilities abstractly ('Advanced dashboard creation with Tableau') without showing how to actually perform any task. The 'Example Interactions' are prompts, not demonstrations of outputs or methods. | 1 / 3 |
Workflow Clarity | The 'Response Approach' section provides a reasonable 8-step sequence, but lacks validation checkpoints, error handling, or feedback loops. Steps are high-level descriptions rather than actionable procedures with verification points. | 2 / 3 |
Progressive Disclosure | References `resources/implementation-playbook.md` for detailed examples, which is appropriate. However, the main content is a monolithic wall of capability lists that should be restructured or moved to reference files, making the overview bloated. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
75%| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata.version' is missing | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 12 / 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.