Conciseness

The body is lean and assumes Claude's competence: each pattern is a terse When/Pattern/Example triple with concrete parameters ("start at 2s, double each attempt", "Maximum 3 retries") and no explanation of concepts Claude already knows. Only the intro paragraph duplicating the frontmatter description is arguably trimmable, which keeps it at level 5 rather than revealing the padding characteristic of level 4.

Actionability

Guidance is mostly executable: numbered steps, concrete parameters (2s/4s/8s backoff, 3-cycle caps), a worked 429 example, and a failure-type selection table. A few steps remain abstract — "identify alternative tool/method" and "Determine if the failed step is critical" give no heuristics for the judgment — which are minor gaps keeping it below fully copy-paste-ready level 5.

Workflow Clarity

Each pattern is a clearly sequenced numbered workflow with explicit feedback loops ("Re-run to verify the fix", "Maximum 3 fix-retry cycles before escalating") and a selection-guide table acting as a checklist. Verification checkpoints appear only within pattern 3 rather than across all workflows, so it sits at level 4 (most checkpoints present) instead of 5.

Progressive Disclosure

This is a single-file skill with no bundle directories, and nothing that belongs in a separate file is inlined: five well-organized pattern sections plus an application section and selection table, all easy to navigate. Per the simple-skill guidance, well-organized sections with no need for external references warrant level 5.

Specificity

"Standard recovery patterns for all squad agents" names the domain but lists no concrete actions; "adapt — don't just report the failure" is an exhortation rather than a capability. This matches the anchor for naming the domain with minimal/generic actions, and falls short of level 3 because no concrete actions (e.g., retry with backoff, fallback alternatives) are stated.

Completeness

The "what" is clear (standard recovery patterns for squad agents), but "When something fails, adapt" reads as behavioral instruction to the agent rather than an explicit "Use when..." invocation trigger, so the when-clause is only weakly serving as trigger guidance. Per the guideline capping completeness at 3 for missing or weak explicit trigger guidance, this sits at level 3 rather than 4.

Trigger Term Quality

Terms like "recovery", "fails", and "failure" are relevant, but common natural variations users would say — "retry", "error handling", "fallback", "backoff" — are absent. Some relevant keywords exist, but coverage of synonyms and variations is missing, matching the middle anchor.

Distinctiveness Conflict Risk

"for all squad agents" scopes the skill to a specific niche, but "When something fails" is generic and would overlap with any error-handling or troubleshooting skill. It is somewhat specific yet still carries real overlap risk with similar skills, matching the middle anchor rather than the mostly-distinct level 4.