CtrlK
BlogDocsLog inGet started
Tessl Logo

swarm

Deprecated compatibility shim for team execution

64

Quality

75%

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/swarm/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The body is an exemplar of a minimal deprecation shim: terse, with a concrete redirect command and an unambiguous hard-stop directive. It earns top marks across conciseness, actionability, workflow clarity, and progressive disclosure.

DimensionReasoningScore

Conciseness

The body is lean and direct ('Hard-deprecated. Do not invoke or route this skill for new work.') with no padding or explanation of concepts Claude already knows, matching the 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

It provides a concrete, executable redirect ('Use `$team` or `omx team` directly for coordinated multi-agent execution') plus an explicit directive; for a deprecation shim this is complete, copy-paste-ready guidance matching the top anchor.

3 / 3

Workflow Clarity

This is a single-action skill whose action is unambiguous and includes a hard-stop instruction, so per the simple-skills scoring note it earns the top anchor without needing a multi-step workflow or validation checkpoint.

3 / 3

Progressive Disclosure

Under 50 lines with no external references needed and no bundle files present, the content is well-organized into a clear heading, directive, and redirect explanation, satisfying the simple-skill top anchor for progressive disclosure.

3 / 3

Total

12

/

12

Passed

Description

50%

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 correctly conveys that this is a deprecated redirect shim for team execution, but it describes a role rather than concrete actions, omits any 'Use when' trigger guidance, and overlaps with the very skill it points to. It lands at the middle anchor across all dimensions.

Suggestions

Add a 'Use when...' clause (or equivalent) so it is explicit when—if ever—this skill should be selected, since the rubric caps completeness at 2 without one.

Replace jargon like 'compatibility shim' with natural trigger terms a user would actually say (e.g., 'coordinated multi-agent execution', 'parallel agents').

Distinguish it from the Team skill it redirects to, or note explicitly that new work should never route here, to reduce conflict/overlap risk.

DimensionReasoningScore

Specificity

The phrase 'compatibility shim for team execution' names a domain and a role-concept but lists no concrete actions the skill performs, matching the 'names domain and some actions but not comprehensive' anchor rather than the vague level-1 or the multi-action level-3.

2 / 3

Completeness

It states what the skill is ('compatibility shim for team execution') but has no 'Use when...' or equivalent trigger guidance; per the rubric guideline a missing trigger clause caps completeness at 2.

2 / 3

Trigger Term Quality

'team execution' is a relevant keyword but 'compatibility shim' is jargon a user would not naturally say, and common variations ('coordinated', 'multi-agent', 'parallel') are absent, fitting the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

It occupies a specific niche (the swarm/team contract) but directly overlaps with the Team skill it redirects to, fitting 'somewhat specific but could still overlap with similar skills' rather than the conflict-free level-3.

2 / 3

Total

8

/

12

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
Yeachan-Heo/oh-my-codex
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.