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.

72

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

A comprehensive, highly actionable solo-founder GTM playbook with clear sequenced workflows and concrete reference data. Its main weaknesses are length/framing prose and a monolithic single-file structure with no progressive disclosure into separate reference files.

Suggestions

Trim non-actionable framing prose (the 'You are an expert' persona opening and the 'Taste as Moat' philosophy narrative) to tighten conciseness, keeping the concrete DELEGATE/OWN table.

Split the large reference material — the tool stack table, AI agent team definitions, and revenue-stage playbook — into separate one-level-deep files (e.g. STACK.md, AGENTS.md, STAGES.md) referenced from a lean SKILL.md overview to improve progressive disclosure.

Remove or consolidate the Quick Reference table where it merely restates numbers already present in the body sections to avoid redundant context cost.

DimensionReasoningScore

Conciseness

Mostly efficient and table-driven with concrete data, but the ~500-line body carries framing/persona prose ('You are an expert...,' the 'Taste as Moat' philosophy) and a Quick Reference table that restates figures already in the body, so not every token earns its place.

2 / 3

Actionability

Highly concrete, copy-paste-ready guidance for an instruction skill: named tools with monthly costs, per-stage time splits, agent definitions with workflows/time saved, decision tables, sales-velocity targets, a 15-item question bank, and worked Examples.

3 / 3

Workflow Clarity

Processes are clearly sequenced with checkpoints and guardrails: the Before-Starting context checklist, MRR-stage playbook with explicit 'Skip' lists, ordered agent deploy priority, and the QUALIFY→DISCOVER→DEMO→CLOSE→ONBOARD flow with branch logic ('No: politely decline').

3 / 3

Progressive Disclosure

Well-organized into numbered sections with a Quick Reference and a cross-skill Related Skills table, but everything is inline in a single large file with no bundle references; the content (detailed stack/agent/stage reference) is not split across one-level-deep files, and the <50-line simple-skill exception does not apply.

2 / 3

Total

10

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An excellent description that clearly states what the skill does, when to invoke it via natural trigger terms, and what it deliberately does not cover. It matches the strongest reference examples in the rubric and uses correct third-person voice.

DimensionReasoningScore

Specificity

Lists multiple specific concrete capabilities — 'stack selection,' 'agent team design,' 'revenue-stage transitions,' 'time allocation,' and 'when to finally hire' — rather than vague abstractions.

3 / 3

Completeness

Explicitly answers both what ('covers the complete solo founder GTM playbook from stack selection through...') and when ('When the user is a solo founder... Also use when the user mentions...'), plus negative-scope guidance; the 'Use when...' trigger clause is present so it is not capped at 2.

3 / 3

Trigger Term Quality

Dense coverage of natural terms a user would actually say: 'solo founder,' 'one-person startup,' 'solopreneur,' 'bootstrapped,' 'no team,' 'scaling without hiring,' 'founder-led sales,' 'lean GTM,' 'one-person company,' 'no employees.'

3 / 3

Distinctiveness Conflict Risk

Clear niche (solo founder GTM) with distinct trigger terms and an explicit 'Do NOT use for technical implementation, code review, or software architecture' boundary, making misfires unlikely.

3 / 3

Total

12

/

12

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.