squad-conventions
Core conventions and patterns used in the Squad codebase
61
43%
Does it follow best practices?
Impact
93%
1.27xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.squad/skills/squad-conventions/SKILL.mdEvaluation results
85%
25%Squad CLI: Add a Project Health Check Command
Error handling and color output conventions
fatal() for errors
0%
0%
No raw stack traces
100%
100%
Color constants used
100%
100%
No inline ANSI codes
100%
100%
No npm dependencies added
100%
100%
Uses node:test for tests
0%
100%
Uses node:assert/strict
0%
100%
Test file in test/ directory
100%
100%
100%
34%Squad CLI: Implement the Init Command
Init idempotency and file structure
Correct directory layout
25%
100%
User-owned vs Squad-owned distinction
60%
100%
Skip-if-exists for user files
100%
100%
Already-exists message
70%
100%
path.join() for all paths
100%
100%
copyRecursive pattern
16%
100%
No npm dependencies
100%
100%
Idempotency test coverage
100%
100%
Tests use node:test
0%
100%
96%
3%Squad CLI: Add Upgrade Command and Tests
Zero-dependency constraint and built-in test runner
Uses node:test
100%
100%
Uses node:assert/strict
100%
100%
Correct test command
75%
83%
Test files in test/ directory
100%
100%
No added npm dependencies
100%
100%
Upgrade overwrites Squad-owned files
66%
100%
Upgrade preserves user-owned files
100%
100%
path.join() used throughout
100%
100%
copyRecursive used for upgrade
100%
71%
- Repository
- FritzAndFriends/BlazorWebFormsComponents
- Commit
9bf8669
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
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.