backend-patterns

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

Quality

69%

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

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 body is a thorough, highly actionable catalog of backend patterns with executable TypeScript examples and clean section organization. Its weaknesses are the lack of multi-step workflows with validation checkpoints and the absence of progressive disclosure — everything lives in one large inlined file.

Suggestions

Split large reference areas (caching strategies, auth/RBAC, logging/monitoring) into separate files under references/ and link to them from SKILL.md so the main file stays a concise overview.

Add at least one end-to-end workflow with explicit validation checkpoints (e.g. build API -> validate input with Zod -> test -> deploy) to raise workflow clarity above the catalog-of-patterns baseline.

Trim the closing "記住" summary line and placeholder comments to push conciseness toward a lean 5.

Dimension	Reasoning	Score
Conciseness	The body is code-heavy with brief comments and avoids explaining concepts Claude already knows, fitting the "efficient; minor instances of over-explanation" anchor; not a 5 because the closing "記住" line and a few placeholder comments ("// 其他方法...") are trimmable padding.	4 / 5
Actionability	Provides copy-paste-ready TypeScript across repository, service, middleware, caching, error handling, retry, JWT/RBAC, rate-limiting, queue, and logging patterns covering common cases; not downgraded because the few intentional placeholders (vectorSearch, execute) are justified abstractions rather than missing detail.	5 / 5
Workflow Clarity	This is a pattern catalog rather than a sequenced multi-step workflow, and there are no explicit validation checkpoints tying patterns into an end-to-end process, matching the "steps present but checkpoints missing or implicit" anchor; not a 4 because no workflow with validation feedback loops is provided despite covering database/batch operations.	3 / 5
Progressive Disclosure	The 588-line body is well-organized with clear section headers but is a monolithic single file with no external references, so content that belongs in separate files (caching, auth, logging references) is inlined; not a 2 because the internal section structure is solid, not a 4 because nothing is split out or signaled as one-level-deep references.	3 / 5
	Total	15 / 20 Passed

Description

66%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 well-scoped to concrete backend domains and frameworks, with good natural trigger terms. Its main weakness is the missing explicit "Use when..." trigger guidance, which caps completeness.

Suggestions

Append an explicit trigger clause, e.g. "Use when designing or reviewing backend APIs, optimizing database queries, or structuring server-side code for Node.js, Express, or Next.js API routes."

Add a few common synonym triggers users might say (e.g. "REST endpoints", "query performance", "middleware") to broaden natural keyword coverage.

Tighten "server-side best practices" into one or two more concrete actions to push specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the domain plus several concrete capabilities — "API design, database optimization, and server-side best practices" — matching the anchor for listing several specific actions with minor coverage gaps; not a 5 because the actions are topic areas rather than a comprehensive enumerated action list.	4 / 5
Completeness	The description gives a clear "what" (backend architecture patterns, API design, database optimization, best practices) but has no "Use when..." or equivalent explicit trigger guidance, which per the guidelines caps completeness at 3; not a 4 because the "when" is entirely missing rather than merely weak.	3 / 5
Trigger Term Quality	Includes natural domain terms users would say ("API design", "database optimization", "Node.js", "Express", "Next.js API routes") giving good keyword coverage; not a 5 because common synonyms and broader trigger phrasings are absent.	4 / 5
Distinctiveness Conflict Risk	Scoping to "Node.js, Express, and Next.js API routes" gives a mostly-distinct niche with only minor overlap risk against a general Node.js or database skill; not a 5 because the broad "backend architecture patterns / best practices" framing could still overlap with adjacent backend skills.	4 / 5
	Total	15 / 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: e04ea0b

Reviewed: 2 days 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.