backend-architect

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

Quality

45%

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

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

The content is well-structured by section but functions as a verbose knowledge dump of backend terminology Claude already knows, with high-level rather than executable guidance and no progressive disclosure into reference files. It reads more as a persona/catalog than an actionable skill.

Suggestions

Move the large capabilities catalogs (API patterns, microservices, event-driven, etc.) into reference files referenced one level deep from SKILL.md to improve progressive disclosure and token efficiency.

Trim terminology enumerations that restate concepts Claude already knows, keeping only the non-obvious guidance, deferrals, and decisions specific to this architect role.

Add concrete, executable artifacts (an ADR template, a sample OpenAPI skeleton, a Mermaid service-diagram template) so the skill instructs rather than merely describes.

Dimension	Reasoning	Score
Conciseness	The ~327-line body is a wall of terminology bullets (e.g. "RESTful APIs: Resource modeling, HTTP methods, status codes, versioning strategies") cataloging concepts Claude already knows across every backend subdomain, matching the level-2 anchor of noticeably verbose with several unnecessary padded sections.	2 / 5
Actionability	Sections like "Response Approach" (a 10-step process) and "Output Examples" give some concrete guidance, but the bulk is an abstract capabilities catalog rather than specific, executable instructions, fitting the level-3 anchor of some concrete guidance that is incomplete.	3 / 5
Workflow Clarity	"Instructions" and "Response Approach" provide a clear sequence of steps, but there are no validation checkpoints or feedback loops; because the skill is advisory rather than destructive/batch, the level-3 anchor (sequence present, checkpoints missing/implicit) fits best.	3 / 5
Progressive Disclosure	The file has good section headers, but no bundle files exist and the entire capabilities catalog is inlined in SKILL.md with no one-level-deep references, matching the level-3 anchor of decent structure with content that should be split remaining inline.	3 / 5
	Total	11 / 20 Passed

Description

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

The description clearly identifies the domain and specialization but lacks an explicit trigger ("Use when") clause and concrete action verbs, which caps completeness and limits specificity. It is reasonably distinctive within the architect skill family.

Suggestions

Add an explicit "Use when..." clause listing the natural trigger phrases (e.g. designing APIs, defining service boundaries, planning microservices) to lift completeness above 3.

Replace static specialization language with concrete actions (e.g. "Designs service boundaries and API contracts, plans resilience and scaling strategies").

Include natural synonyms users would actually say (e.g. "API design", "microservices", "backend services") to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The phrase "Expert backend architect specializing in scalable API design, microservices architecture, and distributed systems" names the domain and areas of expertise but uses no concrete verbs/actions (e.g. "Design", "Define service boundaries"), matching the level-2 anchor where the domain is named but actions are minimal or generic.	2 / 5
Completeness	It gives a clear "what" (a backend architect's specialization) but contains no "Use when..." trigger clause, so per the judging guideline completeness is capped at 3, matching the anchor for a clear "what" with "when" missing or only weakly implied.	3 / 5
Trigger Term Quality	Terms like "backend architect", "scalable API design", "microservices architecture", and "distributed systems" are relevant and somewhat natural, but common variations a user would actually say (e.g. "design an API", "microservices") are missing, fitting the level-3 anchor of some relevant keywords with missing synonyms.	3 / 5
Distinctiveness Conflict Risk	"Backend architect" carves a clear niche that is mostly distinct, with only minor overlap risk against closely related skills (cloud-architect, database-architect), matching the level-4 anchor.	4 / 5
	Total	12 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/backend-architect/SKILL.md
Commit: 1f67c44

Reviewed: about 22 hours 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.