backend-patterns

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

Quality

52%

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 ./.agents/skills/backend-patterns/SKILL.md

Quality

Content

42%

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

The skill is highly actionable with complete code patterns, but it is a verbose monolith that under-utilizes progressive disclosure and provides no guided workflow or validation checkpoints. Conciseness, workflow clarity, and progressive disclosure are the weaknesses.

Suggestions

Split the catalog into reference files (e.g. references/api-patterns.md, references/database.md, references/caching.md) and keep SKILL.md as a concise overview with clearly signaled one-level-deep links.

Add a guided workflow for the genuinely multi-step operations (e.g. transaction with explicit validate-rollback steps, or deploy-safe rate-limiting setup) with validation checkpoints.

Trim inline comments that restate what the code already shows and remove teaching of well-known concepts to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	At ~550 lines it is a monolithic wall of fairly complete code examples for patterns Claude already knows (repository, service, middleware, JWT verification), with redundant inline comments restating what the code does; much of this could be trimmed or split out.	1 / 3
Actionability	Provides multiple complete, executable TypeScript/SQL snippets (Repository, Service, Cache-Aside, JWT verification, RBAC, retry-with-backoff, structured logging) that are concrete and copy-paste ready.	3 / 3
Workflow Clarity	There is no multi-step sequence for any task and no validation/checkpoint steps; patterns are presented as a reference catalog rather than a guided flow, and batch/destructive operations like transactions and rate-limiting lack any validate-fix-retry feedback loop.	1 / 3
Progressive Disclosure	All content lives inline in a single large SKILL.md with no bundle files (references/scripts/assets absent) and no one-level-deep references, so there is no progressive disclosure structure despite the volume of content that would benefit from being split.	1 / 3
	Total	6 / 12 Passed

Description

62%

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 clearly niche-scoped to backend work, but lacks an explicit 'Use when...' trigger clause and leans on framework names rather than natural user phrases. Completeness is the main cap, at 2.

Suggestions

Add an explicit 'Use when...' clause naming natural user triggers (e.g. 'Úsalo cuando se diseñen endpoints de API, se optimicen consultas de base de datos o se estructure el manejo de errores para APIs').

Add natural-language trigger terms a user would actually say ('endpoints de API', 'consultas N+1', 'rate limiting', 'caché Redis') alongside the framework names.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across the backend domain: 'diseño de API', 'optimización de base de datos', and 'buenas prácticas del lado del servidor', naming specific actions rather than vague abstractions.	3 / 3
Completeness	It clearly states what the skill covers, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so the 'when' half is only implied and completeness is capped at 2.	2 / 3
Trigger Term Quality	Includes relevant technical terms (Node.js, Express, Next.js API routes), but these are framework names rather than the natural phrases a user would say when asking for backend help, and common variations like 'API endpoints' or 'database queries' are only implied.	2 / 3
Distinctiveness Conflict Risk	The Node.js/Express/Next.js backend niche is distinct and, combined with server-side best practices, is unlikely to overlap with non-backend skills.	3 / 3
	Total	10 / 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 (557 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: affaan-m/ECC
Path: .agents/skills/backend-patterns/SKILL.md
Commit: 754b8dd

Reviewed: 1 day 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.