ClaudeSuperPower

api-discovery

Skill

Guide for agents to help users extract OpenAPI specs from source code using NightVision API Discovery. Use when running swagger extract, identifying framework support, troubleshooting extraction, handling unresolved variables, comparing API specs, or understanding Code Traceback.

Install

git clone https://github.com/nvsecurity/nightvision-skills.git ~/.claude/skills/api-discovery

What is api-discovery?

Guide for agents to help users extract OpenAPI specs from source code using NightVision API Discovery. Use when running swagger extract, identifying framework support, troubleshooting extraction, handling unresolved variables, comparing API specs, or understanding Code Traceback.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Run shell commands

Declares Bash

~70 tokens of context used while enabled, before you invoke anything

All declared tools (1)
Bash

Documentation

README · ~5 min read

NightVision API Discovery

Use this skill when helping users generate OpenAPI specifications from their source code using nightvision swagger extract. API Discovery performs static analysis — no running application or compilation needed — and annotates the spec with source file paths and line numbers (Code Traceback) so that vulnerabilities found during DAST scans trace back to exact code locations.

Agent workflow

When a user asks to extract or document their API:

  1. Check prerequisites — verify the NightVision CLI is available (nightvision --help)
  2. Examine the repo — identify the backend language and web framework to determine the --lang flag and whether the framework is supported (see references/framework-support.md)
  3. Run extraction — execute nightvision swagger extract with the appropriate flags. On success, the CLI prints "Swagger file extracted successfully." and writes the spec to the output path (default: openapi-spec.yml)
  4. Review the output — read the generated spec to check completeness. Handle unresolved variables if nv.config was created alongside the spec
  5. Compare coverage — if the user has an existing spec, run nightvision swagger diff to show what was discovered vs. what was documented
  6. Upload to target — attach the spec to a NightVision target for scanning

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.