backend-patterns

Patrones de arquitectura backend, diseño de API, optimización de base de datos y buenas prácticas del lado del servidor para Node.js, Express y rutas API de Next.js.

Quality

65%

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

Quality

Content

72%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 content is highly actionable with complete, executable TypeScript and SQL examples across backend patterns, and is reasonably concise. Its weaknesses are the absence of validation/feedback checkpoints for destructive and batch operations and a monolithic single-file structure with no progressive disclosure via reference files.

Suggestions

Add explicit validation/verify checkpoints to risky workflows — e.g. after the transaction RPC, confirm both inserts committed; after N+1 batch rewrite, assert the creator map covers all ids; after queue processing, log success/failure counts — to lift workflow_clarity above the 3 cap.

Split the large pattern catalogs (auth/RBAC, caching, database patterns) into one-level-deep reference files under references/ and link them from a concise overview in SKILL.md to improve progressive_disclosure.

Trim the closing 'Recuerda...' line and redundant PASS/BIEN/FAIL/MAL labels in favor of a single consistent convention to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable pattern code with terse Spanish comments and assumes Claude's competence; only a few lines ('Recuerda...') and inline labels like 'PASS/BIEN' and 'FAIL/MAL' edge toward over-explanation that could be trimmed.	4 / 5
Actionability	Nearly every section provides complete, copy-paste-ready TypeScript (and SQL) examples covering the common cases — repository, service, middleware, caching, error handling, RBAC, queues, logging — with concrete signatures and usage blocks.	5 / 5
Workflow Clarity	Sections are topically organized but there is no end-to-end build/verify sequence and no validation checkpoints for risky or batch operations (transactions, N+1 batch fetches, background jobs, rate limiting), which per the rubric caps workflow_clarity at 3.	3 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ are absent) and all content lives inline in a single ~550-line SKILL.md; section headers give some structure, but large API/pattern catalogs that would benefit from being split into reference files are inlined, and the body cross-references other skills (api-design, security-review) without local files.	3 / 5
	Total	15 / 20 Passed

Description

58%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 specific and stack-scoped, clearly answering 'what' the skill covers, but it omits an explicit 'Use when...' trigger clause and uses generic rather than natural trigger phrasing, which limits discovery. Adding concrete trigger scenarios would lift completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause listing natural trigger phrases (e.g. 'Úsalo cuando diseñes endpoints REST/GraphQL, optimices consultas N+1, o agregues caché/middleware') to raise completeness above 3.

Surface natural trigger terms users actually say — 'N+1', 'caché', 'middleware', 'rate limiting', 'transacciones' — and file/extension synonyms instead of generic 'buenas prácticas' phrasing.

Tighten the capability list to mirror the body's pattern categories (repository/service/controller layers, retries/backoff, RBAC) so the description matches the actual scope.

Dimension	Reasoning	Score
Specificity	Lists several concrete backend actions — 'diseño de API', 'optimización de base de datos', 'buenas prácticas del lado del servidor' — for specific stacks (Node.js, Express, Next.js API routes), with minor coverage gaps around items like caching/background jobs that the body later covers.	4 / 5
Completeness	Provides a clear 'what' (backend architecture patterns, API design, DB optimization, server best practices) but has no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes relevant terms ('API', 'base de datos', 'Node.js', 'Express', 'Next.js') but offers only generic phrasing and lacks the natural user-style triggers (e.g. 'cuando diseñes endpoints', 'N+1', 'caché', '.ts') and synonyms that would make it surface reliably.	3 / 5
Distinctiveness Conflict Risk	The stack scoping (Node.js/Express/Next.js API routes) and domain focus give it a recognizable niche with only minor overlap risk against sibling skills like api-design or security-review that the body itself references.	4 / 5
	Total	14 / 20 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: docs/es/skills/backend-patterns/SKILL.md
Commit: d8409a4

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.