CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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 when creating new backend services or APIs.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/backend-architect/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

35%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 body reads as a persona résumé rather than an operational skill: it catalogs capabilities Claude already possesses instead of adding skill-specific knowledge, and its instructions remain abstract checklists without templates or examples. Structure and step sequencing are clear, but token efficiency and actionability are low, and everything lives inline in one large file with no progressive disclosure.

Suggestions

Delete or drastically cut the Capabilities and Knowledge Base sections — Claude already knows what circuit breakers, OAuth 2.0, and Kubernetes are — and keep only skill-specific guidance such as the workflow, deliverable expectations, and sibling-skill boundaries.

Replace abstract instructions with concrete, copy-paste-ready artifacts: a minimal OpenAPI contract skeleton, an ADR template, and a Mermaid service-diagram example matching the promised outputs.

Merge the duplicative Instructions / Response Approach / Purpose sections into one workflow, and move any retained detailed checklists into one-level-deep reference files (e.g. references/deliverables.md).

DimensionReasoningScore

Conciseness

Roughly 200 lines of the Capabilities section catalog concepts Claude already knows ("**Circuit breaker**: Hystrix, resilience4j, failure detection", "**OAuth 2.0**: Authorization flows, grant types, token management", "**Containerization**: Docker, container images, multi-stage builds"), and the Knowledge Base, Purpose, and Behavioral Traits sections restate the same material. The terse bullet format avoids prose padding (keeping it above anchor 1), but the volume of redundant, already-known content is extensive across many padded sections.

2 / 5

Actionability

Guidance is high-level — "Choose architecture patterns and integration mechanisms", "Define service boundaries and API contracts" — with no templates, code, commands, or worked examples showing how to execute any step. The "Output Examples" deliverable list ("API contracts (OpenAPI/GraphQL schemas) with example requests/responses", "Service architecture diagram (Mermaid)") is the most concrete element but stops short of specifics, placing it above entirely-vague anchor 1 but squarely in anchor 2's "high-level hints but missing the specific steps to execute".

2 / 5

Workflow Clarity

The "Response Approach" section provides a clear 10-step sequence ("1. Understand requirements ... 3. Design API contracts ... 10. Document architecture") that is well defined, but there are no validation checkpoints or feedback loops, and it competes with a duplicative 4-step "Instructions" list. This matches anchor 3's "steps listed but validation gaps" — not anchor 2 (steps are defined, not rough) and not anchor 4 (checkpoints are entirely absent).

3 / 5

Progressive Disclosure

The body is well organized with clear section headers, but it is a monolithic 320-line file: the ~200-line capability catalog and Knowledge Base are inline content that clearly belongs in separate reference files, and no bundle files (references/, scripts/, assets/) exist to offload detail. This matches anchor 3's "content that should be separate is inline" while the good header structure keeps it above anchor 2's minimal-structure example.

3 / 5

Total

10

/

20

Passed

Description

75%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 is well-formed: third-person, explicit about capabilities, with a clear "Use when creating new backend services or APIs" trigger clause. Its main weaknesses are mild buzzword padding ("Expert", "Masters ... modern backend frameworks"), a trigger clause that covers only greenfield creation rather than the fuller set of use cases, and some keyword overlap territory (resilience, observability) shared with sibling architect skills.

Suggestions

Broaden the "Use when..." clause to cover additional natural triggers, e.g. "Use when creating new backend services or APIs, defining service boundaries or data contracts, or planning resilience and observability for backend systems."

Trim over-claim buzzwords ("Expert", "Masters", "modern backend frameworks") in favor of plain concrete verbs like "Designs ... Defines ... Plans".

DimensionReasoningScore

Specificity

"Handles service boundary definition, inter-service communication, resilience patterns, and observability" and "Masters REST/GraphQL/gRPC APIs, event-driven architectures, service mesh patterns" list several concrete capability areas, going well beyond anchor 3's 1-2 actions. Buzzword framing ("Expert", "Masters ... modern backend frameworks") and slightly generic terms ("scalable API design") keep it below anchor 5's clean, comprehensive action list.

4 / 5

Completeness

Both parts are explicit: the "what" ("specializing in scalable API design, microservices architecture, and distributed systems ... Handles service boundary definition, inter-service communication") and the "when" ("Use when creating new backend services or APIs"). The trigger clause is narrower than anchor 5 — it omits redesign, integration, and resilience-planning triggers — but is explicit rather than merely implied, so it clears anchor 3.

4 / 5

Trigger Term Quality

"backend services", "APIs", "microservices architecture", "distributed systems", "REST/GraphQL/gRPC", and "event-driven" are terms users would naturally say when needing this skill, giving good keyword coverage. It falls short of anchor 5 because common synonyms and variations like "server-side", "web services", or "monolith-to-microservices migration" are missing, but it far exceeds anchor 3's single-keyword coverage.

4 / 5

Distinctiveness Conflict Risk

The core niche — "service boundary definition, inter-service communication" and API design for "backend services" — is distinct, matching anchor 4's "mostly distinct; minor overlap risk with closely related skills". Overlap remains with sibling architect skills via "resilience patterns, and observability" and "distributed systems", which keeps it below anchor 5, while it is more clearly niched than anchor 3's generic overlap.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

rmyndharis/antigravity-skills

Path

skills/backend-architect/SKILL.md

Reviewed

Table of Contents

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.