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

33%

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

17%Weight 40%Scale 1-5

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 verbose, abstract persona description that restates knowledge Claude already has and provides no concrete, executable guidance. Its single progressive-disclosure reference is broken (the file is absent), and its workflow lacks validation checkpoints.

Suggestions

Replace the ~70-bullet capability enumeration and 'Behavioral Traits'/'Knowledge Base' padding with a concise overview; move detailed capability catalogs into a real reference file.

Add concrete, executable guidance — example SQL/Python for a KPI query, a dashboard wireframe, or a worked cohort/LTV calculation — instead of abstract steps.

Fix the broken reference: create resources/implementation-playbook.md (or references/) and link it clearly, or remove the dangling pointer; add explicit validation checkpoints to the Response Approach.

Dimension	Reasoning	Score
Conciseness	The ~177-line body is a persona/capability dump — ten capability subsections (~70 bullets) enumerating tools and techniques (Tableau, Snowflake, A/B testing, GDPR) that Claude already knows, plus 'Behavioral Traits' and 'Knowledge Base' padding; it is noticeably verbose with several padded sections.	2 / 5
Actionability	There is no executable guidance anywhere: 'Instructions' ('Clarify goals… Apply relevant best practices and validate outcomes') and 'Response Approach' are entirely abstract, with no code, commands, or concrete methods — it only describes rather than instructs.	1 / 5
Workflow Clarity	The 'Response Approach' gives an 8-step sequence, but the steps are abstract and poorly defined ('Define business objectives', 'Assess data availability') with no validation checkpoints or concrete actions, matching a rough sequence with validation absent.	2 / 5
Progressive Disclosure	The bulk capability/persona content that clearly belongs in a separate reference file is inlined in SKILL.md, and the one reference ('open resources/implementation-playbook.md') is buried in Instructions and points to a file that does not exist — no resources/, references/, scripts/, or assets/ directory is present.	2 / 5
	Total	7 / 20 Passed

Description

50%Weight 40%Scale 1-5

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 communicates a clear capability set but is diluted by marketing buzzwords and an over-claim, and it omits any explicit 'when to use' trigger guidance. It is adequate but generic for a business-analysis skill.

Suggestions

Lead with concrete actions and drop marketing language like 'Master modern business analysis with AI-powered analytics… data-driven insights' in favor of specific deliverables.

Add an explicit 'Use when…' clause naming natural user triggers (e.g., 'Use when building KPI/OKR frameworks, designing dashboards, or forecasting revenue').

Narrow the domain or add distinctive trigger terms (KPI, OKR, cohort, LTV/CAC) to reduce overlap with generic data-analyst and BI skills.

Dimension	Reasoning	Score
Specificity	The description names the domain and a few concrete deliverables ('Build comprehensive KPI frameworks, predictive models, and strategic recommendations', 'real-time dashboards'), but the first sentence is marketing fluff ('Master modern business analysis with AI-powered analytics, real-time dashboards, and data-driven insights') and over-claims ('Master'), so it does not reach the comprehensive, clean action list of a 4.	3 / 5
Completeness	A clear 'what' is present (build KPI frameworks, predictive models, dashboards, strategic recommendations) but there is no explicit 'when' trigger clause, so per the guideline a missing 'Use when…' clause caps completeness at 3.	3 / 5
Trigger Term Quality	Relevant domain keywords appear ('business analysis', 'KPI frameworks', 'dashboards', 'predictive models') that a business user might say, but there is no natural 'Use when…' trigger phrasing and common synonyms/variations are missing.	3 / 5
Distinctiveness Conflict Risk	'Business analysis' with KPI frameworks and dashboards is a recognizable niche but is broad and overlaps with data-science, BI, and finance-analyst skills, so it could still trigger for closely related skills.	3 / 5
	Total	12 / 20 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: 1f67c44

Reviewed: 1 day 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.