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.

1.03x

Quality

16%

Does it follow best practices?

Impact

87%

1.03x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/business-analyst/SKILL.md

Quality

Discovery

25%

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 relies heavily on buzzwords ('AI-powered,' 'data-driven,' 'comprehensive') without specifying concrete, distinguishable actions. It lacks any explicit trigger guidance ('Use when...') and covers such a broad domain that it would likely conflict with multiple other skills. The description reads more like marketing copy than a functional skill selector.

Suggestions

Add an explicit 'Use when...' clause with specific trigger scenarios, e.g., 'Use when the user asks about KPI tracking, business performance dashboards, revenue forecasting, or strategic business recommendations.'

Replace vague buzzwords like 'AI-powered analytics' and 'data-driven insights' with concrete actions such as 'Calculates financial metrics, builds revenue forecasting models, creates executive summary dashboards.'

Narrow the scope to reduce conflict risk — clarify what distinguishes this from general data analysis, visualization, or financial modeling skills.

Dimension	Reasoning	Score
Specificity	Names the domain (business analysis) and lists some actions like 'Build comprehensive KPI frameworks, predictive models, and strategic recommendations,' but many terms are buzzword-heavy rather than concrete actions. 'AI-powered analytics' and 'data-driven insights' are vague fluff.	2 / 3
Completeness	Describes what the skill does (albeit vaguely), but completely lacks any 'Use when...' clause or explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, a missing 'Use when' clause caps completeness at 2, and the 'what' is also weak due to buzzword-heavy language, warranting a 1.	1 / 3
Trigger Term Quality	Includes some relevant keywords like 'KPI,' 'dashboards,' 'predictive models,' and 'business analysis' that users might say, but misses common variations and natural phrases users would use (e.g., 'revenue analysis,' 'business metrics,' 'market analysis,' 'ROI,' 'financial forecasting').	2 / 3
Distinctiveness Conflict Risk	Extremely broad scope covering analytics, dashboards, KPIs, predictive models, and strategic recommendations — this could easily conflict with data science skills, dashboard/visualization skills, forecasting skills, or general strategy skills. No clear niche is carved out.	1 / 3
	Total	6 / 12 Passed

Implementation

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill reads as a persona description or job posting rather than an actionable skill file. It is overwhelmingly verbose, listing dozens of capabilities and concepts Claude already knows without providing any concrete code, templates, frameworks, or executable guidance. The content would need a fundamental restructuring to be useful—replacing abstract capability lists with specific, actionable instructions, code examples, and validation steps.

Suggestions

Replace the extensive capability lists with 2-3 concrete, executable workflow examples (e.g., a complete Python script for churn analysis, a SQL template for cohort analysis, or a specific KPI dashboard specification).

Add specific code examples, SQL queries, or analytical templates that Claude can directly use rather than describing what Claude should be capable of doing.

Add validation checkpoints to the Response Approach workflow (e.g., 'Verify data completeness: check for >5% null values in key columns before proceeding').

Move the capability lists and knowledge base sections to a separate reference file and keep SKILL.md focused on concise, actionable instructions with clear entry points.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive lists of capabilities, behavioral traits, and knowledge bases that Claude already possesses. The content reads like a job description or persona prompt rather than a skill file. Massive amounts of text explain concepts Claude already knows (what CLV is, what A/B testing is, what data governance means).	1 / 3
Actionability	No concrete code, commands, templates, or executable guidance anywhere. The entire skill is abstract descriptions of capabilities and vague process steps like 'Execute comprehensive analysis with statistical rigor.' The 'Example Interactions' are just prompts, not worked examples with outputs. There is nothing copy-paste ready or directly usable.	1 / 3
Workflow Clarity	The 'Response Approach' section lists 8 high-level steps but they are generic and lack any validation checkpoints, specific tools/commands, or error recovery. Steps like 'Assess data availability' and 'Create compelling visualizations' provide no actionable sequence. No feedback loops or verification steps are present.	1 / 3
Progressive Disclosure	There is one reference to an external file ('resources/implementation-playbook.md') which is good, but the main file is a monolithic wall of bullet-pointed lists that could be dramatically condensed or split into separate reference files. The massive capability lists should be in a separate reference rather than inline.	2 / 3
	Total	5 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: sickn33/antigravity-awesome-skills
Commit: e18e63c

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.