CtrlK
BlogDocsLog inGet started
Tessl Logo

mvp-followup

Use when asking what to do next after a feature pass while avoiding bloat and checking for unfinished MVP work.

62

Quality

75%

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 ./.agents/skills/mvp-followup/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The body is a tight, well-structured instruction-only skill that gives a concrete decision procedure, a clear output shape, and explicit verification guidance without any wasted tokens.

DimensionReasoningScore

Conciseness

The body is lean (~45 lines) with no padding or explanation of concepts Claude already knows; every section (Rule, Workflow, Output Shape, Verification Bias) earns its place.

3 / 3

Actionability

Provides a concrete ordered checklist of what to check, a defined output template (Do now / Defer / Blocker), and a specific verification rule ('Use full pnpm prep only when it will not rewrite someone else's concurrent work'); guidance is actionable for an instruction-only skill.

3 / 3

Workflow Clarity

A clear 5-step sequenced workflow with an embedded unfinished-work checklist and a dedicated Verification Bias section; the operation is non-destructive so the missing validate-retry loop does not cap the score.

3 / 3

Progressive Disclosure

Self-contained skill under 50 lines with no need for external references, organized into clear sections plus a Related Skills cross-reference; per the simple-skills note this earns full credit.

3 / 3

Total

12

/

12

Passed

Description

50%

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 provides a clear, natural trigger for when to use the skill, but it leaves the actual capability implicit and relies on somewhat generic phrasing that weakens both completeness and distinctiveness.

Suggestions

Add an explicit capability statement so 'what' is answered, e.g. 'Recommends or executes the smallest closeout batch (validation, real-data pilot review, docs, fixes) to make an MVP shippable. Use when...'

Broaden trigger coverage with natural variations users actually say: 'wrap up', 'closeout', 'ship the MVP', 'is the MVP done', 'what's left before shipping'.

Replace the generic 'what to do next' with MVP-specific language to reduce overlap with general planning skills.

DimensionReasoningScore

Specificity

Names the domain ('after a feature pass', 'unfinished MVP work') and some actions ('avoiding bloat', 'checking for unfinished MVP work'), but does not enumerate the concrete closeout actions the skill actually performs, so it is not comprehensive.

2 / 3

Completeness

The 'when' is explicit ('Use when asking what to do next after a feature pass...'), but the 'what' — the capability of recommending/executing closeout work — is only implied, not stated, so it does not clearly answer both.

2 / 3

Trigger Term Quality

Includes natural phrases a user might say ('what to do next', 'MVP') but misses common variations like 'wrap up', 'closeout', 'ship it', or 'is the MVP done', leaving coverage incomplete.

2 / 3

Distinctiveness Conflict Risk

The MVP/feature-pass framing carves a niche, but the generic phrase 'what to do next' could overlap with general planning or next-step skills, so conflict risk remains.

2 / 3

Total

8

/

12

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository
BuilderIO/agent-native
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.