CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-conduct

Shared hard rules enforced across all squad agents

49

Quality

53%

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 ./packages/squad-cli/templates/skills/agent-conduct/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 body is a tight, well-structured instruction skill: concrete rules with actionable examples and a validation-aware sequence. Its only real weakness is mild redundancy between the Patterns and Anti-Patterns sections.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (e.g. 'Use generic/parameterized values', 'update your history.md'), but the Anti-Patterns section largely restates the Patterns, a minor instance of over-explanation that could be trimmed.

4 / 5

Actionability

Concrete, executable guidance dominates — 'use obviously-fake test fixtures (e.g., "test-agent-1", "TestBot")' and 'Run the test suite for files you touched' — with only minor generality in phrases like 'verify your changes don't break existing tests'.

4 / 5

Workflow Clarity

The Peer Quality Check gives a clear before-finish sequence with a validation checkpoint ('Run the test suite for files you touched. If CI has been failing, check...'), leaving only minor gaps in explicit error-recovery feedback.

4 / 5

Progressive Disclosure

At under 50 lines with no bundle files and no need for external references, the well-organized Context / Patterns / Anti-Patterns sections satisfy the simple-skill exception for a top score.

5 / 5

Total

17

/

20

Passed

Description

28%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 names its domain but stays at a high abstraction level, giving Claude little sense of what the rules are or when to invoke the skill. It lacks any explicit trigger guidance, which is the main weakness.

Suggestions

Add a 'Use when...' clause naming concrete triggers, e.g. 'Use when writing tests, CI configs, or product code that might reference squad agent names, or before declaring work complete.'

Replace 'Shared hard rules enforced' with the two concrete behaviors (product-name isolation and pre-finish test verification) so the 'what' is specific.

Include natural user-facing terms like 'agent names in tests', 'CI failures', and 'test verification' to improve trigger-term quality.

DimensionReasoningScore

Specificity

Quotes 'Shared hard rules enforced across all squad agents' — names the domain (squad agents) but the only action ('enforced') is generic, matching the score-2 anchor 'Processes PDF files'.

2 / 5

Completeness

Offers only a vague 'what' (rules are 'enforced') with no 'Use when...' trigger guidance, matching the score-2 anchor for a vague what and absent when; the missing-trigger cap of 3 does not raise it above this floor.

2 / 5

Trigger Term Quality

Phrases 'hard rules' and 'squad agents' are mildly relevant but no natural trigger a user would actually say when needing this skill, fitting the one-or-two-generic-keywords anchor.

2 / 5

Distinctiveness Conflict Risk

'across all squad agents' carves a fairly specific niche but 'shared hard rules' is broad governance language that could overlap with other conduct/governance skills, matching the somewhat-specific anchor.

3 / 5

Total

9

/

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.