CtrlK
BlogDocsLog inGet started
Tessl Logo

moai-ref-api-patterns

REST/GraphQL API design patterns, error handling conventions, and input validation reference for backend development. Agent-extending skill that amplifies backend domain work (spawned via Agent(general-purpose) with backend instructions) with production-grade API patterns. Use when designing APIs, implementing endpoints, or reviewing backend code. NOT for: frontend development, DevOps, database schema design, security audits.

72

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and well-structured with a verification checklist, but it is monolithic with no progressive file split and reiterates some elementary HTTP/REST knowledge. Splitting dense reference sections into bundled files would lift progressive disclosure, and trimming boilerplate would improve conciseness.

Suggestions

Move the dense reference tables (REST conventions, HTTP status codes, validation checklist) into a bundled references/ file and keep SKILL.md as a concise overview with one-level-deep links, matching the frontmatter's progressive_disclosure declaration.

Trim the most elementary material Claude already knows — the full HTTP status-code mapping and basic verb-to-method table — to recover token budget for the genuinely valuable conventions (error format, pagination, rate-limit headers, versioning rules).

Verify the claimed bundle structure exists: frontmatter sets progressive_disclosure.enabled=true and level2_tokens=3000, but no references/, scripts/, or assets/ directories are present, so the declared disclosure is not actually realized.

DimensionReasoningScore

Conciseness

Mostly compact tables and JSON payloads, but the HTTP status-code guide and basic REST verb-to-method mapping restate elementary knowledge Claude already has, so it could be tightened by dropping the most boilerplate sections.

2 / 3

Actionability

Provides concrete, copy-paste-ready guidance: specific JSON error/pagination payloads, real rate-limit values (e.g. '5 req/min'), and named headers (X-RateLimit-Reset, Retry-After) and tools (Zod, pydantic).

3 / 3

Workflow Clarity

A reference skill rather than a destructive multi-step process, and it closes with an explicit verification checklist (checkboxes for naming, error format, pagination, versioning, validation) that serves as validation checkpoints.

3 / 3

Progressive Disclosure

Well-organized with clear section headers, but it is a single ~170-line monolithic file with no bundle files and no one-level-deep references; reference content that could be split into a separate file is inline.

2 / 3

Total

10

/

12

Passed

Description

100%

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 specific, trigger-rich, and complete, clearly stating both capabilities and use conditions with third-person voice and an explicit scope-exclusion clause. It is a strong example of a well-scoped reference skill description.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'API design patterns, error handling conventions, and input validation' and 'designing APIs, implementing endpoints, or reviewing backend code' — matching the anchor for naming multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers both what (API design patterns, error handling, validation reference) and when ('Use when designing APIs, implementing endpoints, or reviewing backend code'), with an additional explicit NOT-for clause.

3 / 3

Trigger Term Quality

Includes natural triggers a user would say — 'designing APIs, implementing endpoints, or reviewing backend code' — giving good coverage of verbal trigger terms rather than generic 'works with X' phrasing.

3 / 3

Distinctiveness Conflict Risk

Clear backend API niche reinforced by an explicit exclusion list ('NOT for: frontend development, DevOps, database schema design, security audits'), making conflict with adjacent skills unlikely.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
modu-ai/moai-adk
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.