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.

Quality

59%

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

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 skill is a thorough, actionable catalog of backend patterns with strong executable examples, but it is verbose for a single file and lacks validation checkpoints in its batch/destructive operations. Splitting reference material into bundle files would improve navigation.

Suggestions

Add explicit validation/verification steps to destructive and batch patterns (e.g. after create_market_with_position verify both rows exist; after queue processing confirm job completion) to lift workflow_clarity.

Trim obvious inline comments and consolidate long examples into a references/ file (e.g. references/patterns.md), keeping SKILL.md a lean overview with one-level-deep links.

Fill in the stub implementations (vectorSearch, JobQueue.execute) or explicitly mark them as intentionally abstracted so examples remain copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is efficient and code-driven, but ~580 lines of examples include redundant inline comments restating obvious concepts ('// Business logic', '// Check cache first', '// Other methods...') that could be trimmed.	3 / 5
Actionability	Most sections provide concrete, copy-paste-ready TypeScript/SQL examples covering the common backend cases; minor gaps (e.g. vectorSearch and execute(job) left as stubs) keep it from a 5.	4 / 5
Workflow Clarity	This is a pattern catalog rather than sequenced workflows, and operations that are batch/destructive (transactions, queues, rate limiting) lack explicit validation/verification checkpoints, capping this dimension at 3 per the guidance.	3 / 5
Progressive Disclosure	Content is organized into clear section headers, but everything is inlined into a single ~580-line SKILL.md with no bundle files (references/, scripts/, assets/ absent), so material that would benefit from being split (e.g. full API references) is not progressively disclosed.	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 communicates the backend-patterns niche and includes solid natural trigger terms, but it omits any explicit 'when to use' guidance, which limits its completeness score. It is concise and appropriately scoped.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers, e.g. 'Use when designing or reviewing Node.js/Express/Next.js API routes, database queries, or server-side architecture.'

Reframe the category list as concrete actions (e.g. 'Design REST APIs, optimize database queries, implement caching and auth middleware') to push specificity toward 4-5.

Include common synonyms developers say ('backend', 'server-side', 'API routes', 'endpoints') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Backend architecture patterns, API design, database optimization') plus several specific capability areas, but these read as topical categories more than concrete named actions like the score-4/5 anchors.	3 / 5
Completeness	It clearly states what the skill does, but there is no 'Use when...' or equivalent trigger clause, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Natural developer terms are well covered ('API design', 'database optimization', 'Node.js', 'Express', 'Next.js API routes') with only minor synonyms missing; not quite comprehensive enough for a 5.	4 / 5
Distinctiveness Conflict Risk	The backend/server-side Node/Express/Next.js API niche is mostly distinct with only minor overlap risk against general web-dev 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 (594 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: sickn33/antigravity-awesome-skills
Path: skills/cc-skill-backend-patterns/SKILL.md
Commit: 1f67c44

Reviewed: 1 day 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.