CtrlK
BlogDocsLog inGet started
Tessl Logo

startup-business-analyst-business-case

Generate comprehensive investor-ready business case document with market, solution, financials, and strategy

43

Quality

44%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

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/startup-business-analyst-business-case/SKILL.md

The canonical home for this skill is startup-business-analyst-business-case in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

38%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 provides a comprehensive, well-sectioned business-case template with a clear step sequence, but it is verbose with generic filler, lacks validation checkpoints, and inlines content that belongs in a separate reference file while pointing to a missing reference path.

Suggestions

Move the full 10-section document template into a reference file (e.g. references/business-case-template.md) and keep SKILL.md as a concise overview that links to it; fix the broken 'resources/implementation-playbook.md' path or remove it.

Remove the generic 'Use this skill when / Do not use this skill when' boilerplate and the duplicate 'Instructions' section; trim obvious best-practice bullets Claude already knows.

Add an explicit validation/review checkpoint in the workflow (e.g. 'Step 8: Review the draft against the audience goal and confirm every section is quantified before saving').

DimensionReasoningScore

Conciseness

Generic boilerplate trigger sections, two separate 'Instructions' sections, and obvious best-practice bullets ('Quantify everything', 'Show, don't just tell') pad the body alongside numerous $X/$Y/$Z placeholder tables.

2 / 5

Actionability

A concrete 10-section template, specific intake questions, named sibling skills, and a worked use-of-proceeds example give real guidance, but most sections are placeholder-driven ('describe X', 'list Y') rather than fully concrete specifics.

3 / 5

Workflow Clarity

A clear 7-step sequence is present (gather → activate skills → structure → visuals → optional → exec summary → save), but no explicit validation checkpoints appear in the workflow; the only 'validate outcomes' mention is a generic top-level bullet.

3 / 5

Progressive Disclosure

No references/scripts/assets bundle exists, yet the single in-body reference points to a non-existent 'resources/implementation-playbook.md', while ~400 lines of the full document template are inlined in SKILL.md rather than split into a reference file.

2 / 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 clearly states what the skill produces and names several relevant domain terms, but it omits any explicit 'when to use' trigger guidance and lacks the natural synonyms users would most likely say. It lands at the midpoint across all dimensions.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases, e.g. 'Use when creating an investor-ready business case, business plan, fundraising memo, or pitch narrative.'

Expand trigger terms to include natural synonyms users say: 'business plan', 'fundraising', 'investment memo', 'pitch', 'startup business case'.

Use third-person action voice and list multiple distinct actions (e.g. 'Generates, structures, and sizes an investor-ready business case...') to raise specificity.

DimensionReasoningScore

Specificity

Names the domain ('business case document') and several covered areas ('market, solution, financials, and strategy'), but only one action verb ('Generate') appears rather than multiple distinct concrete actions.

3 / 5

Completeness

The 'what' is clearly stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords like 'business case', 'investor-ready', 'market', and 'financials' appear, but common natural variations users would say ('business plan', 'fundraising', 'pitch', 'investment memo') are missing.

3 / 5

Distinctiveness Conflict Risk

'investor-ready business case document' is a recognizable niche, but it overlaps with adjacent startup skills (market-sizing, financial-modeling, competitive-landscape, pitch decks) referenced in the body.

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.