backend-architect

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

1.17x

Quality

45%

Does it follow best practices?

Impact

89%

1.17x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/backend-architect/SKILL.md

The canonical home for this skill is backend-architect in rmyndharis/antigravity-skills

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.

A well-structured persona skill with a clear sequenced workflow and explicit output expectations, but it is heavily padded with a capability/technology catalog that largely duplicates Claude's existing knowledge and provides no validation checkpoints or reference files to offload detail.

Suggestions

Move the exhaustive Capabilities catalog into a one-level-deep reference file (e.g. references/capabilities.md) and keep SKILL.md as a lean overview that points to it, reducing token load.

Trim technology name-drops ('Hystrix, resilience4j', 'Kong, Ambassador, AWS API Gateway') that Claude already knows, keeping only the actionable selection guidance.

Add explicit validation/review checkpoints to the Response Approach workflow (e.g. 'Validate the API contract against consumer needs before finalizing boundaries'), especially before destructive or hard-to-reverse architectural decisions.

Dimension	Reasoning	Score
Conciseness	The ~320-line body is a large catalog of capabilities and technology lists (REST, OAuth, circuit breakers, etc.) that largely restates knowledge Claude already has; it is noticeably verbose and padded despite being organized as bullet lists rather than prose.	2 / 5
Actionability	The 'Response Approach' (10 steps) and 'Output Examples' give some concrete deliverable guidance, but most steps are high-level ('Design API contracts: REST/GraphQL/gRPC') and describe rather than prescribe executable methodology, with no code or concrete artifacts.	3 / 5
Workflow Clarity	A clear sequenced workflow exists ('Response Approach' steps 1–10 plus 'Instructions'), but there are no validation checkpoints or feedback loops anywhere, so the sequence has explicit gaps.	3 / 5
Progressive Disclosure	Section headers give reasonable structure, but no bundle/reference files exist and the large Capabilities catalog (~150 lines of inline bullets) is inlined in SKILL.md rather than offloaded to a one-level-deep reference.	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.

A concise persona statement that is distinct and domain-specific, but it is missing the explicit 'Use when…' trigger guidance and concrete action verbs, leaving 'what' clear while 'when' is absent.

Suggestions

Add an explicit 'Use when…' trigger clause, e.g. 'Use when designing new backend services/APIs, defining service boundaries and data contracts, or planning resilience, scaling, and observability.'

Rewrite around concrete actions rather than a persona ('Designs scalable APIs, defines microservice boundaries and inter-service contracts, plans resilience and observability') to raise specificity.

Include natural user phrases and synonyms (e.g. 'API design, microservices, service boundaries, distributed systems, event-driven architecture') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('backend architect') and three specialization areas ('scalable API design, microservices architecture, and distributed systems') but lists no concrete actions — it reads as a persona ('specializing in…') rather than activity verbs ('designs APIs, defines service boundaries').	2 / 5
Completeness	It states clearly 'what' the skill is (an expert backend architect), but provides no 'when' guidance — no 'Use when…' or equivalent explicit trigger — which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	'API design', 'microservices architecture', and 'distributed systems' are relevant keywords a user might say, but common variations/synonyms and natural trigger phrasing are missing, and there is no 'Use when…' cue.	3 / 5
Distinctiveness Conflict Risk	The backend-architecture framing is a fairly distinct niche with only minor overlap risk against closely related skills (cloud-architect, database-architect, security-auditor).	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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/backend-architect/SKILL.md
Commit: 57c135b

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