CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

new-feature

Post-launch setup for a new feature worktree — detect context, recall memories, and transition to brainstorming.

Quality

70%

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 ./skills/new-feature/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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.

A well-structured, highly actionable orientation workflow with concrete commands, templates, and thoughtful fallbacks for different environments. Its main cost is redundancy — several instructions are stated two or three times across the body — and a dense pipeline paragraph that would sit better in its own section.

Suggestions

Remove the duplicated reminders in the 'Important' section (worktree already exists, always recall from Hindsight, never skip brainstorming) since each restates content already stated verbatim earlier.

Merge Step 4's bolded 'Don't guess from the branch name' paragraph into the step's lead-in to eliminate the near-verbatim repetition.

Move the pipeline/spawn mechanics paragraph out of Step 6 into a short 'Pipeline (for reference)' section so the transition instruction stays scannable.

DimensionReasoningScore

Conciseness

Mostly efficient with no explanations of concepts Claude already knows, but several passages repeat: the worktree-already-exists note appears twice, Step 4's bolded paragraph restates its own lead-in, and the 'Important' section reiterates Steps 2 and 6.

3 / 5

Actionability

Concrete and executable throughout — copy-paste bash snippets, an exact regex, a specific mark_chapter payload, Hindsight query patterns, a verbatim output template, and quoted user prompts; minor gaps such as pattern-only Hindsight query syntax.

4 / 5

Workflow Clarity

A clearly sequenced Preamble → Steps 1-6 flow with explicit guards (main/master branch check, mark_chapter fallback, CLI vs Desktop handling, eval-mode stop condition); lacks an explicit validation checkpoint after context recall, keeping it just below the top anchor.

4 / 5

Progressive Disclosure

No bundle files exist and the ~90-line body is self-contained with well-organized sections (Preamble, Steps, Important) and clear navigation to external skills; the dense pipeline paragraph inside Step 6 and the redundant 'Important' section are minor organization gaps.

4 / 5

Total

15

/

20

Passed

Description

58%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 gives a clear, reasonably specific picture of what the skill does in its niche of the devflow pipeline. Its main weaknesses are the complete absence of 'when to use' trigger guidance and thin natural-language keyword coverage.

Suggestions

Append an explicit trigger clause, e.g. 'Use when launched inside a feature worktree after devflow worktree, or when starting work on a new feature branch.'

Add natural trigger terms and synonyms users would say, such as 'new feature', 'feature branch', 'kick off a feature', or 'start feature work'.

Briefly enumerate the remaining concrete actions (present workspace context, offer codebase walkthrough) to round out coverage.

DimensionReasoningScore

Specificity

Names the domain ('Post-launch setup for a new feature worktree') and three concrete actions ('detect context, recall memories, and transition to brainstorming'), matching the several-specific-actions anchor; not comprehensive since presenting workspace context and the optional walkthrough go unmentioned.

4 / 5

Completeness

The 'what' is concrete and clear, but 'when' is entirely absent — there is no 'Use when...' clause or equivalent trigger guidance, only a weak implication from 'Post-launch', which caps completeness at 3.

3 / 5

Trigger Term Quality

'feature worktree' and 'brainstorming' are terms users would plausibly say, but there are no synonyms or common variations (e.g., 'new feature branch', 'start a feature'), leaving keyword coverage incomplete.

3 / 5

Distinctiveness Conflict Risk

Scoped to a distinct post-launch phase within a feature pipeline, so it is mostly distinguishable; minor overlap risk remains with the brainstorming skill it explicitly transitions to.

4 / 5

Total

14

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

AndreJorgeLopes/devflow

Path

skills/new-feature/SKILL.md

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.