CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

new-feat

Use when starting a piece of feature or fix work in this repository — taking or opening its GitHub issue, cutting the branch (a worktree on the local bare repo, an in-place branch on the remote environment) and producing the implementation plan, including the wiki pages the work will make stale and its observability plan. Also the step for turning a tracker finding into a branch without publishing it.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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.

An exceptionally actionable, well-sequenced workflow skill: concrete commands at every step, upfront gate probes, and a genuine pre-implementation validation gate with feedback loops. Its only costs are length-adjacent — a few trimmable asides and a Step 2 checklist that pushes against what belongs inline versus in a reference file.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — it never explains known concepts, and every aside carries non-inferable repo-specific rationale (e.g. why the refspec is explicit for a bare clone). A few long parentheticals and philosophical asides ("that is a real value and usually the honest one") could be trimmed, landing it just below the lean anchor.

4 / 5

Actionability

Guidance is copy-paste ready throughout: the exact probe snippet (`command -v gh ...`, `echo PERSONAL || echo REMOTE`), `gh issue view` with `--json` fields, `git worktree add ... -b <branch> refs/remotes/origin/main`, the exact `NEW-FEAT.md` opening format, and the designated `-B` idempotent checkout — parameters are real placeholders, not pseudocode.

5 / 5

Workflow Clarity

The sequence is explicit ("Four things, in this order — each depends on the one before"), gates are probed once before Step 0, the branch name is checked for collisions before cutting, and Step 3 is a full validation feedback loop (fix, reject-with-named-fact, or escalate before any code) — checkpoints and error-recovery paths are explicit, including the "When a gate cannot run" fallbacks.

5 / 5

Progressive Disclosure

Structure is good: the one bundle reference (`references/skills-routing.md`) is clearly signaled in Step 4, verified to exist, and one level deep, and wiki/skill pointers are consistently cited. The very long Step 2 plan checklist and the dense stacked-PR paragraph are borderline content that could partly live in reference files, keeping it below the cleanly-split anchor.

4 / 5

Total

18

/

20

Passed

Description

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

A strong, third-person description that states both what the skill does and when to use it in concrete, repo-specific terms with no fluff or over-claims. Its only weaknesses are modest: a slightly thin set of synonym trigger phrases and minor overlap risk with adjacent workflow skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "taking or opening its GitHub issue, cutting the branch (a worktree on the local bare repo, an in-place branch on the remote environment) and producing the implementation plan, including the wiki pages the work will make stale and its observability plan" — with comprehensive, non-generic coverage; nothing is vague or padded.

5 / 5

Completeness

It explicitly answers both questions: "Use when starting a piece of feature or fix work in this repository..." gives concrete 'when' triggers, and the enumerated issue/branch/plan actions give a clear 'what', matching the anchor with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrases are present ("starting a piece of feature or fix work", "GitHub issue", "tracker finding", "implementation plan"), but common variations and synonyms (e.g. "new feature", "bugfix", "start work on") are missing, which is a few natural terms short of the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

The niche (issue → branch → plan pipeline for new work) is distinct with its own triggers, but the description does not disambiguate against closely related workflow skills it names in passing (e.g. orchestrate, write-issue), leaving minor overlap risk.

4 / 5

Total

18

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 possibly missing (scripts/changeset-required.sh)

Warning

Total

15

/

16

Passed

Repository

englishstreetventures/osn

Path

.claude/skills/new-feat/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.