How do I install the API Test Bruno skill?

Run npx skillmds add naodeng/api-test-bruno in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is API Test Bruno safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with API Test Bruno?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is API Test Bruno free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published API Test Bruno?

naodeng (@naodeng) published this skill. Their other Agent Skills are listed on their SkillMD profile.

API Test Bruno by naodeng — Agent Skill

Name: API Test Bruno
Rating: 4.666666666666667 (3 reviews)
Author: naodeng

File contents

api-test-bruno (EN)

Chinese version： See the corresponding Chinese skill.

When to Use

Need API outputs that should land in Bruno structure or Bruno workflow.
The project already uses Bruno or wants Bruno-ready organization.

Workflow

Read and follow the main prompt listed under Progressive disclosure (coverage, structure, quality bar).
Add only project context that changes the result: scope, environment, constraints, risks, dependencies, expected deliverable.
If input is incomplete, return a usable first draft and explicitly mark assumptions and gaps.
Default to Markdown; switch formats only when the user asks.

Core Constraints

Prioritize by risk / business impact — do not treat everything equally.
Separate confirmed facts from current assumptions.
Do not invent endpoints, fields, environments, or root causes the user did not provide.
Use placeholders or env-var semantics for auth/secrets; never hardcode real credentials.
Keep output executable: concrete scenarios, clear priority, clear next steps.

Progressive Disclosure

Before producing output, read and follow prompts/api-test-bruno.md (minimum coverage, output structure, quality bar).
When a ready-made template fits: use matching files under output-templates/.
When the user wants examples or alignment with existing assets: read relevant examples/.
For deep framework/troubleshoot/schema notes: read only the relevant file(s) under references/, do not load the whole directory.
For format conversion or helper checks: prefer existing scripts/ over reinventing.
For evaluating/regressing this skill: use evals/ with skill-up.

Pre-delivery Checklist

Followed the main prompt's output structure
Minimum coverage focus: collection structure, environment setup, auth handling, priority endpoints, positive scenarios, negative and boundary scenarios, data or variable strategy, assertion focus, ... (details in main prompt)
Covered the minimum checklist, or explained omissions
High-risk items have explicit priority
Did not invent details the user did not provide
Assumptions and gaps are marked

Common Pitfalls

Do not pretend completeness when scope/context is missing.
Do not treat every item as equally important.
Do not skip assumptions and information gaps.
Do not dump generic theory unrelated to the current toolchain.

---name: api-test-brunodescription: Use this skill when you need to parse multi-format API definitions and generate Bruno collections for executable regression; triggers include Bruno collections and Bruno API testing.--- # api-test-bruno (EN) **Chinese version：** See the corresponding Chinese skill. ## When to Use - Need API outputs that should land in Bruno structure or Bruno workflow. - The project already uses Bruno or wants Bruno-ready organization. ## Workflow 1. Read and follow the main prompt listed under Progressive disclosure (coverage, structure, quality bar). 2. Add only project context that changes the result: scope, environment, constraints, risks, dependencies, expected deliverable. 3. If input is incomplete, return a usable first draft and explicitly mark assumptions and gaps. 4. Default to Markdown; switch formats only when the user asks. ## Core Constraints - Prioritize by risk / business impact — do not treat everything equally. - Separate confirmed facts from current assumptions. - Do not invent endpoints, fields, environments, or root causes the user did not provide. - Use placeholders or env-var semantics for auth/secrets; never hardcode real credentials. - Keep output executable: concrete scenarios, clear priority, clear next steps. ## Progressive Disclosure - Before producing output, read and follow `prompts/api-test-bruno.md` (minimum coverage, output structure, quality bar). - When a ready-made template fits: use matching files under `output-templates/`. - When the user wants examples or alignment with existing assets: read relevant `examples/`. - For deep framework/troubleshoot/schema notes: read only the relevant file(s) under `references/`, do not load the whole directory. - For format conversion or helper checks: prefer existing `scripts/` over reinventing. - For evaluating/regressing this skill: use `evals/` with skill-up. ## Pre-delivery Checklist - [ ] Followed the main prompt's output structure - [ ] Minimum coverage focus: collection structure, environment setup, auth handling, priority endpoints, positive scenarios, negative and boundary scenarios, data or variable strategy, assertion focus, ... (details in main prompt) - [ ] Covered the minimum checklist, or explained omissions - [ ] High-risk items have explicit priority - [ ] Did not invent details the user did not provide - [ ] Assumptions and gaps are marked ## Common Pitfalls - Do not pretend completeness when scope/context is missing. - Do not treat every item as equally important. - Do not skip assumptions and information gaps. - Do not dump generic theory unrelated to the current toolchain.

Frequently asked questions