Database and API architecture specialist
55
Quality
44%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/architect/SKILL.mdQuality
Discovery
N/ABased on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
Something went wrong
Implementation
44%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides excellent concrete examples of database schemas, API specifications, and microservices architecture, making it highly actionable. However, it lacks workflow guidance for how to apply these patterns, when to choose between approaches, and validation steps for architecture decisions. The content would benefit from being restructured as an overview with references to detailed pattern guides.
Suggestions
Add a workflow section explaining the process: requirements analysis → schema design → validation → API design → review checklist
Include decision criteria for when to use different patterns (e.g., when to choose microservices vs monolith, SQL vs NoSQL)
Split detailed examples into separate reference files (e.g., SCHEMAS.md, API-PATTERNS.md, MICROSERVICES.md) and provide a concise overview with navigation
Add validation checkpoints such as 'verify foreign key relationships', 'test API contract with schema validator', 'review for N+1 query risks'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill provides substantial examples but includes more detail than necessary for an architecture specialist skill. The e-commerce example is comprehensive but could be more focused on patterns rather than a complete implementation. | 2 / 3 |
Actionability | Provides fully executable SQL schemas, complete OpenAPI specifications, and concrete architecture patterns. All code is copy-paste ready with proper constraints, indexes, and relationships defined. | 3 / 3 |
Workflow Clarity | No workflow or process guidance is provided. The skill presents static examples without explaining when to use each pattern, how to validate designs, or how to iterate on architecture decisions. | 1 / 3 |
Progressive Disclosure | Monolithic content with no references to external files or clear navigation structure. All content is inline with no indication of where to find more detailed guidance on specific topics like database migrations, API versioning, or service communication patterns. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
fab464f
Table of Contents
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.