CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dev-instance

Run the current worktree as a production-shaped local dev instance with web, Slack, or both, on a real LLM + Postgres. Each developer uses their own set of Slack apps from their own machine's pool store, so many worktrees (yours and a teammate's) can run reachable at once without colliding. Use when asked to /dev-instance, "spin this up so I can QA it in Slack", or "let me test your branch end to end".

Quality

85%

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

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.

The body is highly actionable and the workflow is exceptionally well validated end to end, covering failure modes and recovery in depth. Its weaknesses are token efficiency (conversational padding and asides) and a monolithic structure that inlines troubleshooting and pool-management detail a leaner SKILL.md would push to reference files.

Suggestions

Trim conversational filler and historical asides (e.g. "This is the part people get wrong, so it's worth stating plainly", the old not-today / 4-hour rule backstory) to tighten the Slack reach section without losing the rules themselves.

Move the step-by-step Slack app rebuild procedure and the pool-minting instructions (manifest creation, poolN.env contents) into a reference file (e.g. references/slack-pool.md), keeping a one-line pointer plus the common case inline.

Consider moving the extended troubleshooting narratives (silent-bot diagnosis, browser SSO gotchas) into a references/troubleshooting.md, leaving the doctor-first guidance and top failure signatures in SKILL.md.

DimensionReasoningScore

Conciseness

Mostly dense with non-obvious operational specifics Claude could not know, but padded with conversational filler ("This is the part people get wrong, so it's worth stating plainly") and historical asides ("the old not-today / 4-hour rule") that go beyond the minor trimming of the anchor above.

3 / 5

Actionability

Copy-paste-ready commands throughout (bash scripts/dev-instance.sh up --surface web, dev doctor, npm run sandbox:local:build), exact env-var overrides, and a step-by-step Slack app rebuild procedure fully cover the common cases.

5 / 5

Workflow Clarity

The full lifecycle is clearly sequenced (up → verified reachability via canary and num_connections == 1 → report slot/URLs/handle → QA → down → verify supervisor exit and lease release) with explicit validation steps and recovery feedback loops (doctor --fix, retry up, --rotate, app rebuild).

5 / 5

Progressive Disclosure

Sections are clearly headed and all file references are one level deep, but this is a ~226-line monolith where the Slack app rebuild walkthrough and pool-minting instructions are inlined content that belongs in separate reference files; the under-50-line simple-skill exception does not apply.

3 / 5

Total

16

/

20

Passed

Description

87%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: it states a concrete, distinctive capability set and gives explicit, natural-sounding trigger phrases for when to use the skill. The only room for improvement is broadening trigger synonyms and enumerating a few more concrete actions.

DimensionReasoningScore

Specificity

Names the domain and several concrete capabilities — "production-shaped local dev instance with web, Slack, or both, on a real LLM + Postgres" plus per-machine Slack app pool stores — but the action set is one operation with modifiers rather than the comprehensive multi-action list of the top anchor.

4 / 5

Completeness

Both what ("Run the current worktree as a production-shaped local dev instance…on a real LLM + Postgres") and when (an explicit "Use when…" clause with three concrete quoted trigger phrases) are clearly and explicitly answered.

5 / 5

Trigger Term Quality

"Use when asked to /dev-instance, 'spin this up so I can QA it in Slack', or 'let me test your branch end to end'" provides natural verbatim user phrasings, but common synonyms like "run the app locally" or "dev server" are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

A clear niche — worktree-level dev instances with per-machine Slack app pools — with distinct triggers (/dev-instance, QA-in-Slack phrasing); no realistic overlap with generic run/test skills.

5 / 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: 13 missing

Warning

Total

15

/

16

Passed

Repository

yc-software/qm

Path

.codex/skills/dev-instance/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.