CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cc-team-workflow

Orchestrate a hierarchical team of Claude Code subagents (lead → worker → validator → synthesizer) with learned archetype role-fit and structured retries, entirely in-session with no PI or external-model dependency. Use when Opus wants to delegate a decomposable task to an all-Claude team with validation and retries. Sibling of team-workflow (which uses external PI models).

Quality

80%

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 ./__solutions/cc-team-workflow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 a model of token efficiency and the 12-phase workflow is clearly sequenced with real validation checkpoints and feedback loops. It is let down by execution gaps: the pivotal Workflow-engine wiring example is left as commented pseudocode, and the bundle is missing the engine, roster, and persona files the instructions depend on, so a reader cannot actually run the skill end-to-end from what ships. Strong on paper, incomplete in practice.

Suggestions

Ship the referenced files or remove the references: engine/team-workflow.engine.js, roster.json / default-roster.json, and personas/<archetype>.md are named as the skill's core mechanism but are absent from the bundle — either include them or rewrite the phases to work without them.

Make the Workflow snippet executable: replace the commented agent() body and '<abs path>' placeholder with real code that reads subagent_type/tier from roster.json and calls agent(), or explicitly justify why the wiring must be filled in by the reader.

Add a fallback path for when the Workflow tool or engine is unavailable (Phase 2 preflight currently only checks readability), e.g. how to run the four helper scripts standalone to salvage partial value from the skill.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what subagents, DAGs, or retry loops are; every phase is compressed to its decision-relevant content (e.g. "Phase 7 — Retry / bounce (W): N=2 retries with feedback; the two-track cutoff ... decides ship-vs-regress"). It earns anchor 5 ('every token earns its place'); the only candidates for trimming are the two v1-deferred caveats, but both carry operational weight (do not design competitive nodes in v1), so this is not the 'minor instances of over-explanation' of anchor 4.

5 / 5

Actionability

The helper-script guidance is copy-paste ready ("echo '{...}' | npx tsx scripts/<name>.ts", plus a fully instantiated roster-postmortem input example), but the centerpiece Workflow snippet is pseudocode: the agent() binding body is a comment ("// Build the subagent prompt from node.prompt + the archetype persona ...") and the import path is an "<abs path>" placeholder. This matches anchor 3 ('pseudocode instead of executable code; missing key details') rather than 4, because the primary execution path cannot be run as written and the persona/roster files it depends on are not in the bundle.

3 / 5

Workflow Clarity

The 12 phases are explicitly sequenced with O/W ownership and validation checkpoints throughout: Phase 5 validates the RunSpec ("spec_invalid → fix and retry"), Phase 7 is a feedback-driven retry loop with a two-track cutoff, Phase 8 enumerates error-recovery options on escalation, and Phase 10 gates shipping on artifact-contract-check plus tests per tests_posture. This matches anchor 5 (clear sequence, explicit validation, feedback loops for error recovery); the batch-operation cap does not apply because batch dispatch is exactly what Phase 10 validates.

5 / 5

Progressive Disclosure

The SKILL.md is a genuine overview with well-signaled one-level-deep pointers (references/escalation-contract.md, references/run-spec-schema.md, references/scoring-protocol.md, and four scripts/*.ts — all real, substantive files), but scored against the actual bundle several core referenced paths do not exist: engine/team-workflow.engine.js (the central mechanism, referenced three times), roster.json, default-roster.json, and personas/<archetype>.md. Structure and signaling are better than anchor 3, but the missing heart-of-the-system files are more than the 'minor organization gaps' of anchor 4 — navigation breaks precisely where the reader needs to go deepest.

3 / 5

Total

16

/

20

Passed

Description

75%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 strong description that names concrete mechanisms, gives an explicit use-when clause, and carefully disambiguates its sibling skill. Its weaknesses are trigger vocabulary laced with internal jargon (PI, archetype, Opus) and a when-clause written from the model's perspective rather than as user-facing trigger phrases. All four dimensions land at 4 — solid but not exemplary.

DimensionReasoningScore

Specificity

Quotes several concrete actions — "Orchestrate a hierarchical team of Claude Code subagents (lead → worker → validator → synthesizer)", "learned archetype role-fit", "structured retries", "delegate a decomposable task ... with validation and retries" — which matches the 'lists several specific actions; minor gaps' anchor. Not a 5 because coverage stops at orchestration/delegation mechanics and never mentions the run artifacts or postmortem loop, and not a 3 because it names the full pipeline roles plus three distinct mechanisms rather than 1-2 actions.

4 / 5

Completeness

Both parts are explicit: the what ("Orchestrate a hierarchical team ... with learned archetype role-fit and structured retries") and the when ("Use when Opus wants to delegate a decomposable task to an all-Claude team with validation and retries"), matching anchor 4. It falls short of anchor 5 because the when-clause is framed from the model's perspective ("Opus wants") rather than concrete user trigger phrases, and there is no do-not-use guidance in the description itself.

4 / 5

Trigger Term Quality

Includes natural phrases a user would plausibly say — "delegate", "team", "subagents", "validation", "retries", "decomposable task" — matching 'good keyword coverage; a few natural terms missing'. Not a 5 because common variations like "multi-agent", "parallel agents", or "fan out" are absent and jargon terms ("PI", "archetype", "Opus") dominate; not a 3 because the core natural trigger vocabulary is present and well-chosen.

4 / 5

Distinctiveness Conflict Risk

The niche is explicit and disambiguated from its nearest neighbor — "entirely in-session with no PI or external-model dependency. ... Sibling of team-workflow (which uses external PI models)" — which is 'mostly distinct; minor overlap risk with closely related skills'. Not a 5 because the trigger terms ("delegate", "team", "validation", "retries") are identical to the sibling skill's, so a user request without the all-Claude/external distinction could route to the wrong skill; clearly above anchor 3 since the description actively separates the two.

4 / 5

Total

16

/

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

KennethJefferson/ccg_ccSkill_CCTeamWorkflow

Path

__solutions/cc-team-workflow/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.