CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

coding-agents-farm

To orchestrate parallel coding-agent farms (Claude, Codex, Copilot, Gemini, etc.) on isolated git worktrees.

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./instructions/r3/core/skills/coding-agents-farm/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A strong, highly executable orchestration workflow with explicit validation checkpoints and intervention feedback loops for a risky batch operation. The main weaknesses are a verbatim-duplicated guidance block and heavy inline CLI reference tables that belong in a separate reference file.

Suggestions

Delete the duplicated model-selection paragraphs for OpenCode/Copilot/Goose (they repeat the bullet list verbatim) and keep only the bulleted version.

Move the provider/model constraint table, auto-approve flags table, known auto-approve issues, and model-id snapshot into a references/cli-reference.md, leaving a one-line pointer in SKILL.md.

Make Monitor and Merge executable: specify how each CLI's output is captured (e.g., redirect to worktrees/<name>/output.log) and give the concrete merge command (e.g., 'git merge farm/<name>' or 'gh pr create').

DimensionReasoningScore

Conciseness

The body is mostly dense, high-value reference material (CLI flags, model ids), but the model-selection guidance for OpenCode/Copilot/Goose is duplicated verbatim — once as bullets ('OpenCode: prefix with provider, e.g. `anthropic/claude-sonnet-5-5`') and again as repeated plain paragraphs — and the all-caps confirmation block could be tightened. This is more than 'minor instances of over-explanation' (anchor 4) but not 'several unnecessary explanations' across the skill (anchor 2).

3 / 5

Actionability

Launch commands are copy-paste ready per CLI (e.g., 'claude -p "PROMPT" --dangerously-skip-permissions --model claude-sonnet-5-5 --max-turns 30 --output-format json') along with concrete worktree setup and cleanup commands. Minor gaps keep it below 5: the merge step ('Merge worktree branches into the working branch') and the Monitor step ('read terminal output files') give direction without executable commands, and no command shows how output is captured to files.

4 / 5

Workflow Clarity

An explicit 8-step sequence (Plan through Report) with concrete validation checkpoints — 'Verify each worktree is clean', pre-flight auto-approve verification, 'Validate: tests pass, no unintended changes, scope respected' — plus error-recovery feedback loops (restart on failure, reassign after '3+ retries', escalate to user). The batch/destructive-operation cap does not apply since validation steps are explicitly present; this fits anchor 5 rather than 4 because checkpoints are comprehensive, not just 'most'.

5 / 5

Progressive Disclosure

Sections are well organized (role, core_concepts, process, resources), but roughly 60% of the body is inlined CLI reference material — the provider/model constraint table, auto-approve flag table, known-issues list, and model-id snapshot — that clearly belongs in a separate references/ file; no bundle files exist. Good structure with content that should be separate inline matches anchor 3; it is above anchor 2 (structure is clear, not minimal) and below anchor 4 (bulk reference content is not appropriately placed in separate files).

3 / 5

Total

15

/

20

Passed

Description

61%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 concise, distinct third-person description with strong natural trigger terms (CLI names, git worktrees), but it omits any explicit 'when to use' guidance and states only one high-level action rather than the skill's concrete capabilities. Adding a Use-when clause and naming two or three concrete operations would lift both completeness and specificity.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user wants to run multiple coding agents in parallel, cross-validate work across different models, or mentions git worktrees for parallel agent execution.'

Name two or three concrete actions instead of the single generic 'orchestrate', e.g., 'decomposes features into subtasks, launches headless CLI sessions in isolated worktrees, and monitors, intervenes, and merges results'.

Include common synonyms such as 'multi-agent' and 'run agents in parallel' so natural user phrasings match the description.

DimensionReasoningScore

Specificity

The description names the domain and one concrete mechanism — 'orchestrate parallel coding-agent farms (Claude, Codex, Copilot, Gemini, etc.) on isolated git worktrees' — but 'orchestrate' is a single generic action, not a list of specific capabilities. It is above anchor 2 (a concrete mechanism and named tools are given) but below anchor 4 (no several specific actions like decompose, launch, monitor, merge).

3 / 5

Completeness

It has a clear 'what' ('orchestrate parallel coding-agent farms... on isolated git worktrees') but no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3. It is not 4 because the 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Natural terms users would actually say are present: the CLI names 'Claude, Codex, Copilot, Gemini' and 'git worktrees'. Coverage is good but misses common variations such as 'multi-agent', 'run agents in parallel', or 'parallel execution', so it fits anchor 4 rather than the comprehensive synonym coverage of anchor 5, and is clearly above the sparse keyword coverage of anchor 3.

4 / 5

Distinctiveness Conflict Risk

The niche — orchestrating multiple coding-agent CLIs on isolated worktrees — is distinct, with specific triggers (CLI names, git worktrees) giving minimal conflict risk. It sits below anchor 5 because the broad phrasing 'parallel' could still overlap with generic multi-agent or parallel-execution skills, fitting 'mostly distinct; minor overlap risk'.

4 / 5

Total

14

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

griddynamics/rosetta

Path

instructions/r3/core/skills/coding-agents-farm/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.