Agent skill · Security

bruno-api

Generate comprehensive API endpoint documentation from Bruno (.bru) files by mapping requests to a Django4Lyfe/Diversio-style backend implementation (Django REST Framework or Django Ninja), including auth/permissions, multi-tenant filtering, request/response schemas, and line-numbered code references. Use for single endpoints, directory scans of .bru files, or when writing docs to a specific output path.

majiayu000github.com/majiayu000GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill bruno-api --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 6 KB
Bundled scripts: none
Allowed tools: -Bash-Read-Edit-Glob-Grep
Path: skills/api/bruno-api/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Bruno API Documentation Generator Skill ## Inputs & Modes This Skill expects one of: - A path to a single Bruno file (usually `*.bru`), OR - `--scan <dir>` to analyze all `.bru` files under a directory. Optional flags: - `--dry-run` – produce an analysis plan only (no deep codebase search). - `--output <path>` – write the generated markdown documentation to a file. If inputs are missing or ambiguous, ask the user to confirm: - Which `.bru` file(s) to analyze. - Whether they want `--dry-run` or full documentation. - Whether an output file should be written. ## Output Shape & Severity Tags ### Dry-run output Return a short plan containing: - Endpoint summary: method, URL, auth, and any detected params/body. - Where you will look in the Django codebase (specific file paths/directories). - Which documentation sections will be generated. - Complexity notes (e.g., “DRF ViewSet + serializer” vs “Ninja router + schema”). ### Full documentation output Generate a single markdown document for each endpoint using this structure: - `# <Endpoint Name>` - ``<METHOD> <URL Pattern>`` - **Authentication**, **Permissions**, **Multi-tenant** - `## Overview` - `## Request` (headers + params/body with

What's inside
Steps it walks through
  1. Inputs & Modes
  2. Output Shape & Severity Tags
  3. Dry-run output
  4. Full documentation output
  5. Workflow
  6. Step 1 — Parse the Bruno file(s)
  7. Step 2 — Locate the Django route & implementation
  8. Step 3 — Extract behavior and contracts
  9. Step 4 — Generate documentation
  10. Step 5 — Handle --output and --scan
  11. Compatibility Notes
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the bruno-api skill do?

Generate comprehensive API endpoint documentation from Bruno (.bru) files by mapping requests to a Django4Lyfe/Diversio-style backend implementation (Django REST Framework or Django Ninja), including auth/permissions, multi-tenant filtering, request/response schemas, and line-numbered code references. Use for single endpoints, directory scans of .bru files, or when writing docs to a specific output path.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill bruno-api --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.

Keep going