emulator-control

Manage Azure Service Bus emulator lifecycle and validate AMQP port 5672 status.

1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/Indomitable/fast-servicebus-emulator --skill emulator-control-indomitable
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: emulator-control
Source: https://github.com/Indomitable/fast-servicebus-emulator/tree/main/.agents/skills/emulator-control
Command: npx skills add https://github.com/Indomitable/fast-servicebus-emulator --skill emulator-control-indomitable

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides comprehensive control over the Azure Service Bus emulator's lifecycle, simplifying its management during development and testing.

Core Features & Use Cases

  • Lifecycle Management: Start, stop, and restart the emulator with configurable options.
  • Status Monitoring: Check if the emulator is running and its ports are listening.
  • Log Management: View, tail, and search emulator logs for debugging.
  • Use Case: When starting a new development cycle, you can use this Skill to ensure the Service Bus emulator is running with debug logging enabled, and then check its status before proceeding with integration tests.

Quick Start

Start the emulator with debug logging enabled.

Frequently Asked Questions about emulator-control

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

FAQPage Schema
How do I start the Azure Service Bus emulator with custom configurations?

You can start the Azure Service Bus emulator using configurable options that support custom configurations, environment variables like CONFIG_PATH, and specific log levels for development.

How can I check if my Azure Service Bus emulator is running and listening?

Check the Azure Service Bus emulator status by validating process existence and verifying that the AMQP port 5672 is actively listening for connections.

How do I view and search Azure Service Bus emulator logs for debugging?

Manage Azure Service Bus emulator logs by viewing, tailing, and searching the output, using the RUST_LOG environment variable to control the verbosity of log levels.

Can I restart the Service Bus emulator during integration testing?

Yes, you can restart the Azure Service Bus emulator to reset its state during integration testing, providing comprehensive control over its lifecycle including stop and start commands.

What is the best way to manage the Service Bus emulator lifecycle during development?

Managing the Azure Service Bus emulator lifecycle is best handled by automating start, stop, and restart commands, ensuring debug logging is enabled before proceeding with tests.