api-test-bruno
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.
Install
npx skills add https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/api-test-bruno
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install naodeng-awesome-qa-skills@llmmart
git clone https://github.com/naodeng/awesome-qa-skills.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole naodeng/awesome-qa-skills collection as a plugin from our marketplace. Git is the plain clone.
README
api-test-bruno (EN)
Skill Overview
Need API outputs that should land in Bruno structure or Bruno workflow; The project already uses Bruno or wants Bruno-ready organization.
How to Use
- Open
SKILL.mdin this folder and confirm this skill fits your task. - In your AI tool, call
@skill api-test-bruno, then add your real project context and goal. - If you need a specific output format (table, checklist, report), include it directly in your request.
One-Click Install Script
Run from the repository root:
macOS / Linux
bash ./scripts/install-skills-mac.sh --tool codex --lang en --skill api-test-bruno
Windows PowerShell
powershell -ExecutionPolicy Bypass -File .\scripts\install-skills-windows.ps1 -Tool codex -Lang en -Skill api-test-bruno
Skill manifest
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.
Generation and execution boundary
Generators produce smoke assertions for known fields only: require nonempty endpoints and explicit expected_statuses; optional expected_json and sourced max_response_ms. Missing data, unresolved parameters/variables, or schema assertions produce incomplete scaffolds and a nonzero exit. Read references/generator-contract.md; configure target and credentials explicitly.
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.
Files (awesome-qa-skills)
-
agents
-
openai.yaml 471 B
Loading…
-
-
evals
-
cases
-
basic-success.yaml 2.5 KB
Loading… -
edge-bad-or-neighbor.yaml 668 B
Loading… -
edge-incomplete-input.yaml 636 B
Loading… -
review-repair-regression.yaml 1.3 KB
Loading…
-
-
fixtures
-
scripts
-
check_bruno_output.sh 1.3 KB
Loading…
-
-
openapi-orders.yaml 1.8 KB
Loading… -
sample-curls.sh 551 B
Loading…
-
-
graders
-
review-repair-regression.py 1.1 KB
Loading…
-
-
eval.yaml 635 B
Loading… -
trigger_queries.json 927 B
Loading…
-
-
examples
-
bruno
-
sample.bru 137 B · in bundle
-
-
ci
-
github-actions-bruno.yml 853 B
Loading… -
Jenkinsfile.bruno 599 B · in bundle
-
-
sample.curl 212 B · in bundle
-
sample.insomnia.json 502 B
Loading… -
sample.openapi.yaml 240 B
Loading… -
sample.opencollection.json 243 B
Loading… -
sample.postman_collection.json 704 B
Loading… -
sample.wsdl 534 B · in bundle
-
-
output-templates
-
template-markdown.md 83 B
Loading…
-
-
prompts
-
api-test-bruno.md 5.7 KB
Loading…
-
-
references
-
local
-
api-testing_EN-1.md 487 B
Loading… -
api-testing_EN.md 487 B
Loading…
-
-
framework-spec.md 1.5 KB
Loading… -
generator-contract.md 2.5 KB
Loading… -
report-schema.md 800 B
Loading… -
setup-and-ci.md 447 B
Loading…
-
-
scripts
-
templates
-
bruno
-
environments
-
staging.bru 64 B · in bundle
-
-
requests
-
health.bru 204 B · in bundle
-
-
bruno.json 74 B
Loading…
-
-
-
api_case_contract.py 7.5 KB
Loading… -
check_bruno_report.py 2.2 KB
Loading… -
generate_bruno_requests.py 3.3 KB
Loading… -
parse_api_sources.py 18.4 KB
Loading… -
run-tests.sh 785 B
Loading… -
run.sh 582 B
Loading…
-
-
README.md 808 B
# api-test-bruno (EN) ## Skill Overview Need API outputs that should land in Bruno structure or Bruno workflow; The project already uses Bruno or wants Bruno-ready organization. ## How to Use 1. Open `SKILL.md` in this folder and confirm this skill fits your task. 2. In your AI tool, call `@skill api-test-bruno`, then add your real project context and goal. 3. If you need a specific output format (table, checklist, report), include it directly in your request. ## One-Click Install Script Run from the repository root: ### macOS / Linux ```bash bash ./scripts/install-skills-mac.sh --tool codex --lang en --skill api-test-bruno ``` ### Windows PowerShell ```powershell powershell -ExecutionPolicy Bypass -File .\scripts\install-skills-windows.ps1 -Tool codex -Lang en -Skill api-test-bruno ``` -
SKILL.md 3.3 KB
--- name: api-test-bruno description: 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. license: PolyForm-Noncommercial-1.0.0 metadata: version: "1.0.0" compatibility: "" author: "Awesome QA Skills contributors" language: "en" category: "testing-types" source: "https://github.com/naodeng/awesome-qa-skills" license-url: "https://polyformproject.org/licenses/noncommercial/1.0.0" --- # 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. ## Generation and execution boundary Generators produce smoke assertions for known fields only: require nonempty endpoints and explicit expected_statuses; optional expected_json and sourced max_response_ms. Missing data, unresolved parameters/variables, or schema assertions produce incomplete scaffolds and a nonzero exit. Read `references/generator-contract.md`; configure target and credentials explicitly. ## 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.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.