x-team

Use when the user asks for parallel team-style execution of multiple features in one project — orchestrates a team lead + N dev workers, one feature per worktree, each gated on x-qa E2E tests, with blocker escalation to human via SendMessage. Hard requires `plugin.omc` (TeamCreate/SendMessage primitives) and `.x-skills/x-qa/profile.json` (E2E gate).

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

88%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 highly actionable and well-sequenced with strong validation feedback loops for a batch orchestration skill. Its only gap is a couple of referenced paths (gotchas.md, external ../x-shared and ../x-omo files) that do not resolve within the provided bundle.

Suggestions

Add the missing gotchas.md to the bundle or remove the 'See gotchas.md' reference so navigation does not dead-end.

Verify the ../x-shared/*, ../x-omo/SKILL.md, ../x-qa/SKILL.md, and ../x-worktree/SKILL.md dependency paths exist in the install tree, or note that they are cross-plugin prerequisites rather than in-bundle files.

Dimension	Reasoning	Score
Conciseness	The body assumes Claude's competence and is dominated by terse, executable blocks rather than concept explanations, but a few dense prose passages (Bootstrap step 5, Persist Lessons) carry minor padding that could be tightened, keeping it just below the lean-anchor 5.	4 / 5
Actionability	It provides copy-paste-ready JSON tool calls (TeamCreate, TaskCreate, SendMessage, TeamDelete), concrete script invocations with full argument lists, and exact flag semantics, covering the common execution cases.	5 / 5
Workflow Clarity	Phases 1-8 are explicitly sequenced with validation checkpoints (refuse-if-missing bootstrap, worktree-fail abort + TeamDelete, QA gate, idempotence guard, shutdown wait-with-timeout), giving clear feedback loops for a batch operation.	5 / 5
Progressive Disclosure	The body is an overview that offloads detail to clearly signaled one-level-deep references (decomposition-rules, monitor-loop, worker-preamble, blocker-escalation, auto-merge-policy, feature-branch-mapping) that all resolve as real files; however gotchas.md is referenced but absent from the bundle and ../x-shared/* and ../x-omo/SKILL.md do not resolve here, so structure is strong but not flawless.	4 / 5
	Total	18 / 20 Passed

Description

80%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 explicit, distinctive, and answers both what and when with a concrete trigger phrase. Its main weakness is jargon-heavy language that under-serves natural user phrasing, capping trigger-term quality at the midpoint.

Suggestions

Add 1-2 natural-language trigger synonyms a user would actually say (e.g. 'run several features at once', 'parallelize feature work') before the technical elaboration.

Move the hard prerequisites ('Hard requires plugin.omc ...') out of the description into the body's Hard Requirements section to keep the description lean and trigger-focused.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete mechanics ('team lead + N dev workers, one feature per worktree, each gated on x-qa E2E tests, with blocker escalation to human via SendMessage'), but it is one composite orchestration capability rather than a list of multiple distinct discrete actions, so it sits just below the comprehensive-anchor 5.	4 / 5
Completeness	It explicitly answers both 'what' (orchestrates lead + N workers, one feature per worktree, QA-gated, blocker escalation) and 'when' with a concrete trigger phrase, matching the anchor for clearly and explicitly answering both.	5 / 5
Trigger Term Quality	The opening 'Use when the user asks for parallel team-style execution of multiple features in one project' is a natural phrase, but the rest leans on internal jargon (plugin.omc, x-qa, SendMessage, TeamCreate) users would not actually say, and common synonyms/variations are missing.	3 / 5
Distinctiveness Conflict Risk	The niche is sharply defined (parallel team-style multi-feature execution) with hard plugin/profile prerequisites, making it very unlikely to trigger for the wrong skill.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: quangtran88/x-skills
Path: skills/x-team/SKILL.md
Commit: f17a69e

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.