CtrlK
BlogDocsLog inGet started
Tessl Logo

nv-implement

Implement planned work by fanning out parallel subagents on isolated worktrees — TDD at pre-agreed seams, per-slice nv-park-and-review, merge back, full suite once at the end.

64

Quality

76%

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 ./.cursor/skills/nv-implement/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 strong, executable implementation playbook with explicit validation checkpoints and feedback loops throughout its six-step workflow. It is token-efficient and well-structured, with only minor conciseness and organization room for improvement.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude knows git/worktrees/mocha; it avoids explaining concepts Claude already knows, with only minor explanatory prose (e.g. the cross-slice fallout paragraph) that could be tightened.

4 / 5

Actionability

Provides fully executable, copy-paste-ready commands — `git worktree add`, `git merge --no-ff`, `ln -s`, and the complete mocha invocation with all env vars — covering the common cases concretely.

5 / 5

Workflow Clarity

Six clearly sequenced steps each end in an explicit '**Done when:**' validation checkpoint, with feedback loops (resume subagents that left tests red, fix fallout then re-run specs) and a guardrail checklist for the parallel/batch operation.

5 / 5

Progressive Disclosure

Well-organized into focused sections with a 'Related skills' block signaling one-level-deep sibling links ([novu-prepare-pr], [nv-worktree-commands]); no bundle files exist, and the inlined Commands section is appropriately scoped, though the body is monolithic rather than split.

4 / 5

Total

18

/

20

Passed

Description

63%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 is highly specific and action-oriented with a distinct niche, but lacks an explicit 'Use when...' trigger clause and leans on project jargon that limits natural trigger-term quality. Completeness is capped at 3 by the missing trigger guidance.

Suggestions

Add an explicit 'Use when...' clause stating when to invoke this skill (e.g. 'Use when implementing a plan or ticket that splits into independently shippable slices').

Replace or gloss project-specific jargon ('nv-park-and-review', 'pre-agreed seams') with natural trigger terms a user would actually say.

Add common synonyms/trigger phrases to broaden discoverability without losing specificity.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'fanning out parallel subagents on isolated worktrees', 'TDD at pre-agreed seams', 'per-slice nv-park-and-review', 'merge back', 'full suite once at the end' — giving comprehensive coverage of the implementation process.

5 / 5

Completeness

The 'what' is clear and concrete, but there is no explicit 'Use when...' trigger clause; per the guideline a missing trigger clause caps completeness at 3, and the 'when' is only weakly implied by 'Implement planned work'.

3 / 5

Trigger Term Quality

Contains relevant keywords ('implement', 'TDD', 'worktrees', 'subagents', 'merge', 'test suite') but leans on project-specific jargon like 'nv-park-and-review' and 'pre-agreed seams', missing common synonyms a user would naturally say.

3 / 5

Distinctiveness Conflict Risk

The worktree/subagent/seam workflow carves a clear niche distinct from general skills, with only minor overlap risk against sibling skills it explicitly references (/tdd, /nv-park-and-review).

4 / 5

Total

15

/

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

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository
novuhq/novu
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.