agent-patterns
Execute this skill should be used when the user asks about "SPAWN REQUEST format", "agent reports", "agent coordination", "parallel agents", "report format", "agent communication", or needs to understand how agents coordinate within the sprint system. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
Overall
score
37%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill agent-patternsActivation
22%This description suffers from severe vagueness and contains meaningless filler phrases like 'Use when appropriate context detected' and 'Trigger with relevant phrases based on skill purpose.' It fails to explain what concrete actions the skill performs, only listing trigger terms without describing actual capabilities. The description reads more like a template than a functional skill description.
Suggestions
Replace vague phrases with concrete actions (e.g., 'Generates SPAWN REQUEST formatted messages for launching parallel agents, parses agent completion reports, coordinates multi-agent task distribution').
Remove meaningless filler like 'Use when appropriate context detected' and 'Trigger with relevant phrases based on skill purpose' - these provide zero value for skill selection.
Add a proper 'Use when...' clause with specific scenarios (e.g., 'Use when the user needs to spawn parallel agents, parse agent reports, or coordinate multi-agent workflows within the sprint system').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only vague phrases like 'Execute this skill' and 'understand how agents coordinate'. It fails to describe what the skill actually does. | 1 / 3 |
Completeness | The 'what' is essentially missing - it only says to 'understand how agents coordinate' without explaining what capabilities the skill provides. The 'when' is present but generic ('Use when appropriate context detected' is useless). | 1 / 3 |
Trigger Term Quality | Lists some relevant keywords like 'SPAWN REQUEST format', 'agent reports', 'agent coordination', 'parallel agents', but the final sentence 'Trigger with relevant phrases based on skill purpose' is meaningless filler that adds no value. | 2 / 3 |
Distinctiveness Conflict Risk | The specific terms like 'SPAWN REQUEST format' and 'sprint system' provide some distinctiveness, but the vague language about 'agent coordination' could overlap with other agent-related skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
22%This skill content is a generic template with no actual substance related to its stated purpose (agent coordination, spawn requests, report formats). The description promises guidance on 'SPAWN REQUEST format', 'agent reports', and 'agent coordination', but the body contains only placeholder text that could apply to any skill. It fails to provide any actionable information about the specific domain it claims to cover.
Suggestions
Add concrete examples of SPAWN REQUEST format with actual syntax and required fields
Include executable code or specific commands for agent coordination and communication patterns
Define the actual report format structure with field names, types, and example values
Replace generic instructions with specific workflow steps for spawning agents and handling their reports
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is brief but entirely generic - it doesn't waste tokens on explanations Claude knows, but the tokens it does use provide no skill-specific value. It's a template with placeholder text rather than meaningful content. | 2 / 3 |
Actionability | The instructions are completely vague and abstract ('Invoke this skill when trigger conditions are met', 'Provide necessary context'). There are no concrete commands, code examples, or specific guidance for agent coordination, spawn requests, or report formats mentioned in the description. | 1 / 3 |
Workflow Clarity | The 4-step process is generic boilerplate with no actual workflow for agent coordination. Steps like 'Review the generated output' and 'Apply modifications as needed' provide no actionable sequence for the described agent patterns functionality. | 1 / 3 |
Progressive Disclosure | References to external files (errors.md, examples.md) are present and one-level deep, but the main content is so empty that the structure serves no purpose. The references use template variables ({baseDir}) suggesting incomplete implementation. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
88%Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 14 / 16 Passed | |
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.