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.

Install with Tessl CLI

npx tessl i github:sickn33/antigravity-awesome-skills --skill cc-skill-backend-patterns

What are skills?

1.42x

Review — 45%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Evaluation — 100%

↑ 1.42x

Agent success when using this skill

Validation — 9 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

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 clear technical domain and specific frameworks 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, while relevant, lack the natural language variations users would actually say.

Suggestions

Add an explicit 'Use when...' clause with trigger scenarios like 'Use when building REST APIs, designing database schemas, optimizing server performance, or working with Express middleware'

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

Include natural language variations users might say: 'backend', 'server-side', 'API endpoints', 'REST', 'database queries', 'Express routes'

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 listing 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. Per rubric guidelines, missing explicit trigger guidance caps this at 2, and the 'what' is also somewhat vague.	1 / 3
Trigger Term Quality	Includes relevant technical keywords (Node.js, Express, Next.js, API, database) that users might mention, but missing common variations like 'REST', 'endpoints', 'server', 'routes', 'SQL', 'MongoDB', or action-oriented terms like 'build API' or 'optimize queries'.	2 / 3
Distinctiveness Conflict Risk	The combination of backend + specific frameworks (Node.js, Express, Next.js) provides some distinctiveness, but 'API design' and 'database optimization' are broad enough to potentially overlap with general coding skills, database-specific skills, or other web development skills.	2 / 3
	Total	7 / 12 Passed

Implementation

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 covering a wide range of backend patterns with proper TypeScript typing. However, it's overly long for a single SKILL.md file, mixing quick-reference patterns with detailed implementations that should be in separate files. The lack of workflow guidance on pattern selection and integration limits its effectiveness for complex scenarios.

Suggestions

Split into overview SKILL.md with links to separate files: CACHING.md, AUTH.md, ERROR_HANDLING.md, DATABASE.md

Add a decision tree or table at the top: 'Use Repository Pattern when X, Service Layer when Y'

Include validation checkpoints for database transactions: 'Verify rollback behavior in dev before production'

Remove basic implementations Claude knows (simple Logger, basic queue) and focus on project-specific patterns or link to external docs

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but includes some patterns Claude already knows well (basic repository pattern, simple rate limiting). Some sections like the Logger class and basic queue implementation could be trimmed as they're standard patterns.	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 combine them or validation checkpoints. Missing workflow for integrating patterns (e.g., 'implement auth before rate limiting') and no verification steps for database transactions or cache invalidation.	2 / 3
Progressive Disclosure	This is a monolithic 400+ line file with no references to external documentation. Content like the full SQL function, complete Logger implementation, and JobQueue could be split into separate reference files with links from a concise overview.	1 / 3
	Total	8 / 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

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