e2e-template-testing

End-to-end validation of coordinator and agent template changes

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.squad-templates/skills/e2e-template-testing/SKILL.md

Quality

Content

77%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 highly actionable, well-sequenced E2E workflow with strong validation checkpoints and feedback loops. Its main weaknesses are redundancy in the progress-comment templates and a monolithic structure that could split detail into reference files.

Suggestions

Consolidate the three renderings of the progress-comment table into one canonical template referenced from both Step 0 and Progress Reporting to remove the duplication.

Move the large progress-comment PowerShell templates and/or the test matrix into reference files under references/ and link to them, improving progressive disclosure for this 550-line skill.

Trim explanatory asides that restate what a flag does where the command is already self-explanatory, to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	Most content earns its place, but the progress-comment table is rendered ~3 times (Step 0 PowerShell, the Progress Reporting bash block, and the update PowerShell block) with overlapping explanations that could be consolidated.	3 / 5
Actionability	Copy-paste ready bash and PowerShell commands cover build, link, init, sessions, verification, and comment posting, with specific flags and concrete examples for the common cases.	5 / 5
Workflow Clarity	A clear Step 0-6 sequence is paired with explicit fast-fail validation checkpoints, retry feedback loops (e.g. reinstall then retry), connection-drop recovery, and a verdict checklist for the complex process.	5 / 5
Progressive Disclosure	Sections are well-organized with clear headers, but the ~550-line skill is a single monolithic SKILL.md with no bundle files and no file-level splitting of content (progress templates, test matrix, fast-fail scripts) that would benefit from separate references.	3 / 5
	Total	16 / 20 Passed

Description

53%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 names a specific niche, but it only conveys the "what" with a single generic action verb and omits any "when to use" trigger guidance. It is functional yet leaves the activation conditions implicit.

Suggestions

Add an explicit trigger clause, e.g. "Use when you change .squad-templates/ coordinator prompts, agent charters, or helper scripts and need to verify the change end-to-end."

List 1-2 more concrete actions (e.g. "build the CLI from your branch, run real squad sessions, and verify outcomes") to raise specificity beyond the single generic verb "validation".

Include natural trigger terms and synonyms users would say (e.g. "template changes", "coordinator prompt", "agent charter", "squad init") to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain clearly ("coordinator and agent template changes") and one action ("end-to-end validation"), but the single verb is generic rather than listing concrete actions like building the CLI or running sessions.	3 / 5
Completeness	It clearly states what the skill does (end-to-end validation of template changes) but has no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Relevant keywords (validation, coordinator, agent, template) are present but are project-internal jargon with no common synonyms, variations, or file extensions a user would naturally say.	3 / 5
Distinctiveness Conflict Risk	It carves a clear niche (coordinator/agent template validation) with minimal conflict risk, though "validation of template changes" could mildly overlap with general testing skills.	4 / 5
	Total	13 / 20 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (558 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 missing, 1 suspicious	Warning

	Total	13 / 16 Passed

Repository: bradygaster/squad
Path: .squad-templates/skills/e2e-template-testing/SKILL.md
Commit: c41b316

Reviewed: ~13 hours ago

Table of Contents

Discovery Implementation Validation

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.