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

59%

Does it follow best practices?

Impact

100%

1.42x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

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

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 rich, mostly executable catalog of backend patterns with good section organization, but it is token-heavy, contains overlapping/standard examples, lacks a sequenced workflow with validation, and keeps all detail inline rather than splitting into references.

Suggestions

Trim overlapping and elementary examples (e.g., collapse the two caching patterns, drop the textbook rate-limiter/retry/queue sections) so remaining tokens earn their place.

Add validation/verification checkpoints around destructive or batch operations (DELETE, transactions, queue jobs) to lift workflow clarity above the cap.

Move the bulk of the pattern catalog into reference files under references/ and keep SKILL.md as a concise overview with one-level-deep pointers, exploiting progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The ~580-line body is mostly code with light prose, but it catalogs many standard patterns Claude already knows (e.g., in-memory rate limiter, retry/backoff, job queue) and duplicates caching as both CachedMarketRepository and Cache-Aside, so it is mostly efficient but could be tightened.	3 / 5
Actionability	Most sections provide concrete, copy-paste-ready TypeScript and SQL (repository, service layer, middleware, transactions, caching), with only minor stubs like vectorSearch and JobQueue.execute leaving small gaps.	4 / 5
Workflow Clarity	This is a pattern catalog rather than a sequenced workflow, and destructive/batch operations (DELETE handlers, transactions, queue processing) appear without validation checkpoints, which caps workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	There are clear section headers and no nested references, but no bundle files exist and all content is inlined in SKILL.md with no pointers to separate reference files, so structure is present but progressive disclosure is not exploited.	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 conveys the skill's domain and includes natural framework keywords, but it lacks an explicit 'Use when...' trigger clause, capping completeness. It is specific and reasonably distinctive but not maximally actionable as a trigger.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger situations (e.g., 'Use when designing Node.js/Express/Next.js API routes, modeling data access, or optimizing database queries').

Reframe topic nouns as concrete verbs (e.g., 'Design APIs, optimize database queries, structure middleware') to lift specificity above a list of domains.

Include common synonyms a user might say (e.g., 'REST endpoints', 'backend services') to round out trigger term coverage.

Dimension	Reasoning	Score
Specificity	The description lists several distinct areas ('API design, database optimization, and server-side best practices') but frames them as topics rather than concrete actions like 'extract' or 'fill', matching the anchor that names a domain with limited concrete actions.	3 / 5
Completeness	It clearly answers 'what' (backend architecture patterns, API design, etc.) but has no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Phrases like 'API design', 'database optimization', 'Node.js, Express, and Next.js API routes' are natural terms users would say, with good framework keyword coverage; only a few synonyms are missing, fitting the 'good keyword coverage' anchor.	4 / 5
Distinctiveness Conflict Risk	The framework-specific framing ('Node.js, Express, and Next.js API routes') carves a mostly distinct niche with only minor overlap risk against closely related backend skills.	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 (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-claude/skills/cc-skill-backend-patterns/SKILL.md
Commit: 57c135b

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.