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

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

65%

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

The body is highly actionable, packed with concrete TypeScript templates across many backend concerns, but it is an oversized monolithic catalog of largely well-known patterns with no progressive disclosure into reference files and no real workflow sequencing or validation checkpoints. Trimming known material and splitting it into referenced files would materially improve it.

Suggestions

Trim or condense well-known patterns (repository, N+1, caching, JWT, RBAC, rate limiting) to only the non-obvious or project-specific guidance, reducing token cost on concepts Claude already knows.

Split the catalog into one-level-deep reference files (e.g. API.md, database.md, auth.md, caching.md) referenced from a concise overview in SKILL.md, so the main file stays lean.

Add explicit validation/verification checkpoints for destructive or batch operations (e.g. validate after transaction RPCs, confirm job completion in the queue) to raise workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is a ~585-line catalog of standard patterns Claude largely already knows (repository, service layer, N+1, caching, JWT, RBAC, rate limiting, structured logging); it is mostly code rather than prose fluff, so above a 1, but the token spend on well-known material could be trimmed significantly.	2 / 3
Actionability	Provides concrete, mostly-complete TypeScript templates (e.g. the CachedMarketRepository, fetchWithRetry, RateLimiter, requirePermission) that go well beyond pseudocode and are near copy-paste ready, matching the 'fully executable code' anchor despite a few clearly-marked stubs.	3 / 3
Workflow Clarity	This is a pattern catalog with no multi-step sequence or validation checkpoints, and batch/destructive operations (transactions, background jobs) lack feedback loops, which caps workflow clarity at 2 per the scoring notes; the boilerplate 'When to Use'/'Limitations' sections add little sequence guidance.	2 / 3
Progressive Disclosure	All content lives inline in a single ~585-line SKILL.md with no references or bundle files, fitting the 'content that should be separate is inline' anchor; headers are well-organized so above a 1, but it is far over the 50-line threshold that would let organized sections alone score a 3.	2 / 3
	Total	9 / 12 Passed

Description

50%

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 is specific and names relevant frameworks and domains, but it omits an explicit 'Use when...' trigger clause and relies on topic nouns rather than concrete actions, leaving it solid but not exemplary. It is clearly backend-focused but could still overlap with broader server-side coding skills.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when building or reviewing Node.js/Express/Next.js API routes, designing REST endpoints, or optimizing database queries.'

Lead with concrete verbs/actions (design, optimize, structure, refactor) rather than only naming domains, to raise specificity.

Include natural user phrasings/variations (e.g. 'API routes', 'REST endpoints', 'query performance', 'Supabase/Postgres') to improve trigger-term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	Names concrete domains ('API design, database optimization, server-side best practices for Node.js, Express, and Next.js API routes') but lists topics rather than concrete actions like 'extract/fill/merge', matching the 'names domain and some actions' anchor; not a 3 because no specific verbs/actions are enumerated.	2 / 3
Completeness	Clearly states what the skill covers but provides no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	Includes natural terms a user would say ('Node.js', 'Express', 'Next.js API routes', 'API design', 'database optimization'), but coverage lacks common variations and there is no trigger phrasing; not a 3 because it does not show broad natural-term coverage like the 'PDFs, forms, .pdf' example.	2 / 3
Distinctiveness Conflict Risk	The framework-specific scope ('Node.js, Express, and Next.js API routes') gives it a niche, but 'server-side best practices' is broad enough to overlap with general web-dev skills; not a 3 because the niche is not sharply distinct from related coding skills.	2 / 3
	Total	8 / 12 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/cc-skill-backend-patterns/SKILL.md
Commit: a3068b7

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