CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-conduct

Shared hard rules enforced across all squad agents

50

Quality

55%

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-conduct/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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 lean, well-organized instruction-only skill with concrete directives, examples, and a clear validation-backed workflow for the Peer Quality Check. The only weakness is minor unnecessary historical context in the opening paragraph.

DimensionReasoningScore

Conciseness

The rules are stated efficiently with concrete examples, but the Context paragraph's history ("previously duplicated in every charter... now they live here as a shared skill, loaded once") is unnecessary rationale that could be trimmed.

2 / 3

Actionability

Directives are concrete and specific for an instruction-only skill, with executable examples such as fake fixtures "test-agent-1"/"TestBot", named agents Flight/EECOM/FIDO, and a concrete file reference history.md.

3 / 3

Workflow Clarity

The Peer Quality Check is a clearly ordered sequence with an explicit validation step ("Run the test suite for files you touched") and feedback loops (check CI contribution; update history.md on mistakes).

3 / 3

Progressive Disclosure

Under 50 lines with no need for external references and no bundle files, the body is well-organized into Context, Patterns (with sub-sections), and Anti-Patterns sections, satisfying the simple-skill allowance.

3 / 3

Total

11

/

12

Passed

Description

25%

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 identifies a domain (squad governance) in third person but is vague about concrete capabilities, lacks natural trigger terms, and omits any "when to use" guidance. It is distinctiveness-neutral rather than distinctive.

Suggestions

Add concrete actions the skill performs, e.g. "Enforces product-isolation and test-verification rules across squad agent charters".

Include a natural "Use when..." trigger clause naming terms users would say, e.g. "Use when writing tests, CI configs, or agent charters that reference squad member names."

Replace internal jargon ("hard rules", "squad agents") with user-facing trigger terms like "team governance", "agent naming rules", or "test isolation".

DimensionReasoningScore

Specificity

The description "Shared hard rules enforced across all squad agents" is an abstract noun phrase that names a domain but no concrete actions or capabilities, matching the vague anchor rather than the action-listing anchor 2.

1 / 3

Completeness

It states a weak "what" (rules for squad agents) but provides no "Use when..." trigger guidance, so completeness is capped at 2 per the rubric guideline.

2 / 3

Trigger Term Quality

"squad agents" and "hard rules enforced" are internal jargon rather than natural terms a user would say when they need this skill; there are no common trigger keywords.

1 / 3

Distinctiveness Conflict Risk

It is somewhat specific to the squad-governance niche, but "hard rules" is generic and could overlap with other team/governance skills, so it is not a clearly conflict-free niche.

2 / 3

Total

6

/

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.