CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

new-feat

Start a feature or fix in the English Street Ventures website repository. Clarify the observable result, inspect the Astro and Cloudflare setup, plan the files and verification, then implement on the current task branch.

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/new-feat/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 lean, well-sequenced instruction body with concrete repo-specific guidance and honest verification framing. Its main weaknesses are that verification is never tied to specific commands and that the existing bundle reference (references/skills-routing.md) is orphaned — never surfaced from the body.

Suggestions

Link the existing bundle reference from the body, e.g., under 'Before implementation': 'Route sub-tasks to existing skills — see [skills-routing](references/skills-routing.md)'.

Name the actual verification commands to run (e.g., the build/preview command from package.json) so the 'checks that will verify it' are executable rather than planned.

Consider a brief validation checkpoint between Implementation and Finish (e.g., 'run the planned checks; fix and re-run before summarizing') to close the feedback loop.

DimensionReasoningScore

Conciseness

The body is lean, directive, and free of concept explanations or padding — every line instructs ('Inspect `package.json`, `astro.config.mjs`, `wrangler.jsonc`...', 'Astro output is `dist`; `wrangler.jsonc` serves that directory'). It fully assumes Claude's competence, matching anchor 5.

5 / 5

Actionability

Concrete file paths, config facts, and specific directives make the guidance mostly executable, but the verification step is never grounded in an actual command (no build/preview/check command is named), leaving minor gaps. Anchor 4 rather than 5; clearly above anchor 3's vague/pseudocode level.

4 / 5

Workflow Clarity

A clear three-phase sequence (Before implementation → Implementation → Finish) with verification planned up front ('the checks that will verify it') and honesty-enforced at the end ('Do not report an unrun check as passing'). Not anchor 5 because checkpoints are planned rather than explicit validate-then-proceed steps with recovery loops; not a destructive/batch skill so no cap applies.

4 / 5

Progressive Disclosure

The body itself is short and well-sectioned, but the bundle's `references/skills-routing.md` (a routing table to other relevant skills) is never mentioned or linked anywhere in the body — a reference that is present but not signaled, matching anchor 3. Not anchor 2 because the in-body structure is good and nothing oversized is inlined; not anchor 4 because navigation to the one provided reference is entirely missing.

3 / 5

Total

16

/

20

Passed

Description

70%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 specific, domain-anchored description with concrete workflow actions and low conflict risk, weakened only by the complete absence of a 'when to use this' trigger clause. Adding an explicit 'Use when...' sentence with common trigger variations would raise it substantially.

Suggestions

Add an explicit trigger clause, e.g., 'Use when starting a new feature, fix, or bug fix in the English Street Ventures site, or when the user asks to implement or change something on the website.'

Include common trigger variations users would naturally say — 'bug', 'issue', 'add a page', 'change the site' — alongside 'feature' and 'fix'.

Optionally mention the wrap-up (summarize changes and verification results) so the action coverage is fully comprehensive.

DimensionReasoningScore

Specificity

Enumerates several concrete actions ('Clarify the observable result, inspect the Astro and Cloudflare setup, plan the files and verification, then implement') tied to a named domain and stack. Minor gaps in coverage (e.g., the finish/reporting step is absent) keep it just below the comprehensive anchor 5, but well above anchor 3's '1-2 concrete actions'.

4 / 5

Completeness

The 'what' is clearly and concretely stated (the full feature/fix workflow), but there is no 'Use when...' clause or any equivalent explicit trigger guidance, which per judging guidelines caps completeness at 3. Not anchor 2 because the 'what' is specific, not vague.

3 / 5

Trigger Term Quality

Contains natural terms a user would say when needing this skill — 'feature', 'fix', 'website', 'Astro', 'Cloudflare', 'branch'. A few natural variations are missing (e.g., 'bug', 'issue', 'add a page'), which matches anchor 4's 'good keyword coverage; a few natural terms missing' rather than anchor 5's full synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Scoped to a single named repository ('the English Street Ventures website repository') with a distinct stack (Astro + Cloudflare), giving it a clear niche with minimal conflict risk against generic or sibling skills. Matches anchor 5.

5 / 5

Total

16

/

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

englishstreetventures/englishstreetventures.com

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.