CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

startup-analyst

Expert startup business analyst specializing in market sizing, financial modeling, competitive analysis, and strategic planning for early-stage companies. Use 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

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/startup-analyst/SKILL.md
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 reads as an agent-persona manifesto rather than a usable skill: it exhaustively enumerates capability areas, traits, and example prompts while providing no actual analytical content (formulas, benchmarks, templates, or procedures). The description frontmatter does the triggering work; the body adds length without adding knowledge Claude does not already have.

Suggestions

Replace the capability and knowledge-base bullet lists with actual instructional content: concrete TAM/SAM/SOM formulas, a worked unit-economics example (CAC payback calculation), and stage-specific benchmark tables (e.g., burn multiple targets by round).

Cut the padded sections — Behavioral Traits, Example Interactions, When to Use This Agent, and Quality Standards largely restate the description's trigger terms; the body could shrink to a fraction of its length with no loss of guidance.

Move detailed framework material (industry-specific model templates, compensation benchmarks) into reference files under references/ and link them explicitly by path, keeping SKILL.md as a concise overview with clearly signaled one-level-deep references.

DimensionReasoningScore

Conciseness

The ~300-line body is dominated by padded sections: "Behavioral Traits" (10 adjective bullets like "Data-driven: Always grounds recommendations in data"), "Knowledge Base" entries that only name topics ("Common pitfalls and how to avoid them" without describing any pitfall), and 18 "Example Interactions" that restate the description's trigger terms. This matches anchor 2 (noticeably verbose, several padded sections) rather than anchor 3, since the padding is the majority of the body rather than isolated instances.

2 / 5

Actionability

The body describes rather than instructs: "TAM/SAM/SOM calculations using bottom-up and top-down methodologies", "Unit economics analysis (CAC, LTV, payback period)", and "Compensation benchmarks (US-focused, 2024)" are all stated without a single formula, benchmark number, model template, or worked example. The "Response Approach" and "Output Format" sections offer high-level process hints, matching anchor 2 (minimal concrete guidance, missing specific steps to execute) rather than anchor 1 only because those two sections give some structural direction.

2 / 5

Workflow Clarity

The "Response Approach" provides a clear 10-step sequence including "Validate findings - Cross-check with benchmarks and alternatives" and "Acknowledge limitations", so a sequence exists. But checkpoints are named without mechanism (no how to cross-check, no error-recovery loop), matching anchor 3 (sequence present but checkpoints implicit) rather than anchor 4's explicit verification commands.

3 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and the body's pointers to detail ("Leverages skills: market-sizing-analysis, startup-financial-modeling...") are bare names with no paths or links. Sections are well-headered, but ~300 lines of capability lists that belong in separate reference files are inlined, matching anchor 3 (some structure, content that should be separate is inline, references not clearly signaled).

3 / 5

Total

10

/

20

Passed

Description

87%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 answers both what and when explicitly, uses natural trigger keywords with acronym synonyms, and carves out a distinct startup-stage niche. The only gaps are a few missing colloquial trigger phrases (fundraising, runway, burn rate, pitch deck) and capability phrasing that is domain-level rather than action-level.

DimensionReasoningScore

Specificity

"specializing in market sizing, financial modeling, competitive analysis, and strategic planning" names the domain plus several concrete capability areas, matching anchor 4 (several specific actions, minor gaps). It falls short of anchor 5 because these are domain areas rather than verb-level concrete actions like "extract text and tables, fill forms, merge documents".

4 / 5

Completeness

"Expert startup business analyst specializing in market sizing, financial modeling, competitive analysis, and strategic planning for early-stage companies" clearly states what, and "Use when the user asks about market opportunity, TAM/SAM/SOM... or business strategy for pre-seed through Series A startups" explicitly states when with concrete trigger phrases — a direct match for anchor 5.

5 / 5

Trigger Term Quality

"market opportunity, TAM/SAM/SOM, financial projections, unit economics, competitive landscape, team planning, startup metrics" gives good natural keyword coverage including acronym synonyms, matching anchor 4. Not anchor 5 because common user phrases like "fundraising", "pitch deck", "runway", "burn rate", and "market size" are missing.

4 / 5

Distinctiveness Conflict Risk

The niche is clearly scoped to "pre-seed through Series A startups" with distinct triggers like TAM/SAM/SOM and unit economics, giving minimal conflict risk (anchor 5). The broad term "business strategy" is explicitly stage-qualified in the same phrase, so it does not drop to anchor 4's "minor overlap risk".

5 / 5

Total

18

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

rmyndharis/antigravity-skills

Path

skills/startup-analyst/SKILL.md

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.