CtrlK
BlogDocsLog inGet started
Tessl Logo

swarm

Deprecated compatibility shim for team execution

51

Quality

55%

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

86%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 an efficient, well-structured deprecated-shim notice that gives a concrete redirect command and a brief justification for the file's existence. Its only blemish is a leftover "Task: {{ARGUMENTS}}" template marker that slightly muddies the do-not-invoke message.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: "Hard-deprecated. Do not invoke or route this skill for new work." followed by a single concrete redirect and one sentence justifying the file's existence, fitting "Lean and efficient; assumes Claude's competence; every token earns its place." It is not a 4 because there is no over-explanation to trim.

5 / 5

Actionability

"Use `$team` or `omx team` directly for coordinated multi-agent execution" is a concrete, executable redirect command, matching "Mostly executable guidance; concrete code or commands with minor gaps." It is not a 5 because no usage example of the replacement is given, and not a 3 because the command is specific and copy-paste ready.

4 / 5

Workflow Clarity

The single redirect action is unambiguous and benefits from the simple-skill exception, but the leftover "Task: {{ARGUMENTS}}" template marker is mildly confusing in a do-not-invoke skill, fitting "Clear sequence with most checkpoints present; minor validation gaps." It is not a 5 because of that template inconsistency, and not a 3 because the instruction is otherwise fully clear.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references (none exist), and is well-organized with a clear header, so the simple-skill exception applies and progressive disclosure scores 5, matching "Clear overview with well-signaled one-level-deep references; content appropriately split."

5 / 5

Total

18

/

20

Passed

Description

25%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 is terse but communicates only the skill's deprecated status, not a usable capability or trigger. It lacks any "Use when" guidance and overlaps heavily with the team skill it defers to. Specificity and trigger quality are both weak.

Suggestions

Add an explicit trigger clause such as "Use when a caller requests the legacy `swarm` interface" so the when is stated, not inferred.

Replace the status-only phrasing with the concrete redirect action, e.g. "Redirects legacy `swarm` requests to `$team`/`omx team` for coordinated multi-agent execution."

Include natural synonyms a user might actually say (e.g. "swarm", "multi-agent", "team") to improve trigger-term quality.

DimensionReasoningScore

Specificity

The description "Deprecated compatibility shim for team execution" names the domain (team execution) and what the skill is (a shim) but lists no concrete actions or capabilities, matching the score-2 anchor "Names the domain but actions are minimal or generic." It is not a 3 because no concrete actions are stated, and not a 1 because the domain is named rather than being entirely vague.

2 / 5

Completeness

The description offers a vague meta-"what" (it is a deprecated shim) and entirely omits any "when"/"Use when" guidance, matching "Has a vague 'what' and no 'when'." It is not a 3 because the "what" describes status rather than a clear capability, and the missing trigger clause caps completeness at 3 anyway.

2 / 5

Trigger Term Quality

"team execution" is a generic keyword but the phrase is technical/boilerplate ("compatibility shim") with no natural user-facing trigger phrasing, fitting "One or two generic keywords; missing the natural phrases users say." It is not a 3 because there is no meaningful coverage of common variations, and not a 1 because a relevant keyword is present.

2 / 5

Distinctiveness Conflict Risk

"compatibility shim for team execution" directly overlaps with the real Team-mode skill it redirects to, giving high conflict risk, matching "Very broad; high overlap risk with many similar skills." It is not a 3 because the overlap is with its own replacement, and not a 1 because it is tied to a specific domain.

2 / 5

Total

8

/

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