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 is a clean index-style SKILL.md that correctly pushes 584 lines of detailed material into a single well-organized reference, respecting the token budget. Its weaknesses are boilerplate circularity in "When to Use" and the absence of any inline quick-start content or section map, which force a full reference load before any work begins.

Suggestions

Replace the circular "When to Use" text with concrete activation conditions, e.g. "Use when designing or refactoring Express/Next.js API routes, optimizing database queries, or adding caching, rate limiting, or auth middleware."

Add a brief section map or quick-start snippet inline (e.g., one canonical middleware or repository-pattern example, or a bulleted list of the guide's ten sections) so Claude can navigate without loading the full 584-line guide.

Tighten the Limitations section by removing the first bullet, which restates the scope already covered by the description and guide pointer.

Dimension	Reasoning	Score
Conciseness	The body is short and assumes Claude's competence, but the circular "This skill is applicable to execute the workflow or actions described in the overview" and a scope-restating limitations bullet are filler that could be trimmed, keeping it below the every-token-earns-its-place anchor (5).	4 / 5
Actionability	The pointer to the guide is specific and operationally qualified ("read the guide completely" vs "load the relevant sections", "treat its safety, prerequisites, and validation requirements as mandatory"), but the body itself contains no code, commands, or quick-start example — concrete guidance is incomplete rather than minimal (anchor 3, not 2 or 4).	3 / 5
Workflow Clarity	A rough flow exists (read guide, honor prerequisites, "Stop and ask for clarification if required inputs... are missing", execute with mandatory validation), giving one explicit checkpoint, but the actual sequence and validation steps are deferred to the reference and remain implicit in the body.	3 / 5
Progressive Disclosure	The bundle matches the anchor-4 structure: a concise SKILL.md overview with a single clearly-signaled, one-level-deep reference (references/detailed-guide.md exists, is well-sectioned, and holds no nested references), with the minor gap that the body never enumerates the guide's sections, so navigation requires loading the 584-line file.	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 identifies a clear framework-specific niche with natural trigger terms, but it reads as a topic list rather than an action list and entirely lacks a "when to use" trigger clause. Adding explicit usage triggers and concrete actions would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. "Use when building or reviewing Node.js/Express/Next.js backends, designing REST APIs, or optimizing database queries."

Replace the generic "server-side best practices" phrase with concrete actions (e.g., "implements repository/service-layer patterns, prevents N+1 queries, adds caching and rate limiting").

Include common synonyms and variations users say, such as "REST", "endpoints", "API routes", and "server-side", to strengthen trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domains and a few semi-concrete areas ("API design", "database optimization") but actions are nominal and "server-side best practices" is generic filler, so it falls between the minimal-actions anchor (2) and the several-specific-actions anchor (4).	3 / 5
Completeness	The "what" is stated via domains and frameworks, but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	"Node.js", "Express", and "Next.js API routes" are terms users naturally say, giving good keyword coverage, but common variations like "REST", "endpoints", "server", or "SQL" are missing, so it is not comprehensive (5).	4 / 5
Distinctiveness Conflict Risk	The named frameworks ("Node.js, Express, and Next.js API routes") carve a mostly distinct niche with only minor overlap risk against closely related backend/testing skills; it is more specific than the overlap-prone anchor 3 example.	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: 7b534bc

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