business-analyst
Master 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.
54
44%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent/skills/business-analyst/SKILL.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description provides adequate structure with both 'what' and 'when' clauses, earning full marks for completeness. However, it relies heavily on buzzwords ('AI-powered', 'data-driven', 'master modern') that add fluff without specificity. The trigger terms are reasonable but could be more comprehensive to cover natural user language variations.
Suggestions
Replace vague buzzwords like 'AI-powered analytics' and 'data-driven insights' with specific concrete actions (e.g., 'calculate ROI, analyze revenue trends, forecast sales').
Expand trigger terms to include natural user phrases like 'metrics', 'business reports', 'revenue analysis', 'market analysis', 'quarterly review'.
Add distinguishing details to differentiate from general analytics or data visualization skills (e.g., specify business domains or unique capabilities).
| 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 | Answers both what ('Build comprehensive KPI frameworks, predictive models, and strategic recommendations') and when ('Use PROACTIVELY for business intelligence or strategic analysis') with explicit trigger guidance. | 3 / 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 analysis types users might request. | 2 / 3 |
Distinctiveness Conflict Risk | Terms like 'analytics', 'dashboards', and 'data-driven insights' could overlap with data visualization skills, general analytics tools, or reporting skills. The business focus helps but isn't sufficiently distinct. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
22%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 hollow shell that delegates all substance to sub-skills without providing any actionable guidance in the main file. It lacks concrete examples, specific workflows, or executable instructions—just generic advice that Claude already knows. The structure exists but the content doesn't earn its tokens.
Suggestions
Add a concrete 'Quick Start' section with a specific example workflow (e.g., 'To analyze sales KPIs: 1. Load data with pandas, 2. Calculate metrics X/Y/Z, 3. Visualize with...')
Replace vague instructions ('Apply relevant best practices') with specific, actionable steps for common business analysis tasks
Include at least one executable code example or concrete analysis template that demonstrates the skill's value
Add a brief summary of what each sub-skill covers so users can navigate without clicking through all 10 links
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content has some unnecessary padding (generic 'Use this skill when' sections, verbose purpose statement) but isn't excessively verbose. The capabilities section is essentially just a list of links, which is efficient but the framing text adds little value. | 2 / 3 |
Actionability | The skill provides no concrete code, commands, or executable guidance. Instructions like 'Clarify goals, constraints, and required inputs' and 'Apply relevant best practices' are vague abstractions with no specific examples or actionable steps. | 1 / 3 |
Workflow Clarity | No clear workflow or sequence is defined. The four bullet points under 'Instructions' are generic platitudes without any specific process, validation checkpoints, or feedback loops for business analysis tasks. | 1 / 3 |
Progressive Disclosure | The skill does reference 10 sub-skills and a resources file, showing some structure. However, the main content provides almost no useful overview—it's essentially just a table of contents with no substantive quick-start content before directing to other files. | 2 / 3 |
Total | 6 / 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 |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- Dokhacgiakhoa/antigravity-ide
- Commit
332e58b
- 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.