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

64%

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/backend-architect/SKILL.md

Quality

Content

48%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.

A well-structured but over-long persona catalog that enumerates widely-known backend knowledge Claude already has, with a clear advisory workflow but no executable examples or external reference files. It reads more like a capability inventory than a lean, actionable skill.

Suggestions

Trim the Capabilities and Framework sections to the non-obvious choices and defer the full technology catalog to a reference file; Claude already knows what RabbitMQ, Express, and Kafka are.

Move the large capability/framework enumerations into bundled reference files (e.g. references/patterns.md, references/tech-stacks.md) and keep SKILL.md as a lean overview with one-level-deep links.

Add a concrete artifact template (e.g. an OpenAPI skeleton or a Mermaid service-diagram stub) so the 'Output Examples' guidance is copy-paste actionable rather than purely descriptive.

Dimension	Reasoning	Score
Conciseness	The ~330-line body is an exhaustive enumeration of well-known technologies and patterns (e.g. 'RabbitMQ, AWS SQS, Azure Service Bus', 'Express, NestJS, Fastify, Koa') that Claude already knows, constituting noticeable padding across many sections.	2 / 5
Actionability	The 'Response Approach' provides a concrete 10-step process and 'Output Examples' a deliverable checklist, but there is no executable code, no templates, and the per-capability sections are high-level descriptions rather than actionable instruction.	3 / 5
Workflow Clarity	A clear, well-ordered 10-step sequence (Understand requirements → Define boundaries → Design contracts → … → Document) is present; validation checkpoints are absent but are not critical for an advisory design skill, so this is a minor gap rather than a cap.	4 / 5
Progressive Disclosure	Section structure is clear, but the skill is a monolithic inlined catalog with no bundle files and no references — large capability/framework catalogs that belong in separate reference files are all kept inline in SKILL.md.	3 / 5
	Total	12 / 20 Passed

Description

80%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.

A strong, third-person description with concrete capability coverage and an explicit use-trigger, though the trigger is narrow and the role borders on adjacent architecture skills. It reads as a clear, specific niche rather than generic fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete capabilities across API design, microservices, event-driven architecture, resilience, and observability ('Masters REST/GraphQL/gRPC APIs', 'Handles service boundary definition, inter-service communication, resilience patterns'), giving comprehensive coverage rather than vague claims.	5 / 5
Completeness	Clearly answers 'what' (the architect's expertise domains) and 'when' ('Use PROACTIVELY when creating new backend services or APIs'), but the 'when' is a single narrow clause that could be more explicit and cover design/planning triggers.	4 / 5
Trigger Term Quality	Includes natural terms users would say ('backend services', 'APIs', 'microservices') and an explicit trigger ('Use PROACTIVELY when creating new backend services or APIs'), but the trigger phrasing is narrow and omits common synonyms like 'design an API' or 'plan architecture'.	4 / 5
Distinctiveness Conflict Risk	The backend/API/microservices niche is clearly staked out and distinguishable, but it overlaps with adjacent roles (cloud-architect, database-architect, security-auditor, performance-engineer) that the skill itself references, creating minor conflict risk.	4 / 5
	Total	17 / 20 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/backend-architect/SKILL.md
Commit: 3eff4af

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.