startup-business-analyst-business-case

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

Quality

38%

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

Quality

Content

31%Scale 1-5

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

This skill is essentially a massive business case template pasted into a SKILL.md, explaining document sections that Claude already knows how to produce. It is severely over-long and under-actionable—mostly placeholder scaffolding rather than genuinely novel guidance. The workflow has reasonable sequencing but lacks validation steps, and the content desperately needs to be split into separate reference files.

Suggestions

Move the entire document template (Sections 1-10) into a separate reference file like `resources/business-case-template.md` and keep SKILL.md to a concise workflow overview with key decision points.

Remove explanations of standard business case concepts (what an executive summary is, what competitive analysis covers) since Claude already knows these—focus only on non-obvious investor-specific requirements or formatting preferences.

Add explicit validation/review checkpoints, e.g., 'After drafting financials, verify internal consistency: do revenue projections match unit economics? Does headcount plan align with use of proceeds?'

Either provide the referenced `resources/implementation-playbook.md` file or remove the reference; similarly, verify that referenced skills like 'market-sizing-analysis' and commands like '/market-opportunity' actually exist.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~350+ lines. The vast majority is a template skeleton with placeholder values (e.g., '$X.XM', 'XX%') that Claude could generate on its own. It explains obvious concepts like what an executive summary should contain, what a competitive matrix is, and basic business case structure—all things Claude already knows well. Almost no token earns its place.	1 / 5
Actionability	The skill provides a structured outline with table templates and placeholder formats, which gives some concrete guidance. However, it's essentially a document template rather than executable instructions—there's no actual code, no specific commands, and the 'steps' are mostly 'ask the user for X' and 'create section Y.' References to other skills/commands (market-sizing-analysis, /market-opportunity) are unverified and may not exist.	3 / 5
Workflow Clarity	There is a 7-step sequence (Gather Context → Activate Skills → Structure → Enhance → Additional Sections → Executive Summary → Save), which provides reasonable ordering. However, there are no validation checkpoints—no step to verify the document's quality, consistency of financial figures, or review with the user before finalizing. For a document generation task this complex, the lack of any review/validation loop is a notable gap.	3 / 5
Progressive Disclosure	The content is a monolithic wall of text with everything inlined. It references 'resources/implementation-playbook.md' but no bundle files exist. The 300+ lines of document template structure should clearly be in a separate reference file, with the SKILL.md providing just the workflow and key guidance. References to other skills/commands are mentioned but not linked or verified.	2 / 5
	Total	9 / 20 Passed

Description

45%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 identifies a clear domain (investor-ready business case documents) and lists the major sections covered, providing moderate specificity. However, it lacks a 'Use when...' clause, which is critical for Claude to know when to select this skill. The trigger terms are adequate but miss many natural synonyms users might employ when requesting this type of document.

Suggestions

Add an explicit 'Use when...' clause with trigger phrases like 'Use when the user asks for a business plan, investment proposal, pitch document, startup business case, or funding-related document.'

Include natural synonyms and related terms users might say: 'business plan', 'pitch deck', 'investment memo', 'startup plan', 'funding proposal', 'revenue projections'.

Make the actions more concrete by specifying what is generated within each section, e.g., 'builds market sizing analysis, competitive landscape, financial projections with revenue models, and go-to-market strategy'.

Dimension	Reasoning	Score
Specificity	Names the domain (business case document) and lists several high-level sections (market, solution, financials, strategy), but these are categories rather than concrete actions. It doesn't specify what actions are performed within each section (e.g., 'build financial projections', 'analyze market size', 'create competitive landscape').	3 / 5
Completeness	Provides a reasonable 'what' (generate a business case document with specific sections) but completely lacks a 'when' clause. There is no 'Use when...' guidance or equivalent trigger phrasing, which per the rubric should cap completeness at 3, and the absence is severe enough to warrant a 2.	2 / 5
Trigger Term Quality	Includes some relevant keywords like 'investor-ready', 'business case', 'market', 'financials', and 'strategy', but misses common natural user phrases like 'pitch deck', 'business plan', 'startup', 'funding', 'investment proposal', 'revenue model', or 'go-to-market'.	3 / 5
Distinctiveness Conflict Risk	The combination of 'investor-ready business case document' with specific section types (market, solution, financials, strategy) creates a fairly distinct niche. There's minor overlap risk with general document generation or financial analysis skills, but the investor-focused framing helps differentiate it.	4 / 5
	Total	12 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/startup-business-analyst-business-case/SKILL.md
Commit: 57c135b

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