ClawTrust
9.0
/ 10
1 evaluations
2.6k Downloads
Overview
Provides a senior API architect persona to design or review REST and GraphQL APIs, producing resource models, endpoint designs, and OpenAPI 3.1 specifications with best-practice patterns for versioning, pagination, errors, and auth.
Key Advantages
1.Strong, opinionated guidance aligned with modern REST and GraphQL best practices (HTTP semantics, resource-oriented URIs, HATEOAS awareness).
2.Built-in focus on OpenAPI 3.1 with explicit expectation to output full specifications (YAML/JSON) and examples.
3.Clear constraints and checklists (MUST/MUST NOT) that reduce common API design mistakes such as verb-based URIs, missing pagination, or weak error semantics.
4.Covers full lifecycle of API design: resource modeling, endpoint design, versioning, pagination, error catalog, and auth documentation.
5.Includes reference topics (REST patterns, versioning, pagination, error handling, OpenAPI) that help maintain depth and consistency across different API scenarios.
Use Cases
- Designing a new REST API from scratch, including resources, relationships, and endpoint structure.
- Creating or refining an OpenAPI 3.1 specification for an existing or planned API.
- Standardizing error handling using RFC 7807-style problem details and consistent status codes.
- Planning API versioning, deprecation policies, and backward compatibility strategies for evolving services.
- Defining pagination and filtering strategies (cursor, offset, keyset) for collection endpoints in large datasets.
Evaluation Scores
9.0
/ 10
Reliability
8.8
Functionality
9.2
Usability
9.0
Safety
9.3
Performance
8.5
Compatibility
9.0
Based on 1 evaluation · Latest: 3/19/2026
Download Trend
Loading...
Evaluation History (1)
9.0/103/19/2026▼
OS: linux-x64LLM: x-ai/grok-4.1-fast
**Quick judgment:** High-quality, specialized skill for API design work. It is well-scoped, opinionated, and grounded in widely-accepted standards for REST, GraphQL, and OpenAPI 3.1.
**Strengths:**
- Emulates a senior API architect with explicit workflows (analyze domain → model resources → design endpoints → specify contract → plan evolution).
- Strong emphasis on correctness details: HTTP semantics, resource naming, pagination, versioning, authentication, and RFC 7807-style error responses.
- Explicit MUST/MUST-NOT rules significantly reduce the chance of producing poor or inconsistent API designs.
**Risks / Limitations:**
- Focuses on design and specification, not on low-level implementation trade-offs (e.g., specific backend frameworks, database constraints) beyond generic best practices.
- Strong REST bias may be less optimal for highly specialized GraphQL-only domains unless combined with more GraphQL-centric skills.
**Best used when:**
- You need to design or refine an API contract, structure, and documentation before implementation.
- Producing or reviewing OpenAPI 3.1 specs, error catalogs, and versioning strategies for services expected to be consumed by external developers.
- Standardizing API practices across a team or organization to improve consistency and developer experience.
Comments (0)
No comments yet. Be the first!