analyzing-api-layer
Use when analyzing REST/GraphQL API endpoints, contracts, authentication, and client-facing interfaces
npx skills add majiayu000/claude-skill-registry --skill analyzing-api-layer --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.
# Analyzing API Layer **Output:** `docs/unwind/layers/api/` (folder with index.md + section files) **Principles:** See `analysis-principles.md` - completeness, machine-readable, link to source, no commentary, incremental writes. ## Output Structure ``` docs/unwind/layers/api/ ├── index.md # Endpoint summary table, route count ├── endpoints.md # All controller/route definitions ├── auth.md # Authentication & authorization config ├── contracts.md # OpenAPI/AsyncAPI/TSRest specs [CRITICAL] └── errors.md # Error handling patterns ``` For large codebases (20+ route files), split by domain: ``` docs/unwind/layers/api/ ├── index.md ├── users-api.md ├── orders-api.md └── ... ``` ## Process (Incremental Writes) **Step 1: Setup** ```bash mkdir -p docs/unwind/layers/api/ ``` Write initial `index.md`: ```markdown # API Layer ## Sections - [Endpoints](endpoints.md) - _pending_ - [Authentication](auth.md) - _pending_ - [API Contracts](contracts.md) - _pending_ - [Error Handling](errors.md) - _pending_ ## Endpoint Summary _Analysis in progress..._ ``` **Step 2: Analyze and write contracts.md** [CRITICAL - DO FIRST] 1. Search for OpenAPI, AsyncAPI, TSRest, GraphQL specs 2. Include COMPLETE specs (
- Output Structure
- Process (Incremental Writes)
- Output Format
- Additional Requirements
- API Specification Discovery [CRITICAL - MUST PRESERVE]
- Complete Route Inventory [MUST]
- Missing Documentation Tracking
- External API Contracts [MUST]
- Permission Documentation [MUST]
- Mandatory Tagging
- Refresh Mode
mkdir -p docs/unwind/layers/api/
What does the analyzing-api-layer skill do?
Use when analyzing REST/GraphQL API endpoints, contracts, authentication, and client-facing interfaces
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill analyzing-api-layer --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.