CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

59

1.03x
Quality

42%

Does it follow best practices?

Impact

87%

1.03x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

35%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 persona/role card that lists domain capabilities Claude already knows, with abstract instructions and no concrete tooling or worked examples. It has section structure and a rough workflow but inlines bulk content and references a non-existent playbook file.

Suggestions

Cut the capability, behavioral-traits, and knowledge-base enumerations down to the few non-obvious specifics, or move them into a reference file that actually exists.

Replace abstract instructions ('Apply relevant best practices and validate outcomes') with concrete, executable steps or templates.

Add validation/feedback checkpoints to the Response Approach, and either create `resources/implementation-playbook.md` or remove the dangling reference.

DimensionReasoningScore

Conciseness

The ~170-line body is heavily padded with enumerative capability lists ('Tableau, Power BI, Looker, Qlik Sense', 'Machine learning for predictive analytics', etc.) and a persona line ('You are an expert business analyst...') that restate common knowledge Claude already has.

2 / 5

Actionability

Guidance is abstract rather than executable: 'Clarify goals, constraints, and required inputs', 'Execute comprehensive analysis with statistical rigor', 'Create compelling visualizations' — no concrete methods, templates, commands, or worked steps.

2 / 5

Workflow Clarity

The 8-step 'Response Approach' provides a rough sequence (Define objectives → Assess data → Design framework → Execute → Visualize → Recommend → Present → Monitor), but steps are high-level with no validation checkpoints or feedback loops.

3 / 5

Progressive Disclosure

Sections are header-organized, but the large capability/behavioral/knowledge enumerations are inlined rather than split out, and the single reference to 'resources/implementation-playbook.md' points to a file that does not exist in the bundle.

3 / 5

Total

10

/

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 states what the skill does in domain terms but omits any explicit 'when to use' trigger guidance, capping completeness, and leans on buzzword-heavy language that blurs distinctiveness. It names a few concrete actions but is padded and lacks natural trigger synonyms.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger phrases (e.g., 'Use when building KPI frameworks, designing dashboards, sizing a market, or running A/B tests').

Replace buzzword padding ('AI-powered analytics', 'real-time dashboards') with concrete deliverable actions to lift specificity.

Add natural synonyms/users-say-this terms ('KPIs', 'metrics', 'forecasting', 'cohort analysis') to sharpen trigger matching.

DimensionReasoningScore

Specificity

Names the domain ('business analysis') and a few concrete actions ('Build comprehensive KPI frameworks, predictive models, and strategic recommendations'), but prefixes them with buzzwordy fluff ('Master modern business analysis with AI-powered analytics, real-time dashboards, and data-driven insights') and is not comprehensive.

3 / 5

Completeness

Has a clear 'what' (build KPI frameworks, predictive models, strategic recommendations) but no 'when'/trigger clause; per the rubric, a missing 'Use when...' caps completeness at 3.

3 / 5

Trigger Term Quality

Contains relevant keywords ('business analysis', 'analytics', 'dashboards', 'KPI frameworks', 'predictive models') a user might say, but lacks synonyms, natural variations, or file-type triggers, and includes no explicit 'Use when' phrasing.

3 / 5

Distinctiveness Conflict Risk

'business analysis' is a recognizable niche, but the broad buzzword list (AI-powered analytics, real-time dashboards, data-driven insights, predictive models) overlaps notably with data-science and data-analyst skills.

3 / 5

Total

12

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
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.