CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-collaboration

Standard collaboration patterns for all squad agents — worktree awareness, decisions, cross-agent communication

63

Quality

75%

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 ./.copilot/skills/agent-collaboration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The body is a tight, well-structured set of concrete collaboration patterns with copy-paste-ready templates and explicit anti-patterns, with no padding and clear organization appropriate to a simple skill.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no explanation of what a worktree or git is); the brief Context section earns its place by justifying centralization, and the Patterns/Anti-Patterns are terse and direct, matching the lean-and-efficient anchor.

3 / 3

Actionability

It provides concrete executable guidance: the fallback command 'git rev-parse --show-toplevel', the exact inbox path pattern '.squad/decisions/inbox/{your-name}-{brief-slug}.md', and a copy-paste decision format template — fully actionable rather than descriptive.

3 / 3

Workflow Clarity

For a simple single-purpose skill, each pattern is clearly sequenced with concrete steps (locate TEAM ROOT, write to inbox path, apply format template), and the Reviewer Protocol handoff is unambiguous; no destructive or batch operation requires an explicit validate-retry loop.

3 / 3

Progressive Disclosure

The skill is under 50 lines, single-purpose, and references no external files (none exist in references/scripts/assets); it is well-organized into Context, Patterns, and Anti-Patterns sections, satisfying the simple-skill anchor for progressive disclosure.

3 / 3

Total

12

/

12

Passed

Description

50%

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 conveys the skill's scope reasonably but relies on topic labels rather than concrete actions and entirely omits a 'when to use' trigger clause, which caps several dimensions at the middle level.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger situations, e.g. 'Use when joining a squad, recording a decision that affects teammates, or needing another agent's input'.

Reframe sub-areas as concrete actions rather than topics, e.g. 'record decisions to the squad inbox, locate your team root, request help via the coordinator'.

Replace the technical 'worktree awareness' label with user-facing terms like 'find your team root' or 'locate shared squad paths'.

DimensionReasoningScore

Specificity

Names the domain ('Standard collaboration patterns for all squad agents') and three sub-areas ('worktree awareness, decisions, cross-agent communication'), but these are topic labels rather than concrete executable actions, so it falls short of the multiple-specific-actions anchor at level 3.

2 / 3

Completeness

It clearly states what the skill covers, but there is no 'when should Claude use it' trigger clause; per the rubric a missing trigger clause caps completeness at 2.

2 / 3

Trigger Term Quality

'collaboration patterns' and 'cross-agent communication' are somewhat natural, but 'worktree awareness' is technical jargon and there is no explicit trigger phrasing or coverage of common variations, placing it at the some-relevant-keywords anchor.

2 / 3

Distinctiveness Conflict Risk

The 'all squad agents' / team-workflow framing gives it a niche, but the generic collaboration/decisions/communication language could overlap with other team-process skills, matching the somewhat-specific-but-could-overlap anchor.

2 / 3

Total

8

/

12

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.

Validation15 / 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
bradygaster/squad
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.