backend-patterns

Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.

Quality

45%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./docs/v19.7/configuration/agent/skills_external/antigravity-awesome-skills-main/skills/cc-skill-backend-patterns/SKILL.md

Quality

Content

57%

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

This skill provides excellent, actionable code examples for backend patterns but suffers from being a monolithic reference document rather than a well-structured skill. The content is too comprehensive for a single file and lacks workflow guidance for when/how to apply these patterns. It reads more like a pattern catalog than actionable skill instructions.

Suggestions

Split content into separate files (e.g., CACHING.md, AUTH.md, ERROR-HANDLING.md) and make this file a concise overview with links to each topic

Add a decision tree or guidance section explaining when to use each pattern (e.g., 'Use repository pattern when: multiple data sources, need for testing, complex queries')

Remove patterns Claude already knows well (basic repository, simple middleware) or condense them to one-liners with links to detailed examples

Add a workflow section showing how to implement these patterns incrementally in an existing codebase with validation steps

Dimension	Reasoning	Score
Conciseness	The content is comprehensive but includes some patterns Claude already knows well (basic repository pattern, simple rate limiting). Some sections like the JobQueue could be trimmed, and the extensive code examples for common patterns add bulk without proportional value.	2 / 3
Actionability	Excellent executable TypeScript code throughout with complete, copy-paste ready examples. Each pattern includes concrete implementations with proper typing, error handling, and usage examples.	3 / 3
Workflow Clarity	Patterns are presented as isolated examples without clear guidance on when to use each or how they connect. No validation checkpoints for implementing these patterns, and no sequence for adopting them in a project.	2 / 3
Progressive Disclosure	This is a monolithic 400+ line file covering 10+ distinct topics with no references to external files. Content should be split into separate files (caching.md, auth.md, error-handling.md) with this file serving as an overview with links.	1 / 3
	Total	8 / 12 Passed

Description

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 clear technical domain and specific technologies but relies heavily on abstract concepts ('patterns', 'best practices') rather than concrete actions. The complete absence of a 'Use when...' clause significantly weakens its utility for skill selection, and the trigger terms could be expanded to capture more natural user language.

Suggestions

Add an explicit 'Use when...' clause with trigger scenarios like 'Use when building REST APIs, designing backend services, optimizing database queries, or working with Express/Next.js server code'

Replace abstract terms with concrete actions: instead of 'backend architecture patterns', specify 'design REST endpoints, structure Express middleware, configure API routes'

Expand trigger terms to include common variations: 'REST', 'endpoints', 'server-side', 'middleware', 'SQL queries', 'MongoDB', 'authentication'

Dimension	Reasoning	Score
Specificity	Names the domain (backend/API/database) and mentions specific technologies (Node.js, Express, Next.js), but uses abstract terms like 'patterns', 'best practices', and 'optimization' rather than concrete actions like 'design REST endpoints' or 'write database queries'.	2 / 3
Completeness	Describes what the skill covers (backend patterns, API design, etc.) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes some relevant keywords users might say ('API design', 'Node.js', 'Express', 'Next.js', 'database'), but missing common variations like 'REST', 'endpoints', 'server', 'backend code', 'SQL', 'MongoDB', or 'routes'.	2 / 3
Distinctiveness Conflict Risk	The technology stack (Node.js, Express, Next.js API routes) provides some distinction, but 'backend architecture' and 'database optimization' are broad enough to potentially overlap with general coding skills or database-specific skills.	2 / 3
	Total	7 / 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 (584 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: duclm1x1/Dive-Ai
Commit: 20ba150

Reviewed: 4 months 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.