CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dev-server

Manage Next.js dev servers across worktrees, and the worktrees themselves — create one (`wt new`), find finished ones (`wt stale`), remove them (`wt rm`). Start, stop, and read logs from dev servers. Agents can access logs from any running session, regardless of who started it. Use whenever creating, adding or removing a git worktree in this repo.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

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

Exceptionally actionable and rigorous — every command is executable, every risky operation has a validation guard, and the failure-mode analysis (probe verdicts, env layering, cache behavior) is the kind of hard-won knowledge that cannot be inferred. The costs are length and monolithism: dated measurements and bug-history narrative bloat the token budget, and the absence of any reference files makes SKILL.md carry detail that belongs in separate documents.

Suggestions

Split stable-but-deep topics (Auth Hub setup, RGB proxy, cache-size analysis, queued test runs) into files under references/ and keep SKILL.md as an overview with one-level-deep, clearly signaled links — e.g. 'Auth hub setup: See [references/auth-hub.md]'.

Move dated measurements and historical narratives ('Measured 2026-08-16', 'Until 2026-08-19', the missingModule bug history) into an 'old patterns / history' section or the relevant reference file, keeping SKILL.md to the current rule plus the one-line rationale.

Trim narrative asides that restate the lesson ('That is not academic', 'This is why ... cost real time as a habit') down to the operative guidance, preserving the concrete numbers but not the storytelling around them.

DimensionReasoningScore

Conciseness

Mostly dense, non-inferable operational knowledge, but at ~870 lines it is interleaved with dated measurements ('Measured 2026-08-16', 'Until 2026-08-19', 'On 2026-10-07, 32 files were in all 19,197 cache records') and narrative asides ('That is not academic', the missingModule bug history) that sit outside any old-patterns section and could be tightened. Not 2 because almost none of it explains things Claude already knows; not 4 because the dated narrative padding is more than minor.

3 / 5

Actionability

Copy-paste-ready `node .claude/skills/dev-server/cli.mjs ...` invocations throughout, exact env-var names with defaults, a complete command table, verdict-to-remedy mappings, and a one-liner for keypair regeneration. Fully executable guidance covering the common cases, matching the 5 anchor.

5 / 5

Workflow Clarity

Multi-step flows (queued test runs with run/wait/exit-code semantics, `unwedge`, `wt new`, in-place branch switching) are explicitly sequenced with validation checkpoints and feedback loops: 'fails unless `git status -sb` prints `## <branch>` alone', poll for `ready: true`, re-probe after unwedge, the `wt rm` daemon guard, and reading `dbHost` before anything that writes. Destructive operations all carry explicit guards rather than silent execution.

5 / 5

Progressive Disclosure

In-file structure is good (clear section headers, real script paths verified against the scripts/ bundle) but there is no references/ directory at all — the auth hub setup, RGB proxy, cache-size analysis, and test-queue internals are all inlined in one ~870-line SKILL.md instead of split into one-level-deep reference files. Matches the 3 anchor ('content that should be separate is inline'); not 4 because entire topic areas belong in separate files.

3 / 5

Total

16

/

20

Passed

Description

83%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 description: concrete, third-person, command-specific, with an explicit 'Use whenever' trigger for worktree operations. Its only weaknesses are a trigger clause that covers worktree actions but not the dev-server start/stop/logs half of the skill, and a few missing natural synonyms for the other verbs.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with the exact commands that perform them — 'create one (`wt new`), find finished ones (`wt stale`), remove them (`wt rm`)', 'Start, stop, and read logs from dev servers' — comprehensively covering the skill's core surface. Not 4: there are no material gaps in the action coverage for the capability set described.

5 / 5

Completeness

Both parts are present: a clear 'what' (manage dev servers and worktrees, with named commands) and an explicit 'when' ('Use whenever creating, adding or removing a git worktree in this repo'). Not 5: the trigger clause covers only worktree operations, leaving the dev-server start/stop/log use cases without an explicit 'when'.

4 / 5

Trigger Term Quality

Contains the natural terms a user would say — 'dev server', 'worktree', 'git worktree', 'start', 'stop', 'logs' — but omits common phrasings for other verbs the skill covers ('restart', 'tail', 'test run', 'branch'). Good coverage with a few natural terms missing, matching the 4 anchor rather than the comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche — Next.js dev servers and git worktrees in this repo, identified by named `wt` commands — with triggers unlikely to match any other skill. Minimal conflict risk, matching the 5 anchor.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (870 lines); consider splitting into references/ and linking

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

civitai/civitai

Path

.claude/skills/dev-server/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.