backend-architect

Expert backend architect specializing in scalable API design, microservices architecture, and distributed systems.

1.17x

Quality

17%

Does it follow best practices?

Impact

89%

1.17x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/backend-architect/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 reads like a resume headline rather than a functional skill description. It uses first-person framing ('Expert...specializing') which violates voice guidelines, lacks concrete actions, and provides no guidance on when Claude should select this skill. The description would benefit from listing specific capabilities and explicit trigger conditions.

Suggestions

Replace the persona-style framing with concrete actions in third person (e.g., 'Designs REST APIs, implements microservices patterns, architects distributed systems').

Add a 'Use when...' clause with natural trigger terms like 'when the user asks about API design, service architecture, scaling backend systems, or distributed system patterns'.

Include specific deliverables or outputs (e.g., 'generates architecture diagrams, writes API specifications, reviews service boundaries').

Dimension	Reasoning	Score
Specificity	Uses vague, abstract language like 'specializing in' and 'expert' without listing concrete actions. No specific tasks like 'design REST endpoints' or 'implement service discovery' are mentioned.	1 / 3
Completeness	Only vaguely addresses 'what' through domain areas, completely missing 'when' guidance. No 'Use when...' clause or explicit trigger conditions are provided.	1 / 3
Trigger Term Quality	Contains some relevant domain keywords ('API design', 'microservices', 'distributed systems') but uses technical jargon rather than natural user phrases. Missing common variations like 'backend', 'REST', 'services', 'scaling'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'backend', 'API', and 'microservices' provides some specificity, but could easily overlap with general coding skills, system design skills, or architecture review skills.	2 / 3
	Total	6 / 12 Passed

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 is essentially a comprehensive knowledge dump about backend architecture concepts rather than actionable guidance. It extensively lists technologies and patterns Claude already knows without providing concrete examples, templates, or executable code. The content would benefit from dramatic reduction and replacement of concept lists with specific, actionable templates and examples.

Suggestions

Remove or drastically reduce the 'Capabilities' section - Claude already knows what OAuth, JWT, REST, GraphQL, etc. are. Replace with specific decision frameworks or templates.

Add concrete, executable examples: API contract templates (actual OpenAPI snippets), Mermaid diagram templates, example ADR formats, and sample code for resilience patterns.

Split content into separate reference files (e.g., PATTERNS.md for resilience patterns, CONTRACTS.md for API contract examples) and keep SKILL.md as a concise overview with clear navigation.

Add validation checkpoints to the workflow: 'After defining service boundaries, verify with checklist X' or 'Before finalizing API contracts, validate against these criteria.'

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive lists of concepts Claude already knows (OAuth 2.0, JWT, REST, GraphQL, etc.). The skill reads like a comprehensive textbook rather than actionable guidance, with hundreds of lines of capability listings that don't add value beyond what Claude inherently understands.	1 / 3
Actionability	No concrete code examples, commands, or executable guidance anywhere. The entire skill consists of abstract descriptions and bullet-point lists of concepts. The 'Response Approach' section lists steps but provides no specific implementation details or templates.	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, feedback loops, or concrete verification steps. The workflow is present but lacks the specificity needed for complex architectural decisions.	2 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files or structured navigation. All content is inline in one massive document with no clear hierarchy for discovery. The 'Capabilities' section alone contains hundreds of bullet points that could be split into reference files.	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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: sickn33/antigravity-awesome-skills
Commit: 9c177eb

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.