backend-patterns

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

Quality

59%

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

Quality

Content

57%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 body is a well-organized, code-dense pattern catalog with mostly executable TypeScript examples and little conceptual padding. Its weaknesses are its monolithic single-file structure, duplicated caching sections, stub implementations, one invalid SQL example, and the absence of any workflow/validation guidance for risky operations like transactions.

Suggestions

Split the ~590-line catalog into per-topic 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 links.

Remove the duplication between the Redis CachedMarketRepository and the cache-aside function sections, keeping one canonical caching example.

Fix the plpgsql transaction example (the INSERT statements are invalid SQL — jsonb cannot be inserted as a row value) and complete or clearly justify the vectorSearch/execute stubs.

Dimension	Reasoning	Score
Conciseness	The body is code-first with minimal padded explanation, but it duplicates the same cache-aside logic in two sections (CachedMarketRepository and getMarketWithCache) and the ~590-line catalog could be tightened, matching anchor 3 ('mostly efficient but could be tightened').	3 / 5
Actionability	Most snippets (rate limiter, structured logger, retry with backoff, JWT auth, RBAC, middleware, error handler, N+1 fix) are executable TypeScript, but there are gaps: vectorSearch and JobQueue.execute are comment stubs and the plpgsql example's 'INSERT INTO markets VALUES (market_data)' is not valid SQL — minor gaps that fit anchor 4 while falling short of anchor 5.	4 / 5
Workflow Clarity	This is a pattern reference with no step sequencing or decision guidance for choosing among patterns, and the database operations (transaction, batch fetching) lack validate→fix→retry feedback loops, which caps workflow clarity at 3 per the scoring notes.	3 / 5
Progressive Disclosure	Section headers are clear and well-organized, but ~590 lines of per-topic pattern libraries (API, database, caching, auth, logging) are inlined in SKILL.md with no bundle files, fitting anchor 3 ('content that should be separate is inline'); it is not 2 because structure and navigation are present.	3 / 5
	Total	13 / 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 clearly identifies its domain and technology scope with good natural keywords, but it reads as a topic catalog rather than an action list and completely lacks a 'Use when...' trigger clause. Adding explicit trigger guidance and action verbs would raise both completeness and specificity.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g. 'Use when designing REST APIs, optimizing database queries, or building Node.js/Express/Next.js backend routes.'

Convert topic nouns into concrete actions (e.g. 'Design RESTful APIs, optimize database queries, implement caching and rate limiting') to sharpen specificity.

Include a few more natural synonyms (REST endpoints, SQL, Postgres/Supabase) that users would say when needing this skill.

Dimension	Reasoning	Score
Specificity	The description lists concrete capability areas ("API design, database optimization, and server-side best practices") scoped to named technologies, but these are topic nouns rather than executable actions, matching anchor 3 rather than the action-verb comprehensiveness of anchor 5.	3 / 5
Completeness	The 'what' is clear (backend architecture patterns, API design, database optimization), but there is no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3; it is not 4 because the 'when' is wholly absent rather than merely implicit.	3 / 5
Trigger Term Quality	Natural user terms like "backend", "API", "Node.js", "Express", and "Next.js API routes" are present, but a few common synonyms (REST, SQL, Postgres, endpoints) are missing, fitting anchor 4's 'good keyword coverage; a few natural terms missing'.	4 / 5
Distinctiveness Conflict Risk	Technology scoping ("for Node.js, Express, and Next.js API routes") creates a distinct niche with minimal conflict risk, but the broad phrase "server-side best practices" leaves minor overlap with general web development skills, matching anchor 4.	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
skill_md_line_count	SKILL.md is long (588 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: docs/zh-TW/skills/backend-patterns/SKILL.md
Commit: c70874f

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.