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.

Quality

31%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

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 (verbs describing what the skill does), has no 'Use when...' clause to guide skill selection, and uses category-level terms rather than specific capabilities. The description reads more like a topic list than an actionable skill selector.

Suggestions

Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user asks about building REST APIs, optimizing database queries, structuring Express middleware, or setting up Next.js API routes.'

Replace abstract category names with concrete actions, e.g., 'Designs RESTful and GraphQL APIs, optimizes database queries and indexing, structures Express middleware pipelines, and implements authentication flows.'

Include additional natural trigger terms users might say, such as 'REST', 'GraphQL', 'middleware', 'SQL queries', 'MongoDB', 'server performance', or 'endpoint design'.

Dimension	Reasoning	Score
Specificity	Names the domain (backend development) and lists several 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 specify what actions are performed (e.g., 'designs RESTful endpoints', 'optimizes SQL queries').	2 / 3
Completeness	Describes 'what' at a high level 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', 'Node.js', 'Express', 'Next.js API routes', and 'database optimization'. However, it misses common variations like 'REST', 'GraphQL', 'middleware', 'SQL', 'MongoDB', 'backend performance', or 'server setup'.	2 / 3
Distinctiveness Conflict Risk	The mention of specific technologies (Node.js, Express, Next.js API routes) helps narrow the scope, but terms like 'backend architecture patterns' and 'best practices' are broad enough to overlap with general coding, architecture, or full-stack 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 reads as a generic backend development reference/textbook rather than a targeted skill file. It dumps extensive code examples for well-known patterns (repository, middleware, caching, auth, rate limiting, queues, logging) that Claude already understands, without providing any project-specific context, workflow sequencing, or decision guidance. The code quality is high and executable, but the sheer volume of generic content makes it a poor use of context window.

Suggestions

Reduce content to project-specific patterns, conventions, or deviations from standard practices — remove generic backend knowledge Claude already has (e.g., what REST is, how JWT works, basic caching patterns).

Add a workflow section that sequences when and how to apply these patterns (e.g., 'When adding a new API endpoint: 1. Define route → 2. Add validation → 3. Implement service layer → 4. Add error handling → 5. Test').

Split into a concise SKILL.md overview with links to separate reference files (e.g., AUTH.md, CACHING.md, ERROR_HANDLING.md) for detailed code examples.

Add project-specific context: which database is used, what the actual API structure looks like, naming conventions, and any non-obvious architectural decisions unique to this codebase.

Dimension	Reasoning	Score
Conciseness	This is extremely verbose at ~400+ lines, essentially a textbook chapter on backend patterns. It explains concepts Claude already knows well (repository pattern, middleware, JWT auth, rate limiting, caching, queues, logging). Nearly every section covers fundamental backend knowledge that adds no novel or project-specific value. The 'Remember' footer and boilerplate limitations section add further bloat.	1 / 3
Actionability	The code examples are concrete, executable TypeScript with complete implementations. Each pattern includes copy-paste ready code with clear usage examples, proper imports, and realistic implementations rather than pseudocode.	3 / 3
Workflow Clarity	There is no workflow or sequencing whatsoever — this is a catalog of isolated patterns with no guidance on when to apply them, in what order, or how they compose together. There are no validation checkpoints, no decision trees for pattern selection, 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. Sections like caching, auth, rate limiting, and queues could each be separate reference files, with the SKILL.md serving as a concise overview with navigation links.	1 / 3
	Total	6 / 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 (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: 1930a07

Reviewed: about 2 hours 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.