Loading...
Loading...
Found 599 Skills
Inspect Mermail AI, API, and email usage and manage workspaces, members, invitations, email domains, mailboxes, webhooks, and storage. Use for workspace administration, access changes, domain verification, mailbox provisioning or settings, webhook subscriptions and deliveries, storage checks, plan usage, RPM, or credits. Do not use for generic inbox work, composing mail, or third-party app execution.
Use when building, adding or auditing a Telegram bot on the HTTP Bot API: polling or webhooks, update dedup, keyboards, Telegram Stars payments, files and rate limits. Not for user accounts (telegram-userbots) or the web layer (telegram-miniapps). Opt out: no telegram, без телеграма. Triggers - "telegram bot", "bot api", "aiogram", "setWebhook", "telegram stars", "телеграм бот", "вебхук телеграм", "звёзды телеграм".
Payments library: idempotency-key patterns, a webhook reliability checklist, Stripe, Adyen, and PayPal quirks, a refund and chargeback decision tree, currency handling, PCI scope reduction, the PaymentIntent state machine, and code for idempotent creation, webhook processing, 3DS2 exemptions, and dunning. Use when building or debugging payment flows.
Receive and verify inbound webhooks from providers like Stripe, GitHub, Twilio, Slack, or Shopify and deliver them to a local or private service without exposing that service to the public internet. Verify signatures at the edge with no app code; route third-party callbacks to a service behind a firewall, including regulated (HIPAA/PCI) environments or a centralized webhook gateway shared across teams. Use when the user needs to receive, test, or debug webhooks locally, wants signature verification without writing it, or must route callbacks to a private service.
Trello learning task board — use the cyeam CLI to query boards, status groups, and today's tasks; create, modify, and move tasks; upload and view submission photos; review task history; and register or delete real-time Webhooks. Use this when the user mentions Trello, a learning task board, pending/submitted/accepted statuses, task photos, or Trello synchronization. You must read the original skill documentation first to obtain the correct command syntax; do not guess.
Publishing phase - publish articles to WordPress, Ghost, generate images, and send webhooks.
BFL FLUX API integration guide covering endpoints, async polling patterns, rate limiting, error handling, webhooks, and regional endpoints with Python and TypeScript code examples.
Generate, remix, edit, inpaint, reframe, background-process, describe, layerize, and upscale images with the Ideogram Developer API. Use when Codex must integrate Ideogram 4.0 or 3.0, render reliable typography or structured layouts, use style or character references, build synchronous or webhook workflows, migrate legacy Ideogram endpoints, or reason about Ideogram API pricing, safety, privacy, and production QA.
Select, integrate, and operate multi-model image-generation gateways with model-specific schema discovery, version policy, asynchronous jobs, webhooks, spend approval, safe inputs and artifacts, data-governance review, and billing observability. Use for comparing or building against fal.ai, Replicate, or Together AI image APIs, including controlled failover; do not use for direct model-provider APIs, local inference, training, dedicated endpoint provisioning, video generation, or general image editing.
Build automated AI workflows combining multiple models and services. Patterns: batch processing, scheduled tasks, event-driven pipelines, agent loops. Tools: inference.sh CLI, bash scripting, Python SDK, webhook integration. Use for: content automation, data processing, monitoring, scheduled generation. Triggers: ai automation, workflow automation, batch processing, ai pipeline, automated content, scheduled ai, ai cron, ai batch job, automated generation, ai workflow, content at scale, automation script, ai orchestration
Long-running, serverless Node.js HTTP functions deployed onto your Neon branch, with DATABASE_URL injected automatically and compute that runs next to your data. Use when a user wants to host an API, an AI agent with long streaming responses, a WebSocket or server-sent-events (SSE) server, a webhook handler, a Discord bot, an MCP server, or any request/response workload that risks timing out on short, lambda-style serverless functions — and wants it to branch with their database. Triggers include "serverless function", "deploy an API", "long-running function", "streaming agent", "SSE server", "WebSocket server", "webhook handler", "MCP server", "run code next to my database", "function that won't time out", "function logs", "Neon Functions", and "Neon Compute".
Produce a polished, self-contained HTML "readout" document under ~/.readouts (with an auto-maintained index page), either by snapshotting the findings accumulated in the current conversation or — when invoked fresh, e.g. "/readout on how github webhook events are processed" — by sharpening scope with clarifying questions and researching the codebase before documenting. The work runs in a child agent so the main conversation's context stays clean. Use whenever the user invokes /readout, says "write this up", "turn this into a doc/page", "make a readout", or asks for a readable, shareable document capturing findings or explaining how something works.