CtrlK
BlogDocsLog inGet started
Tessl Logo

micro-saas-launcher

You ship fast and iterate. You know the difference between a side project and a business. You've seen what works in the indie hacker community. You help people go from idea to paying customers in weeks, not years. You focus on sustainable, profitable businesses - not unicorn hunting.

42

Quality

43%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/micro-saas-launcher/SKILL.md

The canonical home for this skill is micro-saas-launcher in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

50%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 well-structured and offers genuinely concrete guidance (stack, schedule, pricing), but it is undermined by markdown content enclosed in mislabeled ```javascript code fences, missing validation checkpoints, and 'Sharp Edges' solutions that reference non-existent sections. Fixing the fences and adding explicit verify-gates would materially raise the scores.

Suggestions

Remove the ```javascript fences around the Patterns sections so the markdown tables and steps render as instructions rather than literal code blocks.

Add explicit validation checkpoints to the workflows, e.g. 'Only proceed to Week 2 if the landing page yielded N signups' and 'If pre-sale gets 0 buyers, pivot before building.'

Either write the 'Sharp Edges' subsections (Distribution First, Market Selection, Fixing Churn, Simple Pricing) that the solutions table points to, or remove the broken cross-references.

DimensionReasoningScore

Conciseness

The body is mostly compact tables and bullets and avoids explaining basics Claude already knows, but the opening 'Role' paragraph duplicates the frontmatter description and one-line subtitles like 'Validating before building' restate their headers; could be tightened, so it sits at the 'mostly efficient' anchor rather than 4.

3 / 5

Actionability

Concrete guidance is present (specific stack choices, a day-by-day 2-week schedule, dollar-range pricing tables, a worked pricing formula), but much of it is buried inside mislabeled ```javascript fences that enclose markdown, and 'Sharp Edges' solutions point to headers (e.g. '## Distribution First') that contain no concrete tactics — gaps that keep it below the 'mostly executable' anchor (4).

3 / 5

Workflow Clarity

The MVP Speed Run gives a clear sequenced 2-week timeline and Idea Validation lists ordered methods, but validation checkpoints are only implicit ('If no sales, pivot') with no explicit verify-then-proceed gates; fits the 'steps listed but validation gaps' anchor.

3 / 5

Progressive Disclosure

No bundle files exist and the skill is a single ~218-line file with reasonable section headers and no nested references, but all detailed tables are inlined and the 'Sharp Edges' table links to subsections that do not exist, signaling missing/placeholder structure; not disorganized enough for 2 but not clean enough for 4.

3 / 5

Total

12

/

20

Passed

Description

36%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 reads as a persona/voice statement rather than a capability+trigger description: it names the micro-SaaS niche but lists no concrete actions and provides no 'Use when' trigger guidance. It would benefit from explicit triggers and concrete capabilities.

Suggestions

Rewrite in third person and lead with concrete capabilities, e.g. 'Scopes MVPs, sets pricing, and sequences launch playbooks for micro-SaaS products.'

Add an explicit trigger clause such as 'Use when the user wants to launch, validate, price, or ship a micro-SaaS or indie SaaS product.'

Include natural trigger terms users actually say ('launch a SaaS', 'validate my idea', 'price my SaaS', 'build an MVP') to improve trigger matching.

DimensionReasoningScore

Specificity

Phrases like 'You help people go from idea to paying customers' and 'You focus on sustainable, profitable businesses' name the micro-SaaS domain but offer only minimal, generic actions rather than concrete capabilities; not score 1 because the domain is named, not score 3 because no specific concrete actions are enumerated.

2 / 5

Completeness

It gives a somewhat vague 'what' ('help people go from idea to paying customers') and entirely lacks a 'Use when...' or equivalent explicit 'when' clause, which caps completeness at 3; fits the 'vague what and no when' anchor rather than the 'clear what but no when' anchor (3).

2 / 5

Trigger Term Quality

Contains relevant natural terms ('indie hacker community', 'side project', 'paying customers', 'sustainable, profitable businesses') but misses common trigger phrases a user would actually say such as 'launch a SaaS', 'validate my idea', 'price my SaaS', or 'build an MVP'; sits between the one-or-two-generic anchor (2) and good-coverage anchor (4).

3 / 5

Distinctiveness Conflict Risk

The indie-hacker / micro-SaaS framing ('not unicorn hunting', 'paying customers in weeks, not years') carves a recognizable niche, but the persona-style phrasing and absence of explicit triggers leave overlap risk with general business/startup skills; not distinct enough for 4.

3 / 5

Total

10

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.