agent-backend-patterns

Backend architecture patterns and best practices for scalable server-side applications.

Quality

22%

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

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is too abstract and lacks actionable specificity. It reads more like a topic heading than a skill description, failing to enumerate concrete capabilities or provide explicit trigger conditions for skill selection. The absence of a 'Use when...' clause and specific actions makes it difficult for Claude to know when to select this skill over others.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about API design, microservices, database architecture, caching strategies, or server performance optimization'

Replace 'patterns and best practices' with specific concrete actions such as 'Design RESTful APIs, implement caching layers, structure database schemas, configure load balancing, plan microservice boundaries'

Include natural trigger terms users would say: 'API', 'REST', 'microservices', 'database design', 'server performance', 'horizontal scaling', 'load balancer'

Dimension	Reasoning	Score
Specificity	The description uses vague, abstract language like 'patterns and best practices' without listing any concrete actions. It doesn't specify what Claude actually does (e.g., 'design APIs', 'implement caching', 'structure databases').	1 / 3
Completeness	The description only vaguely addresses 'what' (patterns and best practices) and completely lacks any 'when' clause or explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Contains some relevant keywords ('backend', 'architecture', 'server-side', 'scalable') but misses common variations users might say like 'API design', 'microservices', 'database schema', 'REST', 'performance optimization'.	2 / 3
Distinctiveness Conflict Risk	While 'backend' and 'server-side' provide some specificity, 'architecture patterns' and 'best practices' are generic enough to potentially overlap with database skills, API skills, or general coding skills.	2 / 3
	Total	6 / 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 empty shell—a table of contents with no substantive content. It provides no actionable guidance, patterns, or examples in the main file, completely delegating everything to sub-skills without any overview, quick-start, or context that would help Claude understand when and how to apply these patterns.

Suggestions

Add a quick-start section with at least one concrete, executable code example demonstrating a core backend pattern

Include brief summaries (1-2 sentences each) for each sub-skill explaining what it covers and when to use it

Add a workflow or decision tree showing how to choose between the different patterns based on use case

Provide at least one complete, copy-paste ready example of a common backend architecture scenario

Dimension	Reasoning	Score
Conciseness	The content is brief but provides almost no substance—it's essentially just a table of contents with links. While not verbose, it doesn't earn its tokens by providing any actionable content in the main file itself.	2 / 3
Actionability	No concrete code, commands, or executable guidance is provided. The skill only lists links to sub-skills without any actual patterns, examples, or instructions that Claude could act on.	1 / 3
Workflow Clarity	No workflow is defined. There are no steps, sequences, or processes described—just a list of links with no guidance on how or when to apply these patterns.	1 / 3
Progressive Disclosure	The structure attempts progressive disclosure by linking to sub-skills, but the main file provides zero overview content or context. A good overview should include quick-start guidance or summaries, not just naked links.	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: 3395991

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