startup-analyst

Expert startup business analyst specializing in market sizing, financial modeling, competitive analysis, and strategic planning for early-stage companies. Use PROACTIVELY when the user asks about market opportunity, TAM/SAM/SOM, financial projections, unit economics, competitive landscape, team planning, startup metrics, or business strategy for pre-seed through Series A startups.

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/startup-analyst/SKILL.md

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 an over-long, mostly abstract overview that names frameworks and metrics without giving Claude concrete procedures, formulas, or templates to execute them. Heavy generic padding and duplicated trigger lists waste context that concrete worked examples would better use.

Suggestions

Cut the boilerplate 'Use/Do not use this skill when' sections, the duplicated 'When to Use This Agent' trigger list, and the Quality Standards checklists — these restate the description or obvious best practices.

Replace abstract capability lists with concrete, executable guidance: actual TAM/SAM/SOM formulas, unit-economics calculations, or a worked financial-model template.

Move the Knowledge Base, Example Interactions, and Special Considerations into one-level-deep reference files (e.g., references/market-sizing.md) and link them from a lean overview.

Dimension	Reasoning	Score
Conciseness	The ~315-line body is noticeably padded: generic boilerplate ('Working on startup analyst tasks or workflows'), restated trigger lists, Quality Standards checklists ('Use credible, cited data sources'), and Behavioral Traits that state best practices Claude already knows.	2 / 5
Actionability	Guidance stays at the naming level ('TAM/SAM/SOM calculations using bottom-up and top-down methodologies', 'Apply Porter's Five Forces') without concrete formulas, templates, calculation steps, or worked examples, leaving the actual execution underspecified.	2 / 5
Workflow Clarity	The 10-step Response Approach provides a clear sequence including a validate step (step 6), but checkpoints are implicit and generic rather than tied to specific decision gates or error-recovery feedback loops.	3 / 5
Progressive Disclosure	No bundle files exist and the content is a single monolithic file; section headers provide some structure, but the Knowledge Base, Example Interactions, and Special Considerations blocks are inlined where separate reference files would aid navigation.	3 / 5
	Total	10 / 20 Passed

Description

83%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 is strong: it clearly states the skill's purpose and provides explicit, natural trigger terms scoped to the startup stage. Minor gaps in capability coverage (fundraising) and a few missing synonyms keep it just below maximum.

Suggestions

Add fundraising/valuation/pitch-deck trigger terms to capture a capability the body emphasizes but the description omits.

Consider framing capabilities as concrete actions (e.g., 'size markets, build financial models, assess competitors') rather than domain nouns.

Dimension	Reasoning	Score
Specificity	Names several specific capability areas ('market sizing, financial modeling, competitive analysis, and strategic planning') rather than vague abstractions, though these are domains more than discrete concrete actions, leaving minor coverage gaps (e.g., fundraising is omitted).	4 / 5
Completeness	Explicitly answers both what ('Expert startup business analyst specializing in...') and when ('Use PROACTIVELY when the user asks about...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Strong natural keyword coverage ('market opportunity, TAM/SAM/SOM, financial projections, unit economics, competitive landscape, team planning, startup metrics') that users would plausibly say, but misses common synonyms like fundraising, valuation, or pitch deck that appear in the body.	4 / 5
Distinctiveness Conflict Risk	Scoped to a clear niche (early-stage, pre-seed through Series A) with distinct triggers, but 'business strategy' and 'financial modeling' could overlap with general business/finance skills.	4 / 5
	Total	17 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/startup-analyst/SKILL.md
Commit: 3eff4af

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