team-coordination

Multi-person projects - shared state, todo claiming, handoffs

Quality

24%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/team-coordination/SKILL.md

Quality

Discovery

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is a terse, fragment-style summary that fails to articulate concrete actions or provide explicit trigger guidance. While it hints at a collaboration/multi-person workflow domain, it lacks the specificity and completeness needed for Claude to reliably select this skill from a large pool. The absence of a 'Use when...' clause and concrete action verbs significantly weakens its utility.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when multiple people or agents are collaborating on a project, claiming tasks, or performing handoffs.'

Replace fragment-style phrases with concrete action descriptions, e.g., 'Manages shared project state across multiple contributors, enables claiming and reassigning todos, and facilitates structured handoffs between team members.'

Include natural trigger terms users might say, such as 'collaboration', 'team project', 'assign tasks', 'multi-agent', 'shared todos', or 'pass off work'.

Dimension	Reasoning	Score
Specificity	The description uses vague, abstract language like 'shared state', 'todo claiming', and 'handoffs' without explaining concrete actions. It does not list specific operations Claude would perform.	1 / 3
Completeness	The description only loosely addresses 'what' with fragment-like phrases and completely lacks a 'when' clause or explicit trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also very weak, warranting a 1.	1 / 3
Trigger Term Quality	Terms like 'handoffs', 'todo claiming', and 'multi-person projects' are somewhat relevant keywords a user might use, but coverage is incomplete—missing terms like 'collaboration', 'team', 'assign tasks', 'shared workspace', or 'multi-agent'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'multi-person projects' and 'todo claiming' provides some niche specificity, but 'shared state' and 'handoffs' are generic enough to potentially overlap with project management, task tracking, or collaboration skills.	2 / 3
	Total	6 / 12 Passed

Implementation

27%

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

This skill is well-intentioned and covers the team coordination domain comprehensively, but it is far too verbose—most of the content is example templates and scaffolding that Claude could generate from brief instructions. The lack of validation/conflict-detection mechanisms and the reliance on manual markdown editing without any automated enforcement weakens the workflow. The monolithic structure with no supporting bundle files means everything is dumped into one large file.

Suggestions

Cut content by 60-70%: remove full example tables, ASCII art boxes, timezone diagrams, and standup templates. Replace with brief format specifications that Claude can expand when needed.

Add validation steps: include a script or checklist to detect stale state (e.g., claimed todos with no recent updates, conflicting file-touch declarations) rather than relying solely on manual checking.

Split into multiple files: move templates (handoff template, standup template, state.md template) into a bundle templates/ directory and reference them from the main SKILL.md.

Add a concrete conflict resolution workflow with feedback loop: what happens when two people claim the same todo or touch the same files? Currently this is just 'coordinate via Slack.'

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~350+ lines. Massive ASCII art boxes, full example tables with fake data, contributor timezone diagrams, and extensive template content that Claude could generate on its own. The core coordination protocol could be conveyed in under 80 lines. Much of this is template scaffolding rather than instruction.	1 / 3
Actionability	Provides concrete file structures, markdown templates, and a git hook script, which is good. However, much of the content is template/example data rather than executable guidance. The 'Commands' section is just cat/grep on markdown files. The actual coordination mechanism relies entirely on manually editing markdown files and hoping people push—no tooling or automation beyond a weak pre-push hook.	2 / 3
Workflow Clarity	Start/end session checklists are clear and well-sequenced. However, there are no validation checkpoints—no way to verify state consistency, no conflict detection beyond 'check the file,' and no feedback loops for when claims conflict or state.md is stale. The pre-push hook is warning-only and doesn't block, so conflicts can still occur silently.	2 / 3
Progressive Disclosure	Everything is in one monolithic file with no references to external documents. The file is extremely long with inline templates, examples, and full contributor tables that could easily be split into separate reference files (e.g., templates.md, examples.md). No bundle files exist to support progressive disclosure.	1 / 3
	Total	6 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: alinaqi/claude-bootstrap
Commit: 7e5f7a2

Reviewed: 3 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.