CtrlK
BlogDocsLog inGet started
Tessl Logo

gc-dispatch

Routing work to agents with gc sling and formulas

52

Quality

58%

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

Fix and improve this skill with Tessl

tessl review fix ./internal/bootstrap/packs/core/skills/gc-dispatch/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 a well-organized, actionable reference with concrete commands and useful guards, respecting token budget while remaining clear. It is held back from top marks only by minor verbosity in formula descriptions, a lack of output/error examples, and the absence of bundle files for the large formula/convoy catalogs.

DimensionReasoningScore

Conciseness

The body is mostly efficient with terse command examples and inline comments and no padding about concepts Claude already knows, matching 'Efficient; minor instances of over-explanation that could be trimmed'; a few formula blurbs are slightly prose-y, keeping it just below a 5.

4 / 5

Actionability

It provides concrete, copy-paste-ready `gc sling`/`gc convoy`/`gc order` commands with real flags and placeholders covering the common cases, matching 'Mostly executable guidance; concrete code or commands with minor gaps'; missing output/error examples keep it from a 5.

4 / 5

Workflow Clarity

Dispatch flows are organized by type with implicit sequencing, and guards like 'Beads must be in the agent's rig database' and the cross-rig block act as validation checkpoints plus a migration note, matching 'Clear sequence with most checkpoints present; minor validation gaps'.

4 / 5

Progressive Disclosure

The body is a single self-contained file with clear section headers (Quick reference, Targeting, Formulas, Convoys, Orders) and no nested references, matching 'Good structure; most content is appropriately placed; references mostly clear; minor organization gaps'; it is a 4 rather than 5 because the formula/convoy/order catalogs are inlined and could be split into bundle files.

4 / 5

Total

16

/

20

Passed

Description

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

The description names the domain and tooling but stays terse and generic, lacking concrete actions and any explicit 'Use when' trigger. It is reasonably distinct thanks to the 'gc sling' jargon but would benefit from concrete verbs and trigger guidance.

Suggestions

Add a 'Use when ...' clause naming concrete triggers (e.g. 'Use when assigning a bead or formula to an agent, creating a convoy, or routing work across sessions').

Replace the generic verb 'Routing' with multiple concrete actions (e.g. 'Route beads, instantiate formulas, and group work into convoys').

Include natural user phrasings like 'assign work to an agent' or 'send a bead' alongside the 'gc sling' jargon.

DimensionReasoningScore

Specificity

The phrase 'Routing work to agents' names the domain and one generic action (routing), with 'gc sling and formulas' naming tools but no multiple concrete actions; matches the anchor 'Names the domain but actions are minimal or generic' and falls short of the 3-anchor's '1-2 concrete actions'.

2 / 5

Completeness

It states a clear 'what' (routing work to agents) but provides no 'when'/Use-when clause, matching the anchor 'Has a clear what but when is missing or only weakly implied'; per the guideline a missing Use-when caps completeness at 3.

3 / 5

Trigger Term Quality

Keywords like 'gc sling' and 'formulas' are technical jargon rather than natural user phrasing, and natural variations users would actually say (e.g. 'assign work', 'send a bead') are missing, placing it between anchor 2 and 3 and closer to 2.

2 / 5

Distinctiveness Conflict Risk

The tool-specific terms 'gc sling' and 'formulas' carve a clear niche with minimal overlap risk, matching 'Mostly distinct; minor overlap risk with closely related skills'; not a 5 because the phrasing is still somewhat generic ('routing work to agents').

4 / 5

Total

11

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
crypt0nerd1/gascity
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.