architect

Database and API architecture specialist

Quality

52%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/architect/SKILL.md

Quality

Content

55%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 lean, copy-paste-ready reference of database, API, and microservices examples, but it functions as a static template dump rather than skill guidance: there is no design workflow, no validation/feedback steps, and no progressive disclosure to separate reference files.

Suggestions

Add a short design workflow (e.g., gather requirements → draft schema → define API contracts → split services → validate against constraints) with explicit checkpoints, including validation for database migrations or schema changes.

Move the full SQL DDL, OpenAPI spec, and microservices detail into separate reference files under ./references/ and keep SKILL.md as a concise overview with clearly signaled one-level-deep links.

Add brief guidance on how to adapt the e-commerce examples to a new domain, so the templates are actionable rather than only copy-pasteable.

Dimension	Reasoning	Score
Conciseness	The body is almost entirely executable example code (SQL DDL, OpenAPI YAML, architecture markdown) with no padded explanations of concepts Claude already knows, fitting anchor 4 ('Efficient; minor instances of over-explanation that could be trimmed'). It stops short of 5 because the full OpenAPI spec and complete DDL are lengthy enough that some could be referenced rather than inlined.	4 / 5
Actionability	It provides concrete, copy-paste-ready SQL schemas, an OpenAPI specification, and a microservices breakdown covering a common e-commerce case, matching anchor 4 ('Mostly executable guidance; concrete code or commands with minor gaps'). It is not 5 because there is no guidance on how to adapt or apply these templates to a new problem.	4 / 5
Workflow Clarity	There is no sequenced design process or validation checkpoints — only topical example sections — so for a multi-topic architecture skill it fits anchor 2 ('Rough sequence present but many gaps; steps poorly defined; validation absent') more than anchor 3 which expects at least a clear listed sequence.	2 / 5
Progressive Disclosure	No bundle files exist and ~200 lines of full schema/API/architecture specs are inlined monolithically with only section headers, so content that clearly belongs in separate reference files is inlined, matching anchor 2. It does not reach 3 because there are no references signaled at all and the simple-skill exception does not apply to a 200-line multi-topic skill.	2 / 5
	Total	12 / 20 Passed

Description

28%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 a terse role label that names a domain but provides no concrete actions, no natural trigger terms, and no 'Use when' guidance. It is only marginally better than generic filler and would be hard for a user to invoke confidently.

Suggestions

Replace the role label with concrete actions, e.g., 'Designs relational database schemas, defines REST/OpenAPI endpoints, and sketches microservice boundaries.'

Add an explicit 'Use when...' clause with natural trigger phrases such as 'design a database schema', 'define an API', or 'plan a microservices architecture'.

Include common synonyms and artifacts (SQL DDL, OpenAPI/.yaml, ER diagrams) to improve trigger-term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	The description 'Database and API architecture specialist' names the domain but lists no concrete actions, matching the anchor 'Names the domain but actions are minimal or generic'. It does not reach 3 because no specific actions (e.g., 'designs schemas', 'defines REST endpoints') are stated.	2 / 5
Completeness	It offers only a vague role-label 'what' and entirely omits any 'when'/'Use when' trigger guidance, matching anchor 2 ('Has a vague what and no when'); the missing Use-when clause also caps completeness at 3 per the guidelines.	2 / 5
Trigger Term Quality	Only generic keywords ('Database', 'API', 'architecture') appear with no natural trigger phrases a user would actually say (e.g., 'design a database schema', 'build a REST API'), fitting anchor 2 rather than 3 which expects common variations.	2 / 5
Distinctiveness Conflict Risk	'Database and API architecture' is a somewhat specific niche, but with no trigger phrases it could still overlap with general backend or coding skills, fitting anchor 3 rather than 4 which requires minimal overlap risk.	3 / 5
	Total	9 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: TurnaboutHero/oh-my-antigravity
Path: skills/architect/SKILL.md
Commit: f73e1ff

Reviewed: 15 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.