agent-backend-patterns

Master backend logic, APIs, and microservices architectures. Covers REST, GraphQL, caching, and database transactions.

Quality

27%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agent/skills/agent-backend-patterns/SKILL.md

Quality

Discovery

32%

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 identifies a clear technical domain and lists relevant technologies, but suffers from vague action language ('Master', 'Covers') and completely lacks explicit trigger guidance. Without a 'Use when...' clause, Claude cannot reliably determine when to select this skill over others in a large skill library.

Suggestions

Add an explicit 'Use when...' clause with trigger scenarios like 'Use when building server-side logic, designing REST or GraphQL APIs, implementing microservices, or optimizing database queries'.

Replace vague verbs like 'Master' and 'Covers' with concrete actions such as 'Design and implement APIs', 'Architect microservices', 'Optimize caching strategies'.

Expand trigger terms to include common user phrases like 'backend development', 'server-side', 'API endpoints', 'service-to-service communication'.

Dimension	Reasoning	Score
Specificity	Names the domain (backend) and lists several areas (APIs, microservices, REST, GraphQL, caching, database transactions), but uses vague framing like 'Master' and 'Covers' rather than concrete actions like 'design', 'implement', or 'debug'.	2 / 3
Completeness	Describes what the skill covers but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant technical terms users might say (REST, GraphQL, APIs, microservices, caching), but misses common variations like 'server-side', 'endpoints', 'API design', 'backend development', or 'service architecture'.	2 / 3
Distinctiveness Conflict Risk	Backend development is a broad domain that could overlap with database skills, API-specific skills, or general coding skills. Terms like 'APIs' and 'database transactions' are not unique enough to prevent conflicts.	2 / 3
	Total	7 / 12 Passed

Implementation

22%

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

This skill is essentially an index page with no substantive content. While it correctly links to sub-skills (good progressive disclosure structure), it provides no actionable guidance, no workflow context, and no quick-start content. The main file should at minimum explain when to use which patterns and provide a brief orientation to backend architecture.

Suggestions

Add a quick-start section with 1-2 concrete code examples showing common backend patterns (e.g., a basic REST endpoint with service layer)

Provide a brief decision guide or workflow explaining when to use which sub-skill (e.g., 'Start with RESTful API Structure, add Repository Pattern for data access, use Caching when...')

Remove the empty '## API Design Patterns' heading or populate it with actual content

Add brief 1-sentence descriptions next to each sub-skill link explaining what problem it solves

Dimension	Reasoning	Score
Conciseness	The content is brief and doesn't over-explain concepts, but the single-line description and empty '## API Design Patterns' section add no value. The numbered list format with emoji is slightly verbose.	2 / 3
Actionability	The skill provides zero concrete guidance, code, or commands. It's purely a table of contents with links to sub-skills, offering no executable or actionable content in the main file itself.	1 / 3
Workflow Clarity	There is no workflow, sequence, or process described. The skill doesn't explain when to use which pattern, how they relate, or any order of operations for backend development tasks.	1 / 3
Progressive Disclosure	The skill does use one-level-deep references to sub-skills, which is good structure. However, there's no overview content, no quick-start guidance, and no context for when to use each linked resource—it's just a bare list.	2 / 3
	Total	6 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: Dokhacgiakhoa/antigravity-ide
Commit: 332e58b

Reviewed: 17 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.