api-documenter

Master API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals. Use PROACTIVELY for API documentation or developer portal creation.

Quality

57%

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 ./skills/api-documenter/SKILL.md

Quality

Content

31%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 persona-style enumeration of capabilities and traits that restates widely-known API documentation concepts without providing concrete, executable guidance. It lacks progressive disclosure and would benefit from being trimmed and pointed at separate reference materials.

Suggestions

Replace the long capability/trait/knowledge bullet catalogs with concise guidance and move the detailed taxonomies into reference files under references/ (e.g., capabilities.md, tools.md) linked from the body to fix progressive disclosure.

Add concrete, actionable steps or templates — e.g., a minimal OpenAPI 3.1 skeleton, a specific validation command (spectral lint), or an SDK generation command (openapi-generator) — so Claude knows exactly what to run rather than being told to 'create specifications'.

Tighten the body to assume Claude's competence: cut the 'Knowledge Base' and 'Behavioral Traits' sections that restate known concepts (OAuth, JWT, CORS) and keep only non-obvious workflow specifics.

Dimension	Reasoning	Score
Conciseness	The ~175-line body is padded with long capability catalogs ("Modern Documentation Standards", "AI-Powered Documentation Tools", "Knowledge Base") that restate domain taxonomy Claude already knows (OpenAPI 3.1, OAuth 2.0, JWT, CORS), making it noticeably verbose.	2 / 5
Actionability	Guidance is high-level hints only — "Create or validate specifications with examples and auth flows", "Build interactive docs and ensure accuracy with tests" — with no specific tools, commands, templates, or concrete steps, so it offers minimal executable direction.	2 / 5
Workflow Clarity	A rough sequence exists (4 "Instructions" steps and 8 "Response Approach" steps), but validation is only implicit ("ensure accuracy with tests") with no explicit checkpoints or feedback loops for spec validation or SDK generation.	3 / 5
Progressive Disclosure	No bundle files exist and the body inlines large capability catalogs that clearly belong in separate reference files; section headers provide some structure but there are no one-level-deep references to split the bulk content.	2 / 5
	Total	9 / 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, third-person description that covers both what the skill does and when to use it with explicit PROACTIVELY trigger guidance. It is concrete and distinguishable, with only minor gaps in keyword breadth and action comprehensiveness.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — "Create interactive docs, generate SDKs, and build comprehensive developer portals" plus "Master API documentation with OpenAPI 3.1" — but the coverage is broad rather than comprehensive, so it sits at 4 not 5.	4 / 5
Completeness	Explicitly states what it does and includes an explicit trigger clause ("Use PROACTIVELY for API documentation or developer portal creation") with concrete trigger phrases, satisfying the what+when requirement.	5 / 5
Trigger Term Quality	Good natural keywords a user would say ("API documentation", "developer portal", "SDKs", "OpenAPI 3.1", "interactive docs"); a few common synonyms/extensions (Swagger, AsyncAPI, .yaml) are absent, so not a 5.	4 / 5
Distinctiveness Conflict Risk	Clear niche (API docs / developer portals with OpenAPI 3.1 and SDKs) that is mostly distinct from other skills, with only minor overlap risk against a generic documentation skill; not narrow enough for a 5.	4 / 5
	Total	17 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/api-documenter/SKILL.md
Commit: 3eff4af

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.