backend-patterns

后端架构模式、API设计、数据库优化以及适用于Node.js、Express和Next.js API路由的服务器端最佳实践。

Quality

63%

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

Quality

Content

65%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 a well-organized, actionable catalog of backend patterns with mostly executable TypeScript examples, but it is a monolithic inlined reference rather than an overview with one-level-deep references, and its destructive/batch sections lack validation checkpoints.

Suggestions

Split the larger reference sections (RBAC, SQL transaction function, structured logger) into separate files under references/ and link to them from SKILL.md to improve progressive disclosure.

Add explicit validation/feedback checkpoints to the batch and destructive examples (e.g. verify RPC transaction return value, re-check after cache invalidation) to lift workflow clarity above 3.

Trim duplicated labels (PASS/GOOD, FAIL/BAD) and consolidate the two near-identical caching examples to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean code examples with short Chinese headers and little concept over-explanation, but has minor padding such as duplicated 'PASS: GOOD:'/'FAIL: BAD:' labels and two overlapping caching examples, fitting anchor 4 rather than 5.	4 / 5
Actionability	Each pattern ships concrete, largely copy-paste-ready TypeScript (repositories, middleware, caching, retry, RBAC, rate limiter, job queue), with only minor explicit elisions (e.g. '// Vector search implementation', '// Other methods...'), matching anchor 4.	4 / 5
Workflow Clarity	This is a flat patterns catalog with a 'when to activate' trigger list rather than a sequenced workflow, and the destructive/batch sections (DB transactions, N+1 batch fetch, job queue) lack validation/feedback checkpoints, so per the batch-operation cap it stays at anchor 3.	3 / 5
Progressive Disclosure	There are no bundle files and the ~590-line body inlines everything under good section headers; some substantial sections (full RBAC, SQL transaction function, logger) clearly belong in separate reference files, so it matches anchor 3 rather than 4.	3 / 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 clearly conveys a backend-patterns niche with good trigger terms and distinctiveness, but it lacks an explicit "Use when..." trigger clause and uses topic nouns rather than concrete action verbs, capping completeness and specificity.

Suggestions

Add an explicit 'Use when...' trigger clause (e.g., 'Use when designing REST/GraphQL endpoints, repository/service layers, or optimizing database queries') to lift completeness above 3.

Lead with concrete action verbs (design, implement, optimize, structure) instead of topic nouns to raise specificity.

Include common synonyms or file/extension cues users actually say to push trigger-term coverage toward 5.

Dimension	Reasoning	Score
Specificity	The description names the domain plus several specific sub-areas ("API设计", "数据库优化", "服务器端最佳实践") but these are noun-phrase topics rather than concrete action verbs like "extract/fill/merge", so it sits at anchor 3 rather than 4.	3 / 5
Completeness	It clearly states the "what" (backend patterns, API design, DB optimization, best practices) but has no "Use when..." or equivalent trigger clause, so per the missing-trigger guidance completeness is capped at anchor 3.	3 / 5
Trigger Term Quality	It includes natural terms users would say ("Node.js", "Express", "Next.js API路由", "API设计", "数据库优化") with good framework-level coverage, missing only some synonyms, matching anchor 4.	4 / 5
Distinctiveness Conflict Risk	The backend/server-side framing combined with named frameworks (Node.js, Express, Next.js API routes) gives it a distinct niche with only minor overlap risk against general coding or frontend skills, matching anchor 4.	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 (599 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/zh-CN/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.