CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

polyphony

Multi-agent orchestration with container-isolated workspaces — each agent session runs in its own Docker container with independent git branches

54

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/polyphony/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 lean, well-structured overview with concrete CLI commands and config examples, but its batch-orchestration workflow lacks explicit validation checkpoints and feedback loops, and it carries all content inline with no external references to split out.

Suggestions

Add concrete validation/verification steps to the workflow (e.g., what 'verify' checks, test commands to run before landing a PR, and an explicit fix-and-retry loop on failure).

Show example contents for config.yaml, identities.yaml, and agents.yaml rather than only listing their purposes in a table.

Consider splitting the Complexity Scoring and Routing detail into a referenced file to improve progressive disclosure and reduce inline bulk.

DimensionReasoningScore

Conciseness

The body is efficient and well-compressed into tables, terse bullets, and code blocks without explaining concepts Claude already knows, with only minor descriptive prose that could be trimmed.

4 / 5

Actionability

Provides concrete, copy-pasteable CLI commands ('polyphony init', 'polyphony spawn "Fix auth bug"'), an executable prerequisite check, and a concrete routing YAML example, with minor gaps such as omitted contents for config.yaml/identities.yaml.

4 / 5

Workflow Clarity

A clear sequence exists via the task lifecycle diagram and orchestrator loop ('discover -> claim -> route -> provision -> run -> verify -> land'), but for a batch orchestration system the validation/verification steps are only labeled ('VERIFYING') with no concrete checks or error-recovery feedback loops, capping the score at 3.

3 / 5

Progressive Disclosure

Well-organized into clear single-level sections (Architecture, Lifecycle, Configuration, Routing, CLI) with no nested references; at ~125 lines it exceeds the under-50-line simple-skill exception, so it falls just short of a 5 that would require well-signaled one-level-deep external references.

4 / 5

Total

15

/

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 conveys what the skill does via a concrete container-isolation mechanism, but lacks any explicit 'when to use' trigger guidance and misses several natural user phrasings, capping completeness and trigger quality at 3.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill (e.g., spawning parallel agents, isolating agent workspaces).

Include natural trigger terms users would say such as 'parallel agents', 'spawn agents', or 'isolated workspaces' alongside the technical jargon.

Optionally enumerate 2-3 concrete actions (provision, route, land PRs) to lift specificity above a single-capability description.

DimensionReasoningScore

Specificity

Names the domain ('Multi-agent orchestration with container-isolated workspaces') and a concrete mechanism ('own Docker container with independent git branches'), but describes a single capability rather than listing several discrete actions.

3 / 5

Completeness

The 'what' is clearly stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Contains relevant terms ('multi-agent orchestration', 'Docker container', 'git branches') but omits natural phrasings users would actually say such as 'parallel agents', 'spawn agents', or 'isolated workspaces'.

3 / 5

Distinctiveness Conflict Risk

The container-isolation niche is fairly distinct, though there is minor overlap risk with the related agent skills (spawn-team, agent-teams) referenced in the body.

4 / 5

Total

13

/

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

alinaqi/maggy

Path

skills/polyphony/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.