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.
45
Quality
36%
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
50%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 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 vague 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 distinguishing details that separate this from general data/analytics skills, such as specific business domains (finance, marketing, operations) or output types (executive reports, board presentations)
| 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
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 a shallow index page that provides almost no actionable guidance. It lists 10 sub-skills without explaining their contents and offers only generic, abstract instructions that could apply to any domain. The content fails to teach Claude anything specific about business analysis workflows, tools, or techniques.
Suggestions
Replace the generic 4-bullet instructions with a concrete workflow showing how to approach a business analysis task (e.g., 'Step 1: Identify data sources → Step 2: Define KPIs → Step 3: Build analysis → Step 4: Validate findings')
Add at least one concrete example showing input data and expected analytical output format
Provide brief 1-sentence descriptions for each sub-skill link so Claude knows when to reference each one
Remove the verbose 'Purpose' section and 'You are an expert...' framing - Claude doesn't need this context about itself
| 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 'You are an expert...' framing and purpose section explain things Claude already knows about being a business analyst. | 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 | The four-bullet instruction list is generic and lacks any meaningful sequence, validation checkpoints, or specific workflow steps. There's no clear process for how to actually perform business analysis tasks. | 1 / 3 |
Progressive Disclosure | The skill does reference sub-skills and a resources file, showing some structure. However, the main content is thin and the 10 sub-skill links are listed without context about what each contains or when to use them, making navigation unclear. | 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
3395991
- 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.