api-recon-and-docs — Claude Code skill: what it does, how to install
A playbook skill for mapping REST, mobile, and GraphQL API surfaces. It finds hidden routes, OpenAPI schemas, and legacy version drift before testing.
npx skills add yaklang/hack-skills --skill api-recon-and-docs -a claude-codeWhat api-recon-and-docs does
The skill guides the agent through an API mapping checklist. It inspects standard specification paths such as /swagger.json, /openapi.json, and /.well-known/. It also extracts candidate endpoints directly from client-side JavaScript files using regular expressions.
During review, the skill looks for undocumented parameters, admin-only request samples, and deprecated routes like /legacy/ or /api/v1/. It flags schema clues like additionalProperties: true. This approach spots forgotten endpoints that bypass modern controls.
Next steps depend directly on the recon results. If object IDs appear across endpoints, the skill directs the agent toward BOLA checks. If JWT or OAuth claims surface, it hands off to authorization workflows.
What it helps with
- discover reachable REST and GraphQL endpoints
- locate exposed OpenAPI and Swagger specifications
- extract undocumented parameters and deprecated routes
- detect API version drift and mobile paths
Example prompts for the agent
- Audit the API surface and find any exposed OpenAPI or Swagger schemas.
- Extract undocumented parameters and legacy endpoints from our app bundle.
- Enumerate GraphQL and mobile API routes on the target service.
How to install api-recon-and-docs
1Skills CLI (Vercel)
npx skills add yaklang/hack-skills --skill api-recon-and-docs -a claude-code2Manually: put the files in place
~/.claude/skills/api-recon-and-docs/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/api-recon-and-docs/
1Skills CLI (Vercel)
npx skills add yaklang/hack-skills --skill api-recon-and-docs -a codex2Manually: put the files in place
.agents/skills/api-recon-and-docs/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add yaklang/hack-skills --skill api-recon-and-docs -a cursor2Manually: put the files in place
.cursor/skills/api-recon-and-docs/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install yaklang/hack-skills api-recon-and-docs2Manually: put the files in place
.github/skills/api-recon-and-docs/SKILL.md1Skills CLI (Vercel)
npx skills add yaklang/hack-skills --skill api-recon-and-docs -a gemini-cli2Platform CLI
gemini skills install https://github.com/yaklang/hack-skills --path skills/api-recon-and-docsManually: put the files in place
.devin/skills/api-recon-and-docs/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add yaklang/hack-skills --skill api-recon-and-docs -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about api-recon-and-docs
How to install api-recon-and-docs in Claude Code?
Run npx skills add yaklang/hack-skills --skill api-recon-and-docs -a claude-code in your terminal. The file is placed in ~/.claude/skills/api-recon-and-docs/SKILL.md.
What does api-recon-and-docs do?
It provides a checklist to discover endpoints, versions, and schemas across REST and GraphQL services. The skill highlights hidden fields and drift across legacy or mobile routes.
How does api-recon-and-docs route findings to other skills?
It maps discoveries to follow-up playbooks. Object IDs trigger BOLA audits, while token claims route directly to JWT and authorization testing.
Source text
SKILL.md · MIT
--- name: api-recon-and-docs description: >- API reconnaissance and documentation review playbook. Use when discovering endpoints, schemas, versions, OpenAPI specs, hidden docs, and surface area for API testing. --- # SKILL: API Recon and Docs — Endpoints, Schemas, and Version Surface > **AI LOAD INSTRUCTION**: Use this skill first when the target is a REST, mobile, or GraphQL API and you need to enumerate endpoints, documentation, versions, and hidden surface area before exploitation. ## 1. PRIMARY GOALS 1. Discover all reachable API entrypoints. 2. Extract schemas, optional fields, and role differences. 3. Identify old versions, mobile paths, GraphQL endpoints, and undocumented parameters. ## 2. RECON CHECKLIST ### JavaScript and client mining ```bash curl https://target/app.js | grep -oE '(/api|/rest|/graphql)[^"'\'' ]+' | sort -u ``` ### Common documentation and schema paths ```text /swagger.json /openapi.json /api-docs /docs /.well-known/ /graphql /gql ``` ### Version and product drift ```text /api/v1/ /api/v2/ /api/mobile/v1/ /legacy/ ``` ## 3. WHAT TO EXTRACT FROM DOCS - optional and undocumented fields - admin-only request examples - deprecated endpoints that may still be active - schema hints like `additionalProperties: true` - parameter names tied to filtering, sorting, IDs, roles, or tenancy ## 4. NEXT ROUTING | Finding | Next Skill | |---|---| | object IDs everywhere | [api authorization and bola](../api-authorization-and-bola/SKILL.md) | | JWT, OAuth, role claims | [api auth and jwt abuse](../api-auth-and-jwt-abuse/SKILL.md) | | GraphQL or hidden fields | [graphql and hidden parameters](../graphql-and-hidden-parameters/SKILL.md) | | strong auth boundary but suspicious business flow | [business logic vulnerabilities](../business-logic-vulnerabilities/SKILL.md) |
© yaklang · MIT · yaklang/hack-skills