CtrlK
BlogDocsLog inGet started
Tessl Logo

gastown

Multi-agent orchestrator for Claude Code. Use when user mentions gastown, gas town, gt commands, bd commands, convoys, polecats, crew, rigs, slinging work, multi-agent coordination, beads, hooks, molecules, workflows, the witness, the mayor, the refinery, the deacon, dogs, escalation, or wants to run multiple AI agents on projects simultaneously. Handles installation, workspace setup, work tracking, agent lifecycle, crash recovery, and all gt/bd CLI operations.

74

Quality

92%

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

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable operational manual with excellent workflow sequencing, pervasive validation/verification feedback loops, and well-structured one-level-deep progressive disclosure. Its only weakness is verbosity — the persona/creative-flourish examples and repeated JSON demonstration blocks inflate the body beyond what a leaner skill would need.

Suggestions

Condense the Creative Freedom section: trim the four elaborate example blocks (spontaneous diagram, proactive suggestion, in-world moment, character voice) to a single representative illustration — the principle is clear without all four.

Show the AskUserQuestion JSON pattern once instead of repeating full payload blocks in First Contact, Execution Modes, Interaction Style, and Tutorial Navigation; reference the one canonical example thereafter.

Move the full inline Commands listing and the Capability Checklist table into references/commands.md, keeping SKILL.md as a tighter overview that signals where the exhaustive command reference lives.

DimensionReasoningScore

Conciseness

The 705-line body is mostly efficient in its operational parts but is padded by the elaborate Creative Freedom section (four full ASCII/celebration/character-voice example blocks) and repeated full AskUserQuestion JSON demonstrations across First Contact, Execution Modes, and Interaction Style — material that could be tightened without losing the principle.

2 / 3

Actionability

Provides fully executable, copy-paste-ready guidance throughout — a complete Commands reference ("gt sling <bead> <rig>", "gt doctor", "bd doctor", "gt mail send <rig>/witness -s 'Patrol' -m '...'") and concrete verification checklists, not pseudocode.

3 / 3

Workflow Clarity

Multi-step processes are clearly sequenced with explicit validation checkpoints and feedback loops — the System Readiness Checklist with BLOCKERS, the 6-step Full Flow Verification, and "Never Assume - Verify Everything" (validate via gt doctor / gt doctor --fix → retry) exactly match the score-3 anchor.

3 / 3

Progressive Disclosure

A clear overview points to five real, verified reference files (tutorial.md, setup.md, commands.md, concepts.md, troubleshooting.md) via a well-signaled table mapping file → contents → when-to-load, plus grep navigation strategies; references are one level deep with no nested indirection.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 clearly states both what the skill does and when to use it, with extensive natural trigger terms and a distinctive niche that won't conflict with other skills. Voice is correctly third person throughout, so no specificity penalty applies.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Handles installation, workspace setup, work tracking, agent lifecycle, crash recovery, and all gt/bd CLI operations" — matching the score-3 anchor of several specific concrete actions rather than just naming a domain.

3 / 3

Completeness

Explicitly answers both what ("Multi-agent orchestrator for Claude Code... Handles installation, workspace setup, work tracking...") and when ("Use when user mentions gastown, gas town, gt commands... or wants to run multiple AI agents"), with an explicit 'Use when' trigger clause.

3 / 3

Trigger Term Quality

Broad coverage of natural terms a user of this system would say — "gastown, gas town, gt commands, bd commands, convoys, polecats, crew, rigs, slinging work, multi-agent coordination" plus "run multiple AI agents on projects simultaneously"; these are the domain's actual vocabulary, not generic jargon.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive niche — a named product with unique command names (gt, bd) and idiosyncratic in-world terminology (polecats, convoys, beads, rigs, the witness) that is extremely unlikely to trigger for an unrelated skill.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

Total

15

/

16

Passed

Repository
numman-ali/n-skills
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.