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.

1.42x

Quality

23%

Does it follow best practices?

Impact

100%

1.42x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/cc-skill-backend-patterns/SKILL.md

Quality

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 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', and 'authentication'.

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

14%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill reads like a generic backend patterns cheat sheet that teaches Claude things it already knows thoroughly. It's excessively long, lacks project-specific context, has no workflow sequencing or validation steps, and dumps everything into a single monolithic file. The code examples, while mostly concrete, are standard textbook patterns that don't justify the token cost.

Suggestions

Remove generic patterns Claude already knows (repository pattern, middleware, JWT auth, rate limiting, etc.) and focus only on project-specific conventions, configurations, or non-obvious decisions unique to your 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').

Split into an overview SKILL.md with brief descriptions and links to separate files (e.g., CACHING.md, AUTH.md, ERROR_HANDLING.md) for detailed patterns.

Include project-specific details like actual file paths, naming conventions, existing middleware chain, and database schema references rather than generic examples with placeholder names.

Dimension	Reasoning	Score
Conciseness	This is extremely verbose at ~400+ lines, covering many patterns Claude already knows well (repository pattern, middleware, JWT auth, rate limiting, job queues, structured logging). Almost none of this is project-specific or novel — it's a textbook rehash of common backend patterns that adds no unique value beyond what Claude can generate from its training data.	1 / 3
Actionability	The code examples are mostly concrete and executable TypeScript, which is good. However, many are incomplete (e.g., '// Other methods...', '// Job execution logic', '// Continue with request') and some mix pseudocode with real code (the SQL function uses '$' instead of '$$'). The examples are generic rather than tailored to a specific project context.	2 / 3
Workflow Clarity	There is no workflow or sequencing — it's a catalog of isolated patterns with no guidance on when to apply them, in what order, or how they connect. There are no validation checkpoints, no decision trees for choosing between patterns, and no feedback loops for error recovery during implementation.	1 / 3
Progressive Disclosure	This is a monolithic wall of code examples with no references to external files and no layered structure. All content is inline regardless of complexity. For a skill this broad, it should be an overview pointing to separate files for each pattern category (e.g., AUTH.md, CACHING.md, ERROR_HANDLING.md).	1 / 3
	Total	5 / 12 Passed

Validation

81%

Warnings & errors only

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 (589 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: e18e63c

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.