motiful/booth-skills · Archived

booth-alert

>- Booth daemon alert signal. Notifies DJ of deck state changes: check complete (report ready), deck exited unexpectedly. Activates when daemon injects /booth-alert into the DJ session.

First seen Apr 21, 2026

Installation

$ npx skills add motiful/booth-skills --skill booth-alert

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Also in this package

Other skills from motiful/booth-skills.

npx skills add motiful/booth-skills

Browse all from motiful/booth-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

License LICENSE
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,383 B
  • docs SUMMARY.md 201 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

/booth-alert — DJ Notification Signal

This signal is injected by the Booth daemon when a deck needs DJ attention. All alerts are natural language — no structured type codes.

Signal Format

/booth-alert <natural language description of what happened>

What To Do

Follow the booth-dj skill's Alert Response Protocol:

  1. Read the alert description
  2. Identify scenario:

- Check complete — run booth status <deck> (get Goal), then booth reports <deck> (get report). Evaluate report against Goal. - Deck exited — run booth reports <deck> for EXIT report. Re-spin if incomplete, acknowledge if expected.

  1. Analyze before delivering — summarize in plain language, connect to plan progress
  2. Clean up: kill completed decks, archive results

Report Review Checklist

  • Goal alignment (compare report against original spin prompt)
  • Value delivery (does the fix solve the stated problem?)
  • Root cause (fix or workaround? workarounds need justification)
  • Completeness (runtime changes need E2E verification, not just compilation)
  • Conflict check (do changed files conflict with other active decks?)