CtrlK
BlogDocsLog inGet started
Tessl Logo

solo-founder-gtm

When the user is a solo founder building their GTM motion, wants to scale without hiring, or needs to design an AI agent team for go-to-market. Also use when the user mentions 'solo founder,' 'one-person startup,' 'solopreneur,' 'bootstrapped,' 'no team,' 'AI agents as team,' 'scaling without hiring,' 'founder-led sales,' 'lean GTM,' 'one-person company,' or 'no employees.' This skill covers the complete solo founder GTM playbook from stack selection through agent team design, revenue-stage transitions, time allocation, and when to finally hire. Do NOT use for technical implementation, code review, or software architecture.

70

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

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

A highly actionable, well-structured playbook rich in specific domain data, weakened mainly by length/repetition and a total absence of progressive disclosure to separate reference files. The lowest dimensions are conciseness and progressive disclosure.

Suggestions

Move the persona framing ('You are an expert...') and remove overlap between Before Starting, Questions to Ask, and Quick Reference — keep each fact in one place to cut tokens.

Split the bulky tool-stack table (Section 2) and AI agent definitions (Section 5) into reference files (e.g. STACK.md, AGENTS.md) and link to them from a leaner SKILL.md overview.

Add an explicit validate/retry checkpoint to the outbound workflow (e.g. review a sample of personalized emails before the batch sends) to lift workflow_clarity above 4.

DimensionReasoningScore

Conciseness

The body is information-dense with non-obvious domain data (tool costs, MRR thresholds), but the 'You are an expert...' persona opening and repetition between Quick Reference, Questions to Ask, and the Before Starting section could be tightened.

3 / 5

Actionability

It provides concrete, executable guidance throughout — named tools with monthly costs, specific MRR stage thresholds, a five-step sales script, deployment-priority ordering, and checklists with quantified targets.

5 / 5

Workflow Clarity

Multi-step processes are clearly sequenced (QUALIFY→DISCOVER→DEMO→CLOSE→ONBOARD, revenue-stage progression with MRR gates, agent deploy order) with most checkpoints present, though validation feedback loops for batch outbound are implicit rather than explicit.

4 / 5

Progressive Disclosure

The ~450-line file is well-sectioned with headers but is entirely monolithic — no external reference files exist and content like the tool-stack tables and agent definitions that could live one level deep is inlined.

3 / 5

Total

15

/

20

Passed

Description

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

A strong, third-person description that comprehensively covers capabilities, trigger terms, and an explicit use/non-use boundary. No significant gaps; every dimension lands at the top anchor.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete capabilities — 'stack selection,' 'agent team design,' 'revenue-stage transitions,' 'time allocation,' and 'when to finally hire' — giving comprehensive coverage rather than vague domain naming.

5 / 5

Completeness

It explicitly answers both 'what' (the complete GTM playbook scope) and 'when' (two explicit trigger clauses), and adds a 'Do NOT use for technical implementation, code review, or software architecture' boundary.

5 / 5

Trigger Term Quality

It enumerates a comprehensive set of natural trigger phrases a user would actually say, including synonyms ('solo founder,' 'solopreneur,' 'one-person startup,' 'bootstrapped,' 'lean GTM,' 'no employees,' 'scaling without hiring').

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (solo-founder GTM) with distinct triggers and an explicit exclusion clause, minimizing the chance of firing for adjacent technical or general-GTM skills.

5 / 5

Total

20

/

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
tech-leads-club/agent-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.