CtrlK
BlogDocsLog inGet started
Tessl Logo

cc-skill-backend-patterns

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

72

1.42x
Quality

60%

Does it follow best practices?

Impact

100%

1.42x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/cc-skill-backend-patterns/SKILL.md

The canonical home for this skill is cc-skill-backend-patterns in sickn33/agentic-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

58%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, largely executable catalog of backend patterns with tight, code-forward explanations, but it functions as a monolithic reference dump rather than a navigable, progressively-disclosed skill and lacks any sequenced workflow or validation checkpoints despite covering destructive and batch operations.

Suggestions

Split the pattern catalog into one-level-deep reference files (e.g., references/database.md, references/caching.md, references/auth.md) and keep SKILL.md as a concise overview with signaled links, to improve progressive disclosure.

Replace the generic "When to Use" boilerplate with concrete decision guidance: when to apply each pattern and the trade-offs between alternatives.

Add validation/checkpoint steps for the destructive and batch operations (e.g., verify transaction success before proceeding, confirm RBAC permission before DELETE, validate queue job results) to raise workflow clarity above the destructive/batch cap of 3.

DimensionReasoningScore

Conciseness

The body is code-forward with terse, useful comments (e.g., "// ✅ Select only needed columns", "// ❌ N+1 query problem") and little conceptual padding that Claude already knows; it is efficient with only minor trimmable instances, fitting anchor 4 rather than the lean anchor 5 given the sheer volume.

4 / 5

Actionability

It provides mostly executable TypeScript implementations (RateLimiter, JobQueue, Logger, JWT verification, repository classes) that are near copy-paste ready, but several methods are stubbed ("// Other methods...", "// Vector search implementation", "// Job execution logic"), leaving minor gaps that keep it at anchor 4 instead of 5.

4 / 5

Workflow Clarity

There is no overarching multi-step workflow or sequence — the skill is a topical pattern catalog — and the "When to Use" section is generic boilerplate ("This skill is applicable to execute the workflow or actions described in the overview"); it also covers destructive/batch operations (DELETE handlers, transactions, batch fetches) without overall validation/checkpoint guidance, fitting anchor 2 more than 3.

2 / 5

Progressive Disclosure

The body has clear section headers (API Design, Database, Caching, Error Handling, Auth, Rate Limiting, Background Jobs, Logging) but is a ~580-line monolith with all content inlined and no references to separate files (none exist); because it far exceeds the <50-line simple-skill exception, the inlined catalog that belongs in reference files lands at anchor 3 rather than higher.

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 scopes the skill to backend/server-side patterns for a specific Node stack and lists relevant trigger terms, but it omits any explicit "Use when..." guidance, which caps completeness and limits its triggerability. It is solidly above average but not comprehensive.

Suggestions

Add an explicit "Use when..." clause naming concrete trigger situations (e.g., designing API routes, optimizing database queries, structuring a Node/Express backend) to raise completeness above 3.

Reframe topic areas as concrete actions where possible (e.g., "Structure REST endpoints, batch data access, add caching and auth middleware") to move specificity toward anchor 4-5.

Include common natural synonyms a user might say ("REST API", "server-side", "backend services") to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description names several domain areas ("API design, database optimization") and a concrete tech stack ("Node.js, Express, and Next.js API routes"), but these are topics/areas rather than the concrete actions (extract, fill, merge) the higher anchors require; it is not merely minimal (2) but does not reach several specific actions (4).

3 / 5

Completeness

There is a clear "what" (backend architecture patterns, API design, database optimization, server-side best practices for the named stack), but no "Use when..." clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

It includes natural terms users say ("Node.js", "Express", "Next.js API routes", "API design", "database optimization", "backend"); coverage is good but misses some common synonyms/variants, fitting anchor 4 rather than the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

It targets a specific niche (server-side backend for Node.js/Express/Next.js API routes) with distinct triggers, giving mostly-distinct positioning with only minor overlap risk against general web-dev skills; it does not have the fully-conflict-free trigger phrasing of anchor 5.

4 / 5

Total

14

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (589 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
administrakt0r/AI-Agents-Safe-Coding-Skills
Reviewed

Table of Contents

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.