CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

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

43%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.

A well-organized but bloated catalog of generic backend patterns. The code is largely executable, yet most of it duplicates knowledge Claude already has, and the lack of any real usage guidance or external file structure wastes context. The skill needs a much leaner overview with the catalog moved to reference files and a genuine 'when to use' section.

Suggestions

Cut the SKILL.md body to a lean overview (pattern names, one-line trade-offs) and move the full code catalog into separate reference files (e.g. references/caching.md, references/auth.md) linked one level deep.

Delete or rewrite the circular 'When to Use' section with real selection guidance, such as when to choose repository vs. service-layer vs. middleware patterns.

Remove boilerplate examples of patterns Claude already knows (JWT validation, retry with backoff, in-memory rate limiter) or reduce them to one-line mentions, keeping only project-specific conventions.

DimensionReasoningScore

Conciseness

Nearly 600 lines largely re-teach standard patterns Claude already knows cold (repository pattern, JWT validation, exponential backoff, structured logging), with generic filler like 'Backend patterns enable scalable, maintainable server-side applications.'

2 / 5

Actionability

The TypeScript examples are concrete and mostly copy-paste ready, but contain stub implementations (empty vectorSearch and execute methods) and an invalid SQL line (INSERT INTO markets VALUES (market_data) with a jsonb argument).

4 / 5

Workflow Clarity

This is a disconnected pattern catalog with no sequencing or validation checkpoints, and the 'When to Use' section is circular filler ('This skill is applicable to execute the workflow or actions described in the overview') that provides no real guidance.

2 / 5

Progressive Disclosure

Section headers organize the topics reasonably, but ~580 lines of reference catalog are inlined entirely in SKILL.md with no bundle files; caching, auth, rate-limiting, and logging sections clearly belong in separate reference files.

3 / 5

Total

11

/

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.

A decent domain-scoped description with good natural keywords, but it reads as a topic list rather than a capability list and completely lacks a 'when to use' trigger clause. Adding explicit trigger guidance and dropping the generic 'best practices' phrasing would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. 'Use when building or reviewing Node.js, Express, or Next.js API routes, designing REST endpoints, or optimizing database queries.'

Replace generic phrasing like 'server-side best practices' with concrete capabilities such as 'implement caching layers, JWT authentication, rate limiting, and background job queues'.

Include common synonyms users would naturally say (REST, endpoints, SQL, caching) to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names several areas ("API design", "database optimization") but uses topic nouns rather than concrete actions and pads with generic "server-side best practices", matching the 'domain plus limited actions' anchor rather than the several-specific-actions anchor.

3 / 5

Completeness

The 'what' is reasonably clear (backend patterns for Node/Express/Next), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3.

3 / 5

Trigger Term Quality

"backend", "API", "Node.js", "Express", "Next.js", and "server-side" are natural phrases users say, but common variations like "REST", "endpoints", "caching", and "SQL" are missing.

4 / 5

Distinctiveness Conflict Risk

The Node.js/Express/Next.js scoping makes it mostly distinct from skills for other stacks, though it could overlap with generic Node or architecture best-practice skills.

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.

Validation — 14 / 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

Path

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

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.