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.

57

Quality

67%

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

86%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 a tight, well-structured instructional skill with a concrete prioritized workflow, explicit output shape, and thoughtful verification bias. Its only gap is the absence of a worked output example and an explicit retry feedback loop, which would push actionability and workflow clarity to the top anchor.

DimensionReasoningScore

Conciseness

The body is lean and instructional with no padding about concepts Claude already knows; every section (Rule, Workflow, Output Shape, Verification Bias, Related Skills) earns its place and assumes Claude's competence.

5 / 5

Actionability

Guidance is concrete and actionable for an instruction-only skill: a prioritized gap-checklist, an explicit bloat skip-list, a Do-now/Defer/Blocker output shape, and a named command (pnpm prep) with a non-mutation rule — but it lacks a worked example of the output shape or a literal pnpm prep invocation, keeping it short of copy-paste-ready.

4 / 5

Workflow Clarity

A clear 5-step numbered workflow with an ordered sub-priority inside step 2 and explicit verification handling (Verification Bias prefers non-mutating checks, keeps edits minimal, runs in parallel only where safe); it stops short of 5 because there is no explicit validate->fix->retry feedback loop.

4 / 5

Progressive Disclosure

Under 50 lines, single-purpose, and cleanly sectioned with no nested reference chains; per the simple-skill exception, well-organized sections with no needed external files warrant a top score, and the Related Skills links are sibling cross-references rather than buried file pointers.

5 / 5

Total

18

/

20

Passed

Description

48%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 has a genuine, natural trigger clause and a clear distinct niche, but its stated capabilities are abstract rather than concrete and the 'what' is implied rather than explicit. It reads more as a decision policy than a capability list.

Suggestions

Add 1-2 concrete actions to the description so the 'what' is explicit, e.g. 'Reviews the worktree for unfinished verification, unreviewed pilot results, and stale docs, then recommends the smallest closeout batch.'

Broaden trigger-term coverage with natural synonyms users say, such as 'next steps', 'follow-up', 'wrap-up', or 'closeout'.

Consider naming the concrete closeout artifacts (validation, real pilot, docs, bug fixes) to lift specificity from domain-naming to listed actions.

DimensionReasoningScore

Specificity

It names the domain (post-feature-pass closeout) and behaviors ("avoiding bloat", "checking for unfinished MVP work"), but these are abstract directives rather than concrete actions like extract/fill/merge, fitting the 'names domain but actions minimal/generic' anchor.

2 / 5

Completeness

The 'when' is explicit and strong, but the 'what' (recommend/execute closeout work) is only implied in the description — the actual action set lives in the body — so it sits between anchors rather than cleanly answering both what and when.

3 / 5

Trigger Term Quality

It opens with a natural trigger phrase a user would actually say ("Use when asking what to do next after a feature pass"), but beyond "MVP" and "bloat" the keyword set is thin and misses common synonyms like 'next steps', 'follow-up', or 'closeout'.

3 / 5

Distinctiveness Conflict Risk

"What to do next after a feature pass while avoiding bloat... checking for unfinished MVP work" carves a distinct closeout/MVP-hygiene niche with only minor overlap with the cross-referenced siblings qa/ship/adding-a-feature.

4 / 5

Total

12

/

20

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.