moai-domain-backend

Backend development specialist covering API design, database integration, microservices architecture, and modern backend patterns. Use when designing APIs, implementing server logic, authentication, or authorization.

Quality

63%

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 ./.claude/skills/moai-domain-backend/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 body is a well-sectioned pattern catalog, but it relies on prose descriptions instead of executable code, duplicates frontmatter content in a Quick Reference section, carries time-sensitive version numbers, and links to a missing examples.md file. These issues drag down actionability and conciseness despite decent organization.

Suggestions

Replace the prose code recipes in the Implementation Guide and Advanced Patterns with executable code blocks (e.g. an actual Pydantic UserResponse class and a FastAPI endpoint), so guidance is copy-paste ready rather than described.

Remove the redundant Quick Reference section (it restates the frontmatter) and drop or relocate the time-sensitive version numbers in Technology Stack to a separate, clearly-marked reference file.

Fix the broken examples.md reference by either providing the file or removing the link, and move the bulk pattern catalog / technology stack into one-level-deep reference files with clearly signaled links.

Dimension	Reasoning	Score
Conciseness	Several padded/redundant sections are present: the Quick Reference restates the frontmatter capabilities, the Technology Stack carries time-sensitive version numbers (Python 3.13+, PostgreSQL 16+) outside any deprecated section, and implementation recipes are written as prose ("Define a Pydantic UserResponse model with id, email, and name fields") rather than compact code.	2 / 5
Actionability	The recipes give concrete specifics (field names, parameters, library calls like "Strawberry to define GraphQL types"), but the body contains zero executable code blocks, leaving guidance as prose rather than copy-paste-ready code; examples.md is referenced for code but does not exist.	3 / 5
Workflow Clarity	A standalone Verification checklist exists, but the implementation patterns are presented as isolated recipes with no sequenced workflow, and the database/API patterns lack integrated validation checkpoints or feedback loops; per the rubric cap, destructive/batch operations without inline validation cannot exceed 3.	3 / 5
Progressive Disclosure	Section headers give reasonable structure, but reference-style content (the full pattern catalog, Technology Stack) is inlined in SKILL.md and the single outbound reference ("see examples.md") points to a file that is not present in the bundle.	3 / 5
	Total	11 / 20 Passed

Description

83%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 description that clearly answers both what the skill does and when to use it, with concrete trigger phrases and good keyword coverage. The main weaknesses are the generic "modern backend patterns" phrase and modest overlap risk with adjacent database/security domain skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete capabilities ("API design, database integration, microservices architecture") and actions ("designing APIs, implementing server logic, authentication, or authorization"), but the trailing phrase "modern backend patterns" is generic padding that keeps it just short of comprehensive.	4 / 5
Completeness	It explicitly states both what ("Backend development specialist covering API design, database integration, microservices architecture...") and when ("Use when designing APIs, implementing server logic, authentication, or authorization") with concrete trigger phrases, matching the score-5 anchor structure.	5 / 5
Trigger Term Quality	Good coverage of natural terms a backend developer would say ("API design", "microservices", "authentication", "authorization", "server logic"), but it lacks common synonyms (e.g. "REST", "backend", "web server") and framework names that would push it to comprehensive.	4 / 5
Distinctiveness Conflict Risk	The "backend development specialist" niche with API/microservices/auth triggers is mostly distinct, but "database integration" and "authentication/authorization" overlap with sibling domain skills (database, security), creating minor conflict risk rather than minimal.	4 / 5
	Total	17 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
relative_links	Relative link issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: modu-ai/moai-adk
Path: .claude/skills/moai-domain-backend/SKILL.md
Commit: 4100d87

Reviewed: 2 days 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.