cc-skill-backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
34
31%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/cc-skill-backend-patterns/SKILL.mdQuality
Discovery
32%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 identifies a reasonable domain and names specific technologies, which helps with targeting. However, it lacks concrete actions (listing categories rather than specific capabilities), misses a 'Use when...' clause entirely, and uses somewhat broad terminology that could overlap with other backend or full-stack skills.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about designing REST APIs, optimizing database queries, structuring Express middleware, or building Next.js API routes.'
Replace high-level categories with specific concrete actions, e.g., 'Designs RESTful and GraphQL APIs, optimizes SQL/NoSQL queries, structures Express middleware pipelines, and implements authentication patterns.'
Include more natural trigger terms users would say, such as 'REST', 'GraphQL', 'SQL', 'MongoDB', 'middleware', 'endpoints', 'server performance', '.js backend'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (backend development) and some areas like 'API design', 'database optimization', and 'server-side best practices', but these are still fairly high-level categories rather than concrete actions. It doesn't list specific actions like 'design RESTful endpoints', 'write database queries', or 'configure middleware'. | 2 / 3 |
Completeness | Describes 'what' at a high level (backend architecture, API design, etc.) but completely lacks any 'when' clause or explicit trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'what' is also somewhat vague, this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords users might say like 'API design', 'database optimization', 'Node.js', 'Express', and 'Next.js API routes'. However, it misses common variations like 'REST', 'GraphQL', 'SQL', 'MongoDB', 'middleware', 'authentication', 'endpoints', or 'server' that users would naturally use. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of specific technologies (Node.js, Express, Next.js API routes) helps narrow the scope, but 'backend architecture patterns' and 'server-side best practices' are broad enough to overlap with general coding skills, DevOps skills, or framework-specific skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
29%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a backend patterns reference manual that dumps extensive, well-known patterns (REST, repository, caching, auth, rate limiting, queues, logging) into a single monolithic file. While the code examples are high-quality and executable, the content is far too verbose for a skill file—Claude already knows these standard patterns. There is no workflow sequencing, no validation steps, and no progressive disclosure structure.
Suggestions
Drastically reduce content to only project-specific conventions and patterns Claude wouldn't already know (e.g., specific Supabase RPC conventions, project-specific error codes, or custom middleware chains unique to this codebase).
Add a clear workflow section that sequences when and how to apply these patterns (e.g., 'When adding a new API endpoint: 1. Create route file, 2. Add validation schema, 3. Implement service method, 4. Test with curl command, 5. Verify error handling').
Split detailed pattern implementations into separate reference files (e.g., CACHING.md, AUTH.md, ERROR-HANDLING.md) and keep SKILL.md as a concise overview with links.
Remove generic patterns like basic REST URL conventions, standard JWT validation, and textbook repository pattern implementations that Claude already knows thoroughly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines covering many patterns Claude already knows well (REST conventions, repository pattern, middleware, caching, RBAC, rate limiting, queues, logging). Most of this is textbook backend knowledge that doesn't need to be spelled out with full implementations. The content reads like a tutorial rather than a skill that adds novel, project-specific guidance. | 1 / 3 |
Actionability | The code examples are concrete, executable TypeScript with realistic implementations. Patterns include complete, copy-paste-ready code for repositories, middleware, caching, error handling, rate limiting, and more, with clear good/bad comparisons. | 3 / 3 |
Workflow Clarity | There is no sequenced workflow or multi-step process described. The content is a catalog of isolated patterns with no guidance on when to apply them in sequence, no validation checkpoints, and no decision framework for choosing between patterns. The closing line 'Choose patterns that fit your complexity level' is vague. | 1 / 3 |
Progressive Disclosure | The entire content is a monolithic wall of code examples with no references to external files, no layered structure, and no separation of overview from detailed content. All patterns are inlined at the same level of detail with no navigation aids or cross-references. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (594 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
8854d4e
- 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.