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

33%

Does it follow best practices?

Impact

87%

1.03x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/business-analyst/SKILL.md

The canonical home for this skill is business-analyst in sickn33/agentic-awesome-skills

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 generic persona template: long capability lists, behavioral traits, and a knowledge base with no executable guidance, no validation checkpoints, and a single broken file reference. It adds little Claude does not already know and is not actionable.

Suggestions

Cut the capability bullet lists, 'Behavioral Traits', and 'Knowledge Base' sections; replace them with 1-2 concrete worked examples (e.g. an actual churn-prediction SQL/model snippet or a dashboard spec).

Replace the abstract 8-step 'Response Approach' with a concrete, validated workflow: e.g. define objective → pull/quality-check data → analyze → verify numbers reconcile → present with stated assumptions.

Either create `resources/implementation-playbook.md` and point to it for detail, or remove the dangling reference; keep SKILL.md a lean overview with real one-level-deep references.

Dimension	Reasoning	Score
Conciseness	The ~170-line body is padded with capability bullet lists, 'Behavioral Traits', 'Knowledge Base', and a 'Purpose' section describing concepts Claude already knows (what dashboards, KPIs, and ETL are), fitting 'noticeably verbose; several unnecessary explanations or padded sections'.	2 / 5
Actionability	The body contains no executable code, commands, or procedures; it only describes capabilities ('Advanced dashboard creation with Tableau, Power BI'), matching 'entirely vague or abstract; no concrete code or commands; only describes rather than instructs'.	1 / 5
Workflow Clarity	The 'Response Approach' gives an 8-step sequence but the steps are abstract labels ('Design analytical framework', 'Execute comprehensive analysis') with no validation checkpoints, commands, or error-handling, matching 'rough sequence present but many gaps; validation absent'.	2 / 5
Progressive Disclosure	The only reference is to a non-existent `resources/implementation-playbook.md` (no resources/ directory exists), while the bulk detail is inlined as capability lists with minimal internal navigation, matching 'minimal structure; references are buried' and a broken reference.	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 clearly identifies the business-analysis domain and lists several activities, but it relies on buzzwords and abstract nouns rather than concrete, distinctive actions and omits any 'Use when...' trigger guidance. It reads as marketing copy for a persona rather than a precise skill trigger.

Suggestions

Replace abstract nouns ('KPI frameworks', 'predictive models') with concrete verbs ('Build KPI frameworks and OKRs', 'Forecast revenue with cohort and CLV models') and drop buzzwords like 'AI-powered' and 'data-driven insights'.

Add an explicit trigger clause, e.g. 'Use when the user needs business analysis, KPI/OKR design, dashboards, revenue or churn modeling, or data storytelling.'

Narrow the niche and add distinguishing terms (e.g. mention executive decision-making, BI tools like Tableau/Power BI) to reduce overlap with generic data-science skills.

Dimension	Reasoning	Score
Specificity	Names the business-analysis domain plus several actions ('Build comprehensive KPI frameworks, predictive models, and strategic recommendations') but uses abstract nouns and buzzwords ('AI-powered analytics', 'data-driven insights') rather than concrete verbs, fitting the 'domain and 1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	It states a clear 'what' (business analysis with dashboards, KPIs, predictive models) but contains no 'Use when...' clause or equivalent trigger guidance, so per the rubric cap completeness cannot exceed 3.	3 / 5
Trigger Term Quality	Contains some natural terms ('business analysis', 'real-time dashboards', 'KPI frameworks') but lacks synonyms, file types, or common phrasings users would say, and is buzzword-heavy ('AI-powered', 'data-driven'), so it matches 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The 'business analyst' niche is somewhat specific but the description overlaps broadly with data-analytics, BI, and data-science skills and could trigger for adjacent skills, matching 'somewhat specific but could still overlap'.	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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/business-analyst/SKILL.md
Commit: 57c135b

Reviewed: 2 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.