bruno-generator

Convert legacy Bruno .yml collections to v3+ .bru format with secure environment variables.

Updated May 27, 2026
One-click install
npx skills add https://github.com/santanapol/agent-skills --skill bruno-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bruno-generator
Source: https://github.com/santanapol/agent-skills/tree/main/.cursor/skills/bruno-generator
Command: npx skills add https://github.com/santanapol/agent-skills --skill bruno-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the pain of managing Bruno API testing collections across different versions and file formats, eliminating compatibility issues between legacy .yml files and modern v3+ Bruno versions, and preventing insecure hardcoded credentials in API requests.

Core Features & Use Cases

  • Multi-format support: Works with both modern .bru and legacy .yml Bruno collection files for backward compatibility.
  • Secure credential handling: Enforces the use of Bruno environment variables instead of hardcoded sensitive data like API keys and user IDs.
  • Version-agnostic scripting: Provides reliable post-response token extraction scripts that work across Bruno versions, avoiding broken automation after tool updates.
  • Use Case: A QA team maintaining a legacy Bruno collection on v3+ can use this Skill to update all requests to use the correct runtime script format, extract access tokens reliably, and eliminate hardcoded credentials.

Quick Start

Use the bruno-generator skill to update your existing Bruno collection's login request to use the correct v3+ runtime script format for token extraction.

Frequently Asked Questions about bruno-generator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix Bruno legacy YAML collection compatibility issues in v3+?

Bruno legacy YAML collection compatibility issues in v3+ are resolved by updating legacy .yml files to the correct v3+ runtime script format. This process ensures backward compatibility and prevents syntax corruption during bulk collection updates.

How do I extract authentication tokens from API responses in Bruno?

Extracting authentication tokens in Bruno requires version-agnostic post-response scripting patterns. This approach uses reliable cross-version token extraction scripts to capture access tokens from login responses, preventing broken automation after Bruno updates.

How do I replace hardcoded API keys with environment variables in Bruno?

Replacing hardcoded API keys with environment variables in Bruno enforces secure credential handling. You configure Bruno environment variables for sensitive data like API keys and user IDs, eliminating insecure hardcoded credentials from your API testing collections.

Does the Bruno .bru format support scripts from older .yml collections?

Yes, the Bruno .bru format supports scripts from older .yml collections through multi-format backward compatibility. This allows you to manage both modern .bru and legacy .yml Bruno collection files simultaneously without losing existing request configurations.

What is the best way to safely bulk update Bruno collection files?

The best way to safely bulk update Bruno collection files is to use safe bulk update patterns that prevent YAML or Bru syntax corruption. This method updates multiple requests simultaneously while enforcing secure environment variable usage and version-agnostic scripting.