backend-architect

Expert backend architect specializing in scalable API design, microservices architecture, and distributed systems. Masters REST/GraphQL/gRPC APIs, event-driven architectures, service mesh patterns, and modern backend frameworks. Handles service boundary definition, inter-service communication, resilience patterns, and observability. Use PROACTIVELY when creating new backend services or APIs.

Quality

12%

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 ./docs/v19.7/configuration/agent/skills_external/antigravity-awesome-skills-main/skills/backend-architect/SKILL.md

Quality

Discovery

N/A

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

Something went wrong

Implementation

12%

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

This skill content reads like a comprehensive backend architecture encyclopedia rather than actionable guidance for Claude. It extensively lists concepts, patterns, and technologies that Claude already knows, without providing concrete examples, executable code, or specific implementation guidance. The document would benefit from dramatic reduction in scope, addition of concrete examples with actual code/schemas, and splitting detailed reference material into separate files.

Suggestions

Remove or drastically reduce the extensive capability lists (API Design, Microservices, Security Patterns, etc.) - Claude already knows these concepts. Focus only on project-specific conventions or preferences.

Add concrete, executable examples: actual OpenAPI snippets, real Mermaid diagrams, sample API contract definitions, or specific code patterns to follow.

Split detailed reference material (e.g., specific patterns for different frameworks, detailed security checklists) into separate linked files, keeping SKILL.md as a concise overview.

Add validation checkpoints to the workflow: e.g., 'After defining service boundaries, verify with stakeholder review checklist' or 'Before finalizing API contract, validate against these criteria.'

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive lists of concepts Claude already knows (OAuth 2.0, JWT structure, REST methods, etc.). The document is essentially a comprehensive textbook of backend architecture concepts rather than actionable guidance specific to this skill.	1 / 3
Actionability	No executable code, no concrete commands, no specific examples with actual implementation. The entire document describes concepts and lists capabilities without providing any copy-paste ready guidance or concrete steps.	1 / 3
Workflow Clarity	The 'Response Approach' section provides a 10-step sequence, and 'Instructions' gives a 4-step process, but there are no validation checkpoints, no feedback loops for error recovery, and no concrete verification steps for the architectural decisions.	2 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files. All content is inline despite being over 300 lines. Content that could be split into separate reference files (API patterns, security patterns, observability patterns) is all crammed into one document.	1 / 3
	Total	5 / 12 Passed

Validation

90%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	10 / 11 Passed

Repository: duclm1x1/Dive-Ai
Commit: 20ba150

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