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

61%

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

61%Weight 40%Scale 1-5

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

The SKILL.md body is a well-structured, lean overview that correctly offloads detail to a single clearly-signaled reference file. Its weaknesses are the absence of any inline executable guidance or validation workflow and a vague 'When to Use' stub.

Suggestions

Add at least one inline quick-start code snippet or concrete command so the body is actionable without forcing a full guide load.

Replace the generic 'When to Use' line with concrete triggers mirroring the description (e.g. 'Use when designing REST endpoints, preventing N+1 queries, or adding auth middleware').

If any pattern involves destructive or batch operations (e.g. the transaction or rate-limiting examples), surface an explicit validate-then-proceed checkpoint in the body.

Dimension	Reasoning	Score
Conciseness	The body is lean, delegates the bulk of material to the detailed guide, and avoids explaining concepts Claude already knows; the only padding is the vague 'When to Use' stub ('applicable to execute the workflow or actions described in the overview'), which keeps it just below a 5.	4 / 5
Actionability	The body itself contains no executable code or commands, only a pointer to the detailed guide; the guide does contain complete, executable TypeScript, but as written the SKILL.md body gives incomplete concrete guidance, matching the anchor for 3 rather than 4.	3 / 5
Workflow Clarity	There is no multi-step sequenced workflow with validation checkpoints in the body—it is a patterns reference that delegates to the guide—so checkpoints are absent; not a 2 because the delegation instruction is clear, but not a 4 without explicit validation steps.	3 / 5
Progressive Disclosure	Content is appropriately split into a one-level-deep, clearly signaled reference (references/detailed-guide.md) that exists in the bundle, with a concise overview; the weak 'When to Use' section is a minor organization gap that prevents a 5.	4 / 5
	Total	14 / 20 Passed

Description

61%Weight 40%Scale 1-5

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 concise, third-person, and names a coherent backend niche with strong framework-based trigger terms. Its main weakness is the absence of any explicit 'when to use' guidance, which caps completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when designing or debugging Node.js/Express/Next.js APIs, optimizing database queries, or structuring server-side code.'

Replace abstract categories ('server-side best practices') with one or two concrete actions to lift specificity toward 4.

Include common synonyms/file cues users might say (e.g. 'REST endpoints', 'Supabase/Prisma queries') to broaden trigger term coverage.

Dimension	Reasoning	Score
Specificity	The description names the backend domain plus several sub-areas ('API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes'), but these are topic categories rather than the concrete executable actions (e.g. 'extract text', 'fill forms') that anchor a 4; not comprehensive enough for 4.	3 / 5
Completeness	It clearly answers 'what' (backend architecture patterns, API design, DB optimization) but contains no 'Use when...' or equivalent trigger clause, so per the guidelines completeness is capped at 3.	3 / 5
Trigger Term Quality	It surfaces natural framework and topic keywords users actually say ('Node.js', 'Express', 'Next.js API routes', 'API design', 'database optimization') with good coverage, missing only some common synonyms/variations that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	Scoping to 'Node.js, Express, and Next.js API routes' gives it a clear niche with minimal overlap risk versus general-purpose coding skills; only minor overlap with adjacent full-stack skills keeps it from 5.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

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

Reviewed: ~18 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.