CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

creating-workers

How to create custom specialist workers for the orchestration system

Quality

67%

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 ./skills/creating-workers/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 content is a solid, actionable guide: a copy-paste template, a complete worked example, concrete registration steps, and sound design principles. Its main weaknesses are redundancy between the two example workers, a vague final wiring step, and inlining bulk example templates that could be split into reference files.

Suggestions

Cut the Documenter example (or compress it to a scope-boundaries snippet) since it duplicates the Tester example's scaffolding, saving ~100 lines.

Make the final orchestration wiring concrete: show an actual dispatch line or short snippet demonstrating how the manager invokes a registered custom worker.

Move the full worked-example templates into a one-level-deep reference file (e.g. workers/tester-prompt.md) and keep only a condensed pattern in SKILL.md.

DimensionReasoningScore

Conciseness

The body is mostly efficient — it does not explain concepts Claude already knows — but the Documenter example largely restates the template structure already shown in full by the Tester example (~100 lines of near-duplicate scaffolding). One worked example would convey the pattern; this matches 'mostly efficient but could be tightened' rather than the noticeably padded anchor 2.

3 / 5

Actionability

The generic template is copy-paste ready with concrete placeholders, the Tester example is a complete worked instantiation, and registration gives a specific save path ('bach/skills/orchestrating-work/workers/[role]-prompt.md'). It falls short of fully executable because the final wiring step ('[your-role] Task description - delegated to custom worker') is a vague illustration of how the manager actually picks up the template.

4 / 5

Workflow Clarity

The creation flow is clearly sequenced across sections: understand worker anatomy, apply the template (with INCAPABLE refusal built in), save to the registration path, then reference it in orchestration. It is not 5 because the overall create-a-worker process is never laid out as an explicit numbered sequence, and there are no verification checkpoints (e.g., confirming the registered worker is dispatched correctly).

4 / 5

Progressive Disclosure

The skill has no bundle files, and the sections are well-organized with headers. However, at ~250 lines it inlines two full example worker templates that could live as one-level-deep reference files (mirroring the workers/ directory the registration section itself points to). This matches 'some structure but content that should be separate is inline' better than the good-structure anchor 4, which expects most bulk content split out.

3 / 5

Total

14

/

20

Passed

Description

53%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 clearly states what the skill does and is reasonably distinct, but it is a single sentence with one action verb and no 'Use when...' trigger guidance. Adding explicit trigger conditions and a broader set of concrete actions would raise it substantially.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to add, customize, or extend workers/subagents in the orchestration system.'

Enumerate the concrete actions involved: designing role scope, filling in the worker prompt template, and registering the worker under the orchestrating-work skills directory.

Include natural synonyms users would say ('custom agent', 'specialist subagent', 'add a worker') to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The phrase 'create custom specialist workers for the orchestration system' names the domain plus one concrete action ('create'), matching the anchor for naming a domain with 1-2 concrete actions. It does not list several specific actions (what creating a worker involves), so it falls below anchor 4.

3 / 5

Completeness

The 'what' is clear (create custom specialist workers for the orchestration system), but there is no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the judging guidelines. Not score 2 because the 'what' is concrete, not vague.

3 / 5

Trigger Term Quality

Relevant keywords like 'create', 'custom', 'specialist workers', and 'orchestration system' are present, but common natural variations users might say ('add a worker', 'subagent', 'agent', 'specialist') are missing. This matches the 'some relevant keywords but missing common variations' anchor rather than the good-coverage anchor.

3 / 5

Distinctiveness Conflict Risk

The description is scoped to 'the orchestration system', giving it a clear niche with minimal conflict risk against unrelated skills. Score 5 would require distinct trigger phrases, which are absent, so minor overlap risk with closely related agent/prompt-authoring skills keeps it at 4.

4 / 5

Total

13

/

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

tslateman/bach

Path

skills/creating-workers/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.