CtrlK
BlogDocsLog inGet started
Tessl Logo

startup-analysis

Analyze a startup from three perspectives: VC investor, job applicant, and CEO/founder. Use this skill whenever the user wants to evaluate a startup, assess whether to invest in or join a startup, do due diligence, evaluate a job offer from a startup, understand a startup's competitive position, or assess company health and trajectory. Triggers: "analyze this startup", "should I join [company]", "is [company] a good investment", "evaluate [company]", "due diligence on [company]", "what do you think of [startup]", "should I take this startup job offer", "how healthy is [company]", "startup assessment", "company analysis", "is [company] worth joining", "what's the outlook for [company]", "research [company] for me", any mention of evaluating or assessing a startup or tech company from investment, career, or strategic perspectives — provide all three perspectives by default.

69

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 skill body is well-organized with a clear multi-step workflow, strong progressive disclosure (overview plus three real one-level reference files), and actionable guidance including an output template and verdict scales. Its main weaknesses are minor verbosity in a few restating sentences and the absence of an explicit verification checkpoint in the workflow.

Suggestions

Trim restating sentences like 'Each perspective surfaces insights the others miss' and 'A company can be a great investment but a terrible place to work' to tighten conciseness.

Add an explicit validation checkpoint in Step 1 (e.g., 'Confirm you have at least the company's product and funding stage before proceeding') to strengthen workflow feedback loops.

DimensionReasoningScore

Conciseness

The body is largely efficient and assumes Claude's competence (e.g., it lists core areas as bullets without explaining what CAC or TAM mean), but a few sentences restate the obvious ('Each perspective surfaces insights the others miss') and the verdict-label tables add mild padding that could be trimmed.

4 / 5

Actionability

It gives concrete, executable guidance: a specific data-gathering table, decision rules for which perspective to emphasize, explicit verdict scales, and a full output template. It stops just short of a 5 because most guidance is instructional rather than copy-paste executable (appropriate for an analysis skill, but the rubric rewards concrete commands).

4 / 5

Workflow Clarity

A clear five-step sequence is laid out (gather, choose perspectives, analyze each, synthesize, present) with a decision table and structured output template. It lacks an explicit validation/feedback checkpoint, but the skill is analytical rather than destructive/batch, so the destructive-cap at 3 does not apply; it sits at 4 with minor checkpoint gaps.

4 / 5

Progressive Disclosure

SKILL.md is a concise overview that cleanly defers detail to three one-level-deep reference files, all of which exist and are clearly signaled both inline ('Read references/vc-framework.md') and in a closing reference list with descriptions — matching the top anchor for clear overview with well-signaled references.

5 / 5

Total

17

/

20

Passed

Description

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

This is a strong, well-constructed description that clearly states what the skill does and when to use it, with rich natural trigger phrases. Minor improvement is possible by tightening the somewhat overlapping action list and narrowing the very broad catch-all trigger clause.

Suggestions

Consolidate overlapping action phrases into a tighter, distinct list of capabilities to sharpen specificity.

Consider narrowing the catch-all trigger ('any mention of evaluating or assessing a startup or tech company') to reduce overlap with general research skills.

DimensionReasoningScore

Specificity

The description names the domain and multiple concrete actions across three perspectives ('evaluate a startup, assess whether to invest in or join a startup, do due diligence, evaluate a job offer... understand a startup's competitive position, assess company health and trajectory'), but the actions overlap and could be more crisply enumerated as distinct capabilities.

4 / 5

Completeness

It clearly answers both 'what' (analyze a startup from three perspectives) and 'when' (explicit 'Use this skill whenever...' clause with concrete trigger phrases), matching the top anchor.

5 / 5

Trigger Term Quality

It lists a comprehensive set of natural trigger phrases users would actually say ('should I join [company]', 'is [company] a good investment', 'should I take this startup job offer', 'how healthy is [company]') plus synonyms covering investment, career, and strategic angles.

5 / 5

Distinctiveness Conflict Risk

The three-lens framing is a distinct niche with minimal conflict risk, but the broad closing clause ('any mention of evaluating or assessing a startup or tech company') slightly increases overlap with general research skills, keeping it just below a 5.

4 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
himself65/finance-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.