CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-conduct

Shared hard rules enforced across all squad agents

48

Quality

51%

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 ./.squad-templates/skills/agent-conduct/SKILL.md

The canonical home for this skill is agent-conduct in bradygaster/squad

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: it gives concrete, actionable rules and anti-patterns without padding, and its short length makes it easy to navigate. The main gap is the absence of an explicit validate-fix-retry feedback loop in the Peer Quality Check workflow.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, e.g. 'Use obviously-fake test fixtures (e.g., "test-agent-1", "TestBot")' and 'Run the test suite for files you touched'; the only padding is the Context provenance line ('They were previously duplicated in every charter'), so it fits 'Efficient; minor instances of over-explanation that could be trimmed'; not a 5 due to that optional context.

4 / 5

Actionability

Concrete, executable guidance is given throughout — specific fixture values ('test-agent-1', 'TestBot'), a concrete action ('Run the test suite for files you touched'), and 'update your history.md'; this matches 'Mostly executable guidance; concrete code or commands with minor gaps'; not a 5 because no exact commands/fixture patterns are copy-paste ready and CI-check steps are underspecified.

4 / 5

Workflow Clarity

The Peer Quality Check is sequenced with an implicit validation checkpoint ('verify your changes don't break existing tests... If CI has been failing, check your changes'), matching 'Clear sequence with most checkpoints present; minor validation gaps'; not a 5 because there is no explicit fix-and-retry feedback loop or pass/fail gating before declaring work done.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no external references and is cleanly organized into Context, Patterns, and Anti-Patterns sections; per the simple-skill guidance this earns the top score, and navigation is unambiguous with no nested references.

5 / 5

Total

17

/

20

Passed

Description

25%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 concise and third-person but overly abstract: it states the domain without naming the concrete rules or giving any 'Use when' trigger guidance, leaving both what and when underspecified.

Suggestions

Name the concrete behaviors the skill enforces (e.g., 'Enforces product isolation from squad-specific agent names and a pre-finish test verification check').

Add an explicit 'Use when...' clause so Claude knows when to load this skill (e.g., 'Use when writing or modifying tests, CI workflows, or product code that could reference squad agent names').

Include natural user-facing trigger terms such as 'agent names in tests', 'CI failures', or 'test verification' to reduce overlap with generic governance skills.

DimensionReasoningScore

Specificity

The phrase 'Shared hard rules enforced across all squad agents' names the domain (squad-agent governance) but gives no concrete actions, matching the anchor 'Names the domain but actions are minimal or generic'; it is not a 1 because it does specify a real domain, and not a 3 because no specific actions are listed.

2 / 5

Completeness

It offers only a vague 'what' ('Shared hard rules enforced across all squad agents') and no 'when'/'Use when' guidance, matching the 'Has a vague what and no when' anchor; the missing explicit trigger clause also caps it, and it is not a 3 because the what itself is vague.

2 / 5

Trigger Term Quality

Terms like 'squad agents' and 'hard rules' are generic/internal jargon with no natural phrases a user would say when needing this skill, fitting the 'one or two generic keywords; missing the natural phrases users say' anchor; not a 1 because there is some domain vocabulary, not a 3 because common user-facing variations are absent.

2 / 5

Distinctiveness Conflict Risk

'Shared hard rules enforced across all squad agents' is very broad and would overlap with other governance/process skills, matching the 'Very broad; high overlap risk with many similar skills' anchor; not a 3 because it lacks specific distinguishing triggers.

2 / 5

Total

8

/

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.