team-coordination

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

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/team-coordination/SKILL.md

Quality

Content

71%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 highly actionable with concrete commands, paths, and ready-to-use templates organized into clear workflows, but it is padded with redundant ASCII banners and duplicated checklists, and it keeps all templates inlined rather than splitting them into one-level-deep reference files.

Suggestions

Move the full file templates (state.md, contributors.md, handoff, standup) into reference files under ./references/ and replace them with concise inline summaries plus clearly signaled links, raising progressive_disclosure.

Remove the decorative ASCII-art boxes and deduplicate the start/end-session checklists (keep a single markdown checklist) to improve conciseness.

Strengthen the pre-push hook into a blocking validate-then-fix feedback loop so workflow_clarity can reach 5.

Dimension	Reasoning	Score
Conciseness	Mostly useful, domain-specific content, but padded with decorative ASCII-art banners and duplicated checklists (start/end-session boxes repeated as a final markdown checklist), so it could be meaningfully tightened; not a 2 because the bulk is relevant templates and structures rather than concepts Claude already knows.	3 / 5
Actionability	Provides concrete file paths, copy-paste-ready bash commands ('git pull origin main', grep for active sessions), a complete pre-push hook script, and fully filled-in templates with example data covering the common coordination cases.	5 / 5
Workflow Clarity	Start-session, claim, during-work, end-session, and handoff processes are clearly sequenced with checklists, and a pre-push state-diff check plus conflict-prevention steps provide validation; not a 5 because the hook validation is warning-only and lacks an explicit validate-then-fix feedback loop.	4 / 5
Progressive Disclosure	Section headers give reasonable structure, but at ~470 lines the skill is monolithic with several large file templates (state.md, contributors.md, handoff, standup) inlined that would belong in separate reference files, and no external references are signaled; no bundle files exist to offset this.	3 / 5
	Total	15 / 20 Passed

Description

53%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 third-person, on-topic, and targets a distinct niche, but it lists capabilities rather than actions, omits natural synonyms, and lacks an explicit 'Use when' trigger clause, which caps completeness at 3.

Suggestions

Convert the capability nouns into concrete verb-led actions, e.g. 'Coordinates multiple Claude Code sessions on one repo: claims todos, syncs shared state, and writes handoffs.'

Add an explicit trigger clause, e.g. 'Use when multiple developers are working on the same repo, claiming todos, or handing off work.'

Include natural user phrasings like 'team coordination', 'collaboration', and 'multiple developers' to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Multi-person projects') and three concrete capabilities ('shared state, todo claiming, handoffs'), but these are noun-phrase capabilities rather than verb-driven actions and coverage is not comprehensive.	3 / 5
Completeness	Provides a clear 'what' but the description field itself has no 'Use when...' clause; the 'when' is only weakly implied by 'Multi-person projects', so completeness is capped at 3 per the missing-trigger-guidance rule.	3 / 5
Trigger Term Quality	Contains relevant keywords ('multi-person projects', 'shared state', 'handoffs') but misses common natural synonyms a user would say such as 'team', 'collaboration', or 'multiple developers'.	3 / 5
Distinctiveness Conflict Risk	Targets a clear niche (multi-person team coordination) with distinct triggers and only minor overlap risk with adjacent project-management skills; not a 5 because the phrasing is brief and lacks sharply distinguishing trigger phrases.	4 / 5
	Total	13 / 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: alinaqi/claude-bootstrap
Path: skills/team-coordination/SKILL.md
Commit: abc600e

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.