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.

1.00x

Quality

22%

Does it follow best practices?

Impact

100%

1.00x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/antigravity-api-documenter/SKILL.md

Quality

Discovery

32%

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 identifies a clear domain (API documentation with OpenAPI) and lists several concrete outputs, but suffers from missing trigger guidance and some vague language ('Master', 'AI-powered tools'). The lack of a 'Use when...' clause significantly weakens Claude's ability to select this skill appropriately from a large skill set.

Suggestions

Add an explicit 'Use when...' clause with trigger terms like 'OpenAPI', 'swagger', 'API spec', 'REST documentation', or when users mention generating client libraries.

Replace vague terms like 'Master' and 'AI-powered tools' with specific actions such as 'validate OpenAPI specs', 'generate API reference pages', or 'create code samples'.

Include common file extensions and variations users might mention: '.yaml', '.json', 'swagger.json', 'openapi.yaml'.

Dimension	Reasoning	Score
Specificity	Names the domain (API documentation, OpenAPI 3.1) and lists some actions (create interactive docs, generate SDKs, build developer portals), but uses vague terms like 'Master' and 'AI-powered tools' without explaining concrete capabilities.	2 / 3
Completeness	Describes what it does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no trigger guidance at all.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'OpenAPI 3.1', 'API documentation', 'SDKs', 'developer portals', but missing common variations users might say like 'swagger', 'API spec', 'REST docs', or file extensions like '.yaml', '.json'.	2 / 3
Distinctiveness Conflict Risk	OpenAPI 3.1 and SDK generation provide some distinctiveness, but 'API documentation' and 'developer experience practices' are broad enough to potentially overlap with general documentation or coding skills.	2 / 3
	Total	7 / 12 Passed

Implementation

12%

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

This skill reads as a comprehensive capability description rather than actionable documentation. It extensively lists what an API documentation specialist should know and do, but provides zero concrete examples, code snippets, or executable commands. The content would benefit from dramatic reduction and replacement of abstract descriptions with actual OpenAPI snippets, tool commands, and working examples.

Suggestions

Replace the abstract capability lists with 2-3 concrete, executable examples (e.g., a minimal OpenAPI 3.1 spec snippet, a command to generate SDKs with a specific tool)

Remove the 'Capabilities', 'Knowledge Base', and 'Behavioral Traits' sections entirely - these describe what Claude already knows and add no operational value

Add specific tool commands and validation steps (e.g., 'Validate spec: npx @redocly/cli lint openapi.yaml')

Split detailed content into referenced files (e.g., OPENAPI_EXAMPLES.md, SDK_GENERATION.md) and keep SKILL.md as a concise overview

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive lists of capabilities, knowledge bases, and behavioral traits that Claude already knows. The content reads like a job description rather than actionable instructions, with significant padding that doesn't add operational value.	1 / 3
Actionability	No concrete code examples, commands, or executable guidance anywhere. The entire skill describes what to do abstractly ('Create comprehensive specifications', 'Build interactive experiences') without showing how to actually do any of it.	1 / 3
Workflow Clarity	The 'Instructions' and 'Response Approach' sections provide numbered steps, but they are high-level and lack validation checkpoints. No feedback loops or error recovery guidance for complex operations like SDK generation or spec validation.	2 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files for detailed content. All the capability lists, knowledge bases, and examples are inline when they could be split into focused reference documents.	1 / 3
	Total	5 / 12 Passed

Validation

90%

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 — 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

Repository: boisenoise/skills-collections
Commit: 5c5ae21

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