eventbriteEventbrite API integration with managed OAuth. Manage events, venues, ticket classes, orders, and attendees. Use this skill when users want to create and manage events, check orders, view attendees, or access event categories. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Requires network access and valid Maton API key. Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn an Eventbrite connection into automation, in the order they are used: the connection (the first step), a hosted function that runs an Eventbrite action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Eventbrite examples; they add no Eventbrite capability - Eventbrite is not an event source, a trigger cannot read Eventbrite data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
Install via ClawdBot CLI:
clawdbot install byungkyu/eventbriteGrade Good — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://clawhub.ai/byungkyu/api-gatewayUses known external API (expected, informational)
discord.comAudited Apr 18, 2026 · audit v1.0
Generated Mar 22, 2026
A small business owner uses the skill to create and manage promotional events, track ticket sales, and view attendee lists. They automate event setup via API calls, reducing manual entry and ensuring consistent branding across events. This helps them focus on marketing and customer engagement rather than administrative tasks.
A nonprofit organization leverages the skill to organize fundraising conferences, manage multiple sessions and venues, and process attendee registrations. They use it to generate reports on ticket sales and attendee demographics, aiding in donor outreach and event optimization for future campaigns.
A tech startup integrates the skill into their app to offer event ticketing as a service, allowing users to create and sell tickets directly. They automate order processing and attendee management, providing real-time updates and analytics to improve user experience and drive platform adoption.
A corporate training company uses the skill to schedule and manage workshops, handle employee registrations, and track attendance across multiple locations. They automate venue setup and ticket class creation, streamlining logistics and ensuring compliance with internal training requirements.
A local government agency employs the skill to coordinate public events like festivals and town halls, managing venues, ticket sales, and attendee feedback. They use it to ensure accessibility and monitor event success, supporting community engagement and resource allocation.
Developers embed the skill into a SaaS platform to offer event management as a feature, charging subscription fees based on usage tiers. This model generates recurring revenue by providing value-added services to clients who need seamless event handling without building their own integration.
Marketing or event agencies use the skill to manage client events, offering setup, monitoring, and reporting as part of a service package. Revenue comes from project-based fees or retainer agreements, leveraging automation to scale operations and serve multiple clients efficiently.
Freelancers offer consulting services to help businesses set up and optimize their Eventbrite integrations using the skill. They charge hourly or fixed rates for customization, troubleshooting, and training, tapping into the growing demand for API expertise in event management.
💬 Integration Tip
Start by setting the MATON_API_KEY environment variable and testing with simple GET requests like fetching user data before moving to more complex operations such as event creation.
Scored Oct 19, 2026
Self-hosted auth for TypeScript/Cloudflare Workers with social auth, 2FA, passkeys, organizations, RBAC, and 15+ plugins. Requires Drizzle ORM or Kysely for D1 (no direct adapter). Self-hosted alternative to Clerk/Auth.js. Use when: self-hosting auth on D1, building OAuth provider, multi-tenant SaaS, or troubleshooting D1 adapter errors, session caching, rate limits, Expo crashes, additionalFields bugs.
Clerk integration. Manage Users, Organizations. Use when the user wants to interact with Clerk data.
Clerk auth with API Keys beta (Dec 2025), Next.js 16 proxy.ts (March 2025 CVE context), API version 2025-11-10 breaking changes, clerkMiddleware() options, webhooks, production considerations (GCP outages), and component reference. Prevents 15 documented errors. Use when: API keys for users/orgs, Next.js 16 middleware filename, troubleshooting JWKS/CSRF/JWT/token-type-mismatch errors, webhook verification, user type inconsistencies, or testing with 424242 OTP.
Sentry API integration with managed authentication. Monitor errors, issues, and application performance. Use this skill when users want to list issues, retrieve events, manage projects, teams, or releases in Sentry. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Sentry connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Sentry action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Sentry examples; they add no Sentry capability - Sentry is not an event source, a trigger cannot read Sentry data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
Download YouTube videos by URL in various resolutions using a pay-per-use API with credit-based authentication and no charge on failed downloads.
OneNote API integration with managed OAuth via Microsoft Graph. Access notebooks, sections, section groups, and pages. Use this skill when users want to create or manage OneNote notebooks, organize notes, or work with page content. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn an OneNote connection into automation, in the order they are used: the connection (the first step), a hosted function that runs an OneNote action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with OneNote examples; they add no OneNote capability - OneNote is not an event source, a trigger cannot read OneNote data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).