Agent skill

API Test Bruno

by naodeng in naodeng/awesome-qa-skills

A skill your agent uses when you need to parse multi-format API definitions and generate Bruno collections for executable regression; triggers include Bruno collections and Bruno API testing.

Custom licenceAuto-check passedTesting & QA

Install API Test Bruno

skills CLI
$ npx skills add naodeng/awesome-qa-skills --skill api-test-bruno -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install naodeng/awesome-qa-skills api-test-bruno --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/naodeng/awesome-qa-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/en/testing-types/api-test-bruno .claude/skills/api-test-bruno && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
api-test-bruno
GitHub stars
245
Token cost
~663 tokens
SKILL.md length
315 words
Files
43 (incl. scripts, references)
Skills in repo
22
Repo updated
First seen
Licence
Custom licence

At a glance

A skill your agent uses when you need to parse multi-format API definitions and generate Bruno collections for executable regression; triggers include Bruno collections and Bruno API testing.

  • Works in 4 steps: Read and follow the main prompt listed… → Add only project context that changes… → If input is incomplete, return a usable… → …
  • You need to parse multi-format API definitions and generate Bruno collections for executable regression
  • SKILL.md covers When to Use, Workflow, Core Constraints and Progressive Disclosure, plus 2 more sections
  • Runs Shell scripts from its folder

What it does

API Test Bruno is an agent skill from naodeng/awesome-qa-skills. 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.

Its SKILL.md is about 660 tokens, which your agent loads only when the skill is triggered. The skill folder holds 50 other files, including scripts and reference files (for example `README.md`, `agents/openai.yaml` and `evals/cases/basic-success.yaml`).

It sits in Testing & QA, covering API testing. The repository describes itself as: Awesome QA Skills is an open-source AI-native Quality Engineering skill system that helps engineering teams reason about, design, execute, evaluate, and continuously improve…

When your agent uses it

  • You need to parse multi-format API definitions and generate Bruno collections for executable regression
  • Triggers include Bruno collections and Bruno API testing

Example prompts

  • “/api-test-bruno”

Requirements

  • A Bash shell

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  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.

What it can do on your machine

Read from SKILL.md and the folder at commit 52c4eaf. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Shell, from the files we listed), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

API Test Bruno loads about 663 tokens when it runs, and up to ~1.6k if it reads all its reference files. Until then it costs about 49 tokens; SKILL.md has 315 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~49
When it runs · the whole SKILL.md, loaded when a task matches
~663
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 315 words (~663 tokens).

“Chinese version: See the corresponding Chinese skill.”

— opening of SKILL.md by naodeng, Custom licence
name
api-test-bruno

Read the full SKILL.md on GitHub

Files

SKILL.md and 42 other files (scripts, references) in skills/en/testing-types/api-test-bruno of naodeng/awesome-qa-skills.

  • SKILL.md
  • README.md
  • agents/openai.yaml
  • evals/cases/basic-success.yaml
  • evals/cases/edge-bad-or-neighbor.yaml
  • evals/cases/edge-incomplete-input.yaml
  • evals/eval.yaml
  • evals/fixtures/openapi-orders.yaml
  • evals/fixtures/sample-curls.sh
  • evals/fixtures/scripts/check_bruno_output.sh
  • evals/trigger_queries.json
  • examples/bruno/sample.bru
  • examples/ci/Jenkinsfile.bruno
  • … and 30 more

Open the folder on GitHubat commit 52c4eaf

Compare with similar skills

API Test Bruno next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

API Test Bruno compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
API Test Bruno this skillnaodeng/awesome-qa-skills245—~663Automated safety check: PassCustom licence
Diff-Driven QASkyvern-AI/skyvern23k—~4.7kAutomated safety check: WarnAGPL-3.0
AI Regression Testingaffaan-m/ECC275k5 repos~2.9kAutomated safety check: PassMIT
Scout Best Practices Reviewerelastic/kibana21k—~5.1kAutomated safety check: PassCustom licence
API Testing RESTPramodDutta/qaskills232—~4.9kAutomated safety check: PassMIT
API Test Suite Builderalirezarezvani/claude-skills28k1 repos~1.6kAutomated safety check: PassMIT

Similar skills

  • Diff-Driven QA

    Skyvern-AI/skyvern

    Reads your git diff, decides whether the change needs browser QA, API checks or repo tests, runs that validation and reports pass or fail with evidence.

    23k GitHub stars~4.7k tokensUpdated today
    Testing & QAAuto-check: warnings
  • Regression testing strategies for AI-assisted development. An agent skill from affaan-m/ECC.

    275k GitHub starsUsed in 5 repos~2.9k tokens
    Testing & QAAuto-check passed
  • Official

    Review Scout UI/API tests (including Scout test migrations) and Scout reuse surfaces (page objects, UI component objects, API services) for best practices, reuse, correct placement, parity, and…

    21k GitHub stars~5.1k tokensUpdated today
    Testing & QAAuto-check passed
  • API Testing REST

    PramodDutta/qaskills

    Comprehensive RESTful API testing patterns covering HTTP methods, status codes, request/response validation, authentication, error handling, and contract testing.

    232 GitHub stars~4.9k tokensUpdated 4 days ago
    Testing & QAAuto-check passed
  • API Test Suite Builder

    alirezarezvani/claude-skills

    A skill your agent uses when the user asks to generate API tests, create integration test suites, test REST endpoints, or build contract tests.

    28k GitHub starsUsed in 1 repo~1.6k tokens
    Testing & QAAuto-check passed
  • API Testing Observability API Mock

    aiskillstore/marketplace

    You are an API mocking expert specializing in realistic mock services for development, testing, and demos.

    430 GitHub starsUsed in 7 repos~572 tokens
    Testing & QAAuto-check passed

More from naodeng/awesome-qa-skills

All 22 skills in this repo
  • Accessibility Testing

    naodeng/awesome-qa-skills

    A skill your agent uses when you need to design accessibility testing against WCAG, keyboard navigation, and assistive technology scenarios; triggers include accessibility testing and a11y testing.

    245 GitHub stars~665 tokensUpdated 12 days ago
    Auto-check passed
  • API Test Pytest

    naodeng/awesome-qa-skills

    A skill your agent uses when you need to parse multi-format API definitions and generate Pytest API automation; triggers include Pytest API tests and API automation with Pytest.

    245 GitHub stars~655 tokensUpdated 12 days ago
    Auto-check passed
  • API Test Restassure

    naodeng/awesome-qa-skills

    A skill your agent uses when you need to parse multi-format API definitions and generate Rest Assured Java test classes; triggers include Rest Assured, RestAssured, and Java API automation.

    245 GitHub stars~658 tokensUpdated 12 days ago
    Auto-check passed
  • API Test Supertest

    naodeng/awesome-qa-skills

    A skill your agent uses when you need to parse multi-format API definitions and generate executable Supertest scripts; triggers include Supertest, Node.js API testing, and Supertest automation.

    245 GitHub stars~659 tokensUpdated 12 days ago
    Auto-check passed
  • API Testing

    naodeng/awesome-qa-skills

    A skill your agent uses when you need to design API test plans or cases for REST, GraphQL, or gRPC interfaces; triggers include API testing and API test cases.

    245 GitHub stars~636 tokensUpdated 12 days ago
    Auto-check passed
  • Automation Testing

    naodeng/awesome-qa-skills

    A skill your agent uses when you need to design automation testing approaches using patterns like POM, data-driven testing, or BDD; triggers include automation testing and test automation strategy.

    245 GitHub stars~647 tokensUpdated 12 days ago
    Auto-check passed

Categories

Questions about API Test Bruno

What does API Test Bruno do?

A skill your agent uses 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 is an agent skill from naodeng/awesome-qa-skills. 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.

When should I use API Test Bruno?

API Test Bruno fits situations like: you need to parse multi-format API definitions and generate Bruno collections for executable regression; triggers include Bruno collections and Bruno API testing.

How do I install API Test Bruno in Claude Code?

Run `npx skills add naodeng/awesome-qa-skills --skill api-test-bruno -a claude-code`. Or copy the skill folder (skills/en/testing-types/api-test-bruno in naodeng/awesome-qa-skills) into .claude/skills/api-test-bruno in your project. Claude Code loads it when a task matches its description.

How do I install API Test Bruno in Codex?

Run `npx skills add naodeng/awesome-qa-skills --skill api-test-bruno -a codex`. Or copy the skill folder (skills/en/testing-types/api-test-bruno in naodeng/awesome-qa-skills) into .agents/skills/api-test-bruno in your project. Codex loads it when a task matches its description.

Can I use API Test Bruno in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add naodeng/awesome-qa-skills --skill api-test-bruno -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/api-test-bruno, .gemini/skills/api-test-bruno, .github/skills/api-test-bruno and .opencode/skills/api-test-bruno in your project.

What does API Test Bruno need to run?

Going by SKILL.md and its folder, API Test Bruno needs a shell for the scripts in its folder. Our summary lists: A Bash shell.

Does API Test Bruno access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is API Test Bruno safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does API Test Bruno use?

API Test Bruno has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does API Test Bruno use?

About 663 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 928 tokens, read only when the agent opens those files.

What are the alternatives to API Test Bruno?

Skills that share tags, products or a category with API Test Bruno: Diff-Driven QA (Skyvern-AI/skyvern, 23k stars), AI Regression Testing (affaan-m/ECC, 275k stars), Scout Best Practices Reviewer (elastic/kibana, 21k stars) and API Testing REST (PramodDutta/qaskills, 232 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains API Test Bruno?

naodeng (a GitHub user) maintains it in naodeng/awesome-qa-skills, which has 245 GitHub stars. The repository holds 22 skills in this directory. The repository was last updated on September 26, 2026.

Source: naodeng/awesome-qa-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.