api-test-bruno (EN)

Chinese version： See the corresponding Chinese skill.

When to Use

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.

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.

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.

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