The description uses vague, abstract language ('conventions and patterns') without listing any concrete actions. It does not describe what the skill actually does—no specific capabilities are mentioned.

The description weakly addresses 'what' (conventions and patterns) and completely omits 'when' — there is no 'Use when...' clause or any explicit trigger guidance.

The only potentially useful keyword is 'Squad codebase,' which is project-specific but not a natural trigger term a user would say. 'Conventions and patterns' are overly generic and not actionable trigger terms.

The mention of 'Squad codebase' provides some specificity to a particular project, which reduces conflict with generic coding skills. However, 'conventions and patterns' is broad enough to overlap with any coding style or standards skill.

Every section earns its place — no explanations of what Node.js built-ins are or how path.join works. The content is dense with project-specific conventions Claude wouldn't know, and avoids padding.

Provides executable code examples for the fatal() pattern, path construction, and skip-if-exists pattern. The anti-patterns section gives concrete do/don't guidance. Commands like `npm test` and `node --test test/` are copy-paste ready.

This is a conventions/patterns skill rather than a multi-step workflow, so explicit sequencing is less critical. However, the init vs upgrade flow could benefit from a clearer decision tree — the distinction between user-owned and Squad-owned files during init vs upgrade is mentioned but not sequenced with validation checkpoints.

The content is well-organized with clear sections (Patterns, Examples, Anti-Patterns), but everything is inline in a single file. The file structure section hints at related files (templates/, .squad/) but doesn't link to any deeper documentation. For a conventions skill this is acceptable but could benefit from linking to e.g., a testing guide or upgrade flow details.