How do I install the Mainstage Workflow skill?

Run npx skillmds@latest add gaelic-ghost/mainstage-workflow in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Mainstage Workflow safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Mainstage Workflow?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Mainstage Workflow free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Mainstage Workflow?

gaelic-ghost (@gaelic-ghost) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Mainstage Workflow by gaelic-ghost — Agent Skill

Name: Mainstage Workflow
Author: gaelic-ghost

Mainstage Workflow

Guide safe MainStage concert, set, patch, channel-strip, audio and MIDI device, mapping, rehearsal, backup, and live-performance preparation. Use when a user needs to prepare or troubleshoot MainStage while avoiding surprise routing, patch, playback, recording, or concert-file changes.

gaelic-ghost 23cafb2 3 files · 4.3 KB Updated Sep 17, 2026

File contents

MainStage Workflow

Use this skill for MainStage app operation and rehearsal preparation. Treat an active performance configuration as high risk.

Source Check

Search the local Tips/Help Viewer catalog for MainStage or open MainStage Help. Confirm the guide matches the installed app/version. Read references/concert-safety-contract.md before changing concert, set, patch, device, mapping, playback, or recording state.

Workflow

Classify the request: inspect, rehearsal preparation, concert/set/patch organization, audio/MIDI device setup, channel-strip routing, mapping, missing device/plug-in repair, backup, or live-performance issue.
Establish the performance contract: whether the configuration is live, rehearsal-only, or disposable; available audio/MIDI hardware; intended inputs/outputs; selected concert/set/patch; backup location; and what must not change.
Inspect before action: active mode, selected set/patch, concert path, audio device, MIDI devices/controllers, channel strips, output routing, mappings, missing plug-ins/media, and current playback/record state.
Preserve the concert. For configuration changes, use a duplicate or explicit backup. Do not save over an active performance file without confirmation.
Confirm immediately before changing selected patches, audio or MIDI devices, channel-strip output routes, mappings, playback, recording, or concert file state. State the user-visible effect and recovery path.
Prepare one rehearsal path: verify audio input/output, MIDI response, patch selection, mappings, level/mute behavior, and any backing-track/transport behavior using observed device evidence.
Report the ready/not-ready state with the specific concert/set/patch, connected devices, tested routes, untested components, backup status, and next safe action.

Guards

Never validate against a live show without explicit confirmation at the moment of the potentially disruptive action.
Do not change a concert, patch, mapping, or audio/MIDI device merely to see what happens.
Do not claim hardware routing, controller response, latency, or sound-check readiness without observed device evidence.
Do not perform unattended playback, recording, or device reconfiguration.
Do not treat missing plug-ins/media as something to replace automatically; identify the exact dependency and stop for direction.

Handoffs

logic-pro-workflow for Logic session/bounce preparation before a MainStage handoff.
apple-dev-skills:avfaudio-session-workflow or avaudio-engine-workflow for application-code audio routing or engine issues.
apple-dev-skills:xcode-build-run-workflow only when MainStage-related work actually concerns an Apple app or plug-in project build/run surface.

---name: mainstage-workflowdescription: Guide safe MainStage concert, set, patch, channel-strip, audio and MIDI device, mapping, rehearsal, backup, and live-performance preparation. Use when a user needs to prepare or troubleshoot MainStage while avoiding surprise routing, patch, playback, recording, or concert-file changes.---# MainStage WorkflowUse this skill for MainStage app operation and rehearsal preparation. Treat an active performance configuration as high risk.## Source CheckSearch the local Tips/Help Viewer catalog for `MainStage` or open MainStage Help. Confirm the guide matches the installed app/version. Read `references/concert-safety-contract.md` before changing concert, set, patch, device, mapping, playback, or recording state.## Workflow1. Classify the request: inspect, rehearsal preparation, concert/set/patch organization, audio/MIDI device setup, channel-strip routing, mapping, missing device/plug-in repair, backup, or live-performance issue.2. Establish the performance contract: whether the configuration is live, rehearsal-only, or disposable; available audio/MIDI hardware; intended inputs/outputs; selected concert/set/patch; backup location; and what must not change.3. Inspect before action: active mode, selected set/patch, concert path, audio device, MIDI devices/controllers, channel strips, output routing, mappings, missing plug-ins/media, and current playback/record state.4. Preserve the concert. For configuration changes, use a duplicate or explicit backup. Do not save over an active performance file without confirmation.5. Confirm immediately before changing selected patches, audio or MIDI devices, channel-strip output routes, mappings, playback, recording, or concert file state. State the user-visible effect and recovery path.6. Prepare one rehearsal path: verify audio input/output, MIDI response, patch selection, mappings, level/mute behavior, and any backing-track/transport behavior using observed device evidence.7. Report the ready/not-ready state with the specific concert/set/patch, connected devices, tested routes, untested components, backup status, and next safe action.## Guards- Never validate against a live show without explicit confirmation at the moment of the potentially disruptive action.- Do not change a concert, patch, mapping, or audio/MIDI device merely to see what happens.- Do not claim hardware routing, controller response, latency, or sound-check readiness without observed device evidence.- Do not perform unattended playback, recording, or device reconfiguration.- Do not treat missing plug-ins/media as something to replace automatically; identify the exact dependency and stop for direction.## Handoffs- `logic-pro-workflow` for Logic session/bounce preparation before a MainStage handoff.- `apple-dev-skills:avfaudio-session-workflow` or `avaudio-engine-workflow` for application-code audio routing or engine issues.- `apple-dev-skills:xcode-build-run-workflow` only when MainStage-related work actually concerns an Apple app or plug-in project build/run surface.

Frequently asked questions