skills.rest
amoai-tech
amoai-techCOMMUNITY
Explore all skills by this author →
GitHub

events

Governs event creation, publishing, ticketing, and attendee flows in MDE AI.

1|Updated Sep 15, 2026
Search Tags:#events#stripe#ticketing#domain rules#event publishing#host workflows#mde ai
One-click install
npx skills add https://github.com/amoai-tech/mdeai --skill events-amoai-tech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: events
Source: https://github.com/amoai-tech/mdeai/tree/main/.claude/skills/events
Command: npx skills add https://github.com/amoai-tech/mdeai --skill events-amoai-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Event-domain changes in MDE AI span hosts, ticketing, payments, and discovery, and without clear boundaries these changes risk inconsistent event state, broken approval flows, and payment bugs. This Skill defines the domain rules and handoff boundaries so event work stays correct and scoped. ## Core Features & Use Cases - Domain Boundaries: Enforces rules for host creation/editing, HITL approval, ticket tiers, capacity, publish state, and organization-scoped writes. - Structured Workflow: Guides changes through persona identification, canonical state transitions, stack-skill loading, and end-to-end verification. - Stack Handoffs: Routes payment mechanics to stripe, persistence to supabase, agent logic to mastra, AI UI to copilotkit, and framework behavior to nextjs. - Use Case: When adding a new ticket tier to an event, use this Skill to keep capacity, pricing, and buyer-facing availability consistent while delegating Stripe checkout changes to the stripe skill. ## Quick Start Use the events skill to review my change to the event publishing flow and confirm the approval and ticketing rules stay intact.

Frequently Asked Questions about events

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

FAQPage Schema
How do I make a change to event creation or ticketing in MDE AI?▼

Start with the events skill to identify the persona, surface, and canonical event state transition being changed. Then load only the affected stack skills, define success and failure states, and verify the user journey and persistence path end to end.

What rules govern ticket tiers and event publishing workflows?▼

Ticket tiers, event capacity, dates, venue, publish state, and buyer-facing availability must stay internally consistent. Host creation and editing must preserve explicit HITL approval where the flow requires it, and all writes must remain organization or user scoped.

Which skill handles Stripe payments for event ticket purchases?▼

Payment mechanics are handed off to the stripe skill, while the events skill owns the domain rule that payment success comes from verified payment state, never UI optimism. Persistence goes to supabase and agent logic to mastra.

When should I not use the events skill for a bug near event flows?▼

When the root cause of a bug is unknown, route diagnosis to systematic-debugging rather than guessing within the events domain. The events skill retains domain evidence while diagnosis stays bounded to the debugging workflow.

Related Skills

Explore More Software Engineering Skills→
kxnkxn
289

remote-state-machine-guardrail

Audit and align remote-surface state machine documentation with implementation changes.

Community
Advanced
lespacemanlespaceman
4

verification-before-completion

Enforces verification before declaring tasks complete by requiring fresh evidence from tests, builds, or lint.

Community
Intermediate
gptdeividgptdeivid

copilotkit-integrations

Integrates external AI agent frameworks into CopilotKit applications via AG-UI protocol.

Community
Advanced
yashs33244yashs33244
1

investigate

Diagnose failures through systematic root-cause investigation across four phases.

Community
Advanced