api-spec-analyzer
Analyzes API documentation from OpenAPI specs to provide TypeScript interfaces, request/response formats, and implementation guidance. Use when implementing API integrations, debugging API errors (400, 401, 404), replacing mock APIs, verifying data types, or when user mentions endpoints, API calls, or backend integration.
npx skills add majiayu000/claude-skill-registry --skill api-spec-analyzer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# API Specification Analyzer This Skill analyzes OpenAPI specifications to provide accurate API documentation, TypeScript interfaces, and implementation guidance for the caremaster-tenant-frontend project. ## When to use this Skill Claude should invoke this Skill when: - User is implementing a new API integration - User encounters API errors (400 Bad Request, 401 Unauthorized, 404 Not Found, etc.) - User wants to replace mock API with real backend - User asks about data types, required fields, or API formats - User mentions endpoints like "/api/users" or "/api/tenants" - Before implementing any feature that requires API calls - When debugging type mismatches between frontend and backend ## Instructions ### Step 1: Fetch API Documentation Use the MCP server tools to get the OpenAPI specification: ``` mcp__Tenant_Management_Portal_API__read_project_oas_f4bjy4 ``` If user requests fresh data or if documentation seems outdated: ``` mcp__Tenant_Management_Portal_API__refresh_project_oas_f4bjy4 ``` For referenced schemas (when $ref is used): ``` mcp__Tenant_Management_Portal_API__read_project_oas_ref_resources_f4bjy4 ``` ### Step 2: Analyze the Specification Extract the following informa
- When to use this Skill
- Instructions
- Step 1: Fetch API Documentation
- Step 2: Analyze the Specification
- Step 3: Generate TypeScript Interfaces
- Step 4: Provide Implementation Guidance
- Step 5: Document Security and Validation
- Step 6: Provide Test Recommendations
- Output Format
- Project Conventions
- Path Aliases
- Code Style (Biome)
- File Organization
- Common Patterns
What does the api-spec-analyzer skill do?
Analyzes API documentation from OpenAPI specs to provide TypeScript interfaces, request/response formats, and implementation guidance. Use when implementing API integrations, debugging API errors (400, 401, 404), replacing mock APIs, verifying data types, or when user mentions endpoints, API calls, or backend integration.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill api-spec-analyzer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.