CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-collaboration

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

59

Quality

68%

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

78%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 concise, well-structured, and actionable, with concrete paths, a fallback command, and explicit anti-patterns; the only real gap is the absence of a validation/checkpoint step in the decision-recording and reviewer-reject flows.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, providing concrete paths and a compact format template without restating known concepts; the brief Context paragraph on byte-count redundancy is the minor trimmable over-explanation keeping it just below 5.

4 / 5

Actionability

Gives concrete, executable guidance — the inbox path `.squad/decisions/inbox/{your-name}-{brief-slug}.md`, the fallback `git rev-parse --show-toplevel`, and a fill-in decision template — with only minor gaps from placeholder-based templates rather than fully copy-paste examples.

4 / 5

Workflow Clarity

Each pattern is clearly sequenced (e.g. decision recording: locate TEAM ROOT → write to inbox path → use the format) with explicit do/don't guardrails; not a 5 because no validation checkpoint is shown even for the write/reject flows.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no external bundle files and no need for references, and is cleanly organized into Context, Patterns, and Anti-Patterns sections, so the simple-skill exception awards a 5 for well-organized structure.

5 / 5

Total

17

/

20

Passed

Description

58%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 clearly states what the skill covers and is fairly distinct, but it lacks any explicit "Use when..." trigger guidance and relies on internal team jargon rather than natural user phrasing, which caps completeness and trigger-term quality.

Suggestions

Add a "Use when..." clause naming the situations that should trigger this skill, e.g. "Use when a squad agent needs to record a decision, locate its worktree root, or coordinate with another agent."

Replace some internal jargon ("squad agents", "worktree awareness") with more natural trigger phrasing a user might actually say, such as "agent team coordination" or "recording team decisions".

Tie the listed sub-areas to concrete actions ("record decisions to the inbox", "resolve the team root path", "request another agent's input") to lift specificity toward 5.

DimensionReasoningScore

Specificity

Names the collaboration domain for squad agents and enumerates several concrete sub-areas ("worktree awareness, decisions, cross-agent communication"); stops short of score 5 because it lists capability areas rather than a comprehensive set of specific actions.

4 / 5

Completeness

Has a clear "what" ("Standard collaboration patterns for all squad agents") but no "Use when..." clause or equivalent trigger guidance, so per the judging guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

Contains relevant keywords ("squad agents", "worktree awareness", "cross-agent communication") but these lean toward internal/system jargon rather than phrases a user would naturally say; common variations or synonyms are missing.

3 / 5

Distinctiveness Conflict Risk

The squad-agent/worktree/decisions framing carves a clear niche with low conflict risk, though it could marginally overlap with generic agent-collaboration skills, keeping it just below 5.

4 / 5

Total

14

/

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.

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.