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.

Quality

40%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/business-analyst/SKILL.md

Quality

Content

20%

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

The body is a monolithic, abstract capability catalog padded with concepts Claude already knows, offering little executable guidance and a broken reference, with only a checkpoint-free workflow sequence and section headings as redeeming structure.

Suggestions

Cut the generic capability, behavioral-trait, and knowledge enumerations (Tableau, A/B testing, CLV/CAC, GDPR) — Claude already knows these; retain only domain-specific guidance Claude lacks.

Add concrete executable guidance — e.g. a worked SQL/Python KPI-dashboard snippet, a churn-prediction template, or a real OKR-framework example — instead of abstract descriptions.

Fix or remove the dangling 'resources/implementation-playbook.md' reference, and add explicit validation checkpoints (e.g. verify data quality before analysis, validate model accuracy) to the Response Approach workflow.

Dimension	Reasoning	Score
Conciseness	The ~180-line body enumerates capabilities, traits, and knowledge Claude already knows (Tableau/Power BI, A/B testing, CLV/CAC, GDPR/CCPR) plus generic boilerplate instructions, matching the verbose/padded-with-unnecessary-context anchor.	1 / 3
Actionability	It provides no concrete code, commands, or executable examples — only abstract descriptions like 'Advanced dashboard creation with Tableau' and generic steps, and punts 'detailed examples' to a non-existent file, matching the vague/describes-rather-than-instructs anchor.	1 / 3
Workflow Clarity	The 'Response Approach' gives an 8-step sequence (Define objectives → Assess data → … → Plan monitoring) but includes no validation checkpoints or feedback loops, matching the steps-listed-but-validation-gaps anchor.	2 / 3
Progressive Disclosure	Section headings provide structure and a reference is signaled, but the bulk capability content that should live in separate files is inline, and the sole reference to 'resources/implementation-playbook.md' is dangling (no such file or references directory exists).	2 / 3
	Total	6 / 12 Passed

Description

60%

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 names concrete capabilities and a recognizable domain, but lacks any explicit 'Use when…' trigger clause and leans on buzzword framing, leaving it only partially complete and only moderately distinctive.

Suggestions

Add an explicit 'Use when…' trigger clause naming concrete scenarios, e.g. 'Use when building KPI dashboards, forecasting models, or analyzing business metrics'.

Include natural trigger terms users would actually say ('business analyst', 'analyze my data', 'build a dashboard', 'business metrics') to improve trigger-term coverage.

Replace buzzword framing ('Master modern…', 'AI-powered', 'real-time') with concrete, distinctive actions to reduce overlap with data-analysis/data-science skills.

Dimension	Reasoning	Score
Specificity	The second sentence lists multiple concrete actions — 'Build comprehensive KPI frameworks, predictive models, and strategic recommendations' — matching the multiple-specific-actions anchor, though the first sentence's 'AI-powered analytics, real-time dashboards, and data-driven insights' framing is buzzword-heavy.	3 / 3
Completeness	It clearly answers 'what' (KPI frameworks, predictive models, strategic recommendations) but has no explicit 'Use when…' trigger guidance, which caps completeness at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	Terms like 'business analysis', 'KPI frameworks', and 'dashboards' are relevant, but common natural variations a user would actually say ('business analyst', 'analyze my data', 'metrics', 'build a dashboard') are missing.	2 / 3
Distinctiveness Conflict Risk	The business-analyst niche with KPI/strategic-recommendations framing is somewhat distinct, but without trigger qualifiers it could still overlap with generic data-analysis or data-science skills.	2 / 3
	Total	9 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/business-analyst/SKILL.md
Commit: a3068b7

Reviewed: about 14 hours 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.