team-coordination

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

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

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

Quality

Content

65%

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 with concrete templates and scripts, but it is verbose (decorative boxes, duplicated checklists), lacks enforced validation gates, and is monolithic with no progressive disclosure into reference files.

Suggestions

Collapse the decorative ASCII boxes and remove the duplicated start/end checklists, keeping one concrete version of each.

Move large templates (state.md, contributors.md, handoff, standup) into reference files under references/ and link to them one level deep from SKILL.md.

Promote the pre-push state check from a soft warning to an explicit validation step with a retry-on-stale loop before pushing shared state.

Dimension	Reasoning	Score
Conciseness	The body is actionable throughout but padded with decorative ASCII boxes and duplicated content (start/end session boxes reappear as markdown checklists), so it could be tightened considerably.	2 / 3
Actionability	It provides copy-paste-ready markdown templates (state.md, contributors.md, handoffs), specific bash commands, and a complete pre-push git hook script.	3 / 3
Workflow Clarity	Start/end workflows are clearly sequenced with numbered checklists, but the only verification (the pre-push state check) is explicitly "Warning only, don't block," leaving validation checkpoints implicit.	2 / 3
Progressive Disclosure	Sections are well-organized, but the ~478-line body is monolithic with every template inline and no external reference files, so content that should be split stays in SKILL.md.	2 / 3
	Total	9 / 12 Passed

Description

67%

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 specific and occupies a distinct niche, but it omits an explicit "Use when..." trigger and leans on somewhat internal terminology rather than natural user phrasings.

Suggestions

Add an explicit trigger clause, e.g. "Use when multiple developers are working on the same repo and you need to avoid conflicting edits."

Swap internal jargon ("shared state", "todo claiming") for natural user terms ("team projects", "claiming tasks", "handing off work").

Dimension	Reasoning	Score
Specificity	The phrase "shared state, todo claiming, handoffs" lists three concrete, specific capabilities rather than vague abstractions, matching the multiple-specific-actions anchor.	3 / 3
Completeness	It states what the skill does (shared state, claiming, handoffs) but lacks an explicit "Use when..." trigger clause, which caps completeness at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	Terms like "shared state" and "todo claiming" are internal/technical phrasings; a user would more naturally say "team project" or "working together," so natural-term coverage is partial.	2 / 3
Distinctiveness Conflict Risk	"Multi-person projects" with team-coordination capabilities carves a clear, distinct niche unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 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: bb6195f

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.