backend-development

Backend API design, database architecture, microservices patterns, and test-driven development. Use for designing APIs, database schemas, or backend system architecture.

Quality

86%

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

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A concise, actionable reference catalog of backend patterns with strong executable examples. It lacks multi-step workflows with validation and keeps everything inline rather than splitting into referenced files.

Suggestions

For destructive or batch patterns (e.g. schema migrations, cache invalidation), add a short validate/retry sequence so workflow clarity can reach 3.

Move the longer reference sections (e.g. full SQL schema, auth middleware) into separate files and link them from a concise overview in SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is a lean pattern catalog — mostly executable code with terse inline comments and no padding or explanation of concepts Claude already knows.	3 / 3
Actionability	Provides concrete, copy-paste-ready examples across SQL schema, TypeScript JWT middleware, cache-aside, and rate limiting, matching the anchor for fully executable guidance.	3 / 3
Workflow Clarity	Content is organized by topic but presents no sequenced multi-step process or validation checkpoints, so it sits below the anchor requiring explicit feedback loops.	2 / 3
Progressive Disclosure	A single ~150-line file holds all reference material inline with no signaled links to deeper files; well-sectioned but monolithic rather than progressively disclosed.	2 / 3
	Total	10 / 12 Passed

Description

92%

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 strong description: concrete capabilities, third-person voice, and an explicit 'Use for' trigger clause. Its only weakness is a somewhat broad scope that may overlap with narrower specialized skills.

Suggestions

Tighten the 'Use for' clause to name microservices-specific triggers and drop generic cross-cutting terms like test-driven development to reduce overlap with specialized skills.

Add a couple of natural user phrasings (e.g. 'building a service', 'designing a data model') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'Backend API design, database architecture, microservices patterns, and test-driven development' — matching the anchor for several specific named actions.	3 / 3
Completeness	Explicitly answers both what (the listed capabilities) and when via an explicit 'Use for ...' clause, satisfying the anchor for clearly answering both.	3 / 3
Trigger Term Quality	Trigger clause 'Use for designing APIs, database schemas, or backend system architecture' uses natural terms a user would actually say, with good coverage of the domain.	3 / 3
Distinctiveness Conflict Risk	Backend is a recognizable niche but the scope is broad and includes cross-cutting items like 'test-driven development', so it could overlap with more specialized API- or database-specific skills.	2 / 3
	Total	11 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: MoizIbnYousaf/Ai-Agent-Skills
Path: skills/backend-development/SKILL.md
Commit: 039ad59

Reviewed: about 5 hours 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.