ceremonies

Inspect scheduled yeaboi ceremonies, their cadences, delivery channels, and run outcomes.

4|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/yeaboi-ai/yeaboi.ai --skill ceremonies-yeaboi-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ceremonies
Source: https://github.com/yeaboi-ai/yeaboi.ai/tree/main/claude-plugin/yeaboi/skills/ceremonies
Command: npx skills add https://github.com/yeaboi-ai/yeaboi.ai --skill ceremonies-yeaboi-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams schedule yeaboi modes like daily standups and weekly reports to run automatically via launchd or crontab, but when a morning goes quiet there is no visibility into what was declared, what the OS actually installed, or why a run was skipped. This Skill surfaces that gap so you can diagnose silent schedules without guessing. ## Core Features & Use Cases - List declared ceremonies: View every ceremony with its mode, cadence, channels, and last-run status, cross-checked against OS-installed jobs to catch declarations that will never fire. - Review run history: See what actually fired, newest first, with honest outcome interpretation across ok, failed, skipped_stale, skipped_over_cap, and skipped_paused states. - Diagnose delivery and cost issues: Identify dead Slack webhooks, monthly spend caps that halted runs, and stale skips caused by sleeping laptops. - Use Case: Your Monday delivery report never posted to Slack. Use this Skill to discover the ceremony hit its monthly_cap_usd and was skipped, then get the exact terminal command to raise the cap. ## Quick Start Ask the assistant to list your scheduled yeaboi ceremonies and explain why the daily standup did not post this morning.

Frequently Asked Questions about ceremonies

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

FAQPage Schema
How do I check why my scheduled standup did not post?▼

List the ceremonies and review the run history for that ceremony. The outcome field explains it: skipped_stale means the laptop was asleep, skipped_over_cap means the monthly spend cap was reached, and failed includes the error reason.

How do I see which yeaboi ceremonies are scheduled to run automatically?▼

Use the ceremonies list to see every declared ceremony with its mode, cadence, channels, and last-run status. Compare it against installed_jobs from the operating system to confirm each one will actually fire.

Why is a declared ceremony not running on schedule?▼

A ceremony declared in yeaboi but missing from the OS installed_jobs list will never fire, since launchd or crontab triggers it. Re-add it from the terminal with yeaboi ceremonies add to reinstall the scheduled job.

Can I create or pause a scheduled ceremony from this Skill?▼

No. Declaring, editing, pausing, or removing ceremonies is deliberately unavailable here because those actions install scheduled jobs on your machine. Run yeaboi ceremonies add, pause, or run directly in the terminal instead.

What does skipped_over_cap mean for a scheduled run?▼

It means the ceremony's spend for the month reached its monthly_cap_usd limit, so the scheduled run was skipped to control unattended cost. Raising the cap with the --monthly-cap option allows it to run again.