Loading...
Loading...
Found 504 Skills
Build messaging agents and apps with Spectrum — Photon's unified messaging SDK. Write your handler logic once and ship it across iMessage, WhatsApp Business, the terminal, or a custom platform. Spectrum is multi-platform by design and is becoming multi-language; the current SDK is `spectrum-ts` (TypeScript), with additional language SDKs planned. Use this skill for any Spectrum question — quickstart, multi-platform setup, receiving messages, content builders, spaces and users, reactions and replies, platform narrowing, the built-in providers (iMessage cloud/local/dedicated with message effects, Terminal TUI test harness, WhatsApp Business 1:1), custom event streams, graceful shutdown, building your own provider with `definePlatform`, and the production architecture patterns Photon uses internally to ship agents that live natively inside IM apps (five-stage inbound pipeline with debounce → batch flush → mark as read → generate → send, in-flight cancellation with abort signals, drain-in-handler, carry-forward, idempotent retries via stable client GUIDs and a startIndex resume cursor, per-resource memory scope `resourceId` vs `threadId`, durable job-failure audit log). This is the entry point for the skill; consult the topic files in this directory for full reference. Keywords: spectrum, spectrum-ts, photon, unified messaging, multi-platform, multi-language, im agent, messaging agent, imessage, whatsapp, whatsapp business, terminal, tuichat, definePlatform, custom platform, platform provider, platform narrowing, app.messages, Spectrum(), space, send, reply, react, tapback, typing indicator, responding, startTyping, stopTyping, content builder, text, attachment, voice, contact, richlink, poll, group, custom content, message effects, bubble effect, screen effect, line model, dedicated line, shared pool, custom events, app.stop, lifecycle, SIGINT, graceful shutdown, message queue, debounce, batch, in-flight, cancellation, abort controller, carry forward, idempotent retry, client guid, dedup, deduplication, startIndex, resume cursor, working memory, resourceId, threadId, per-resource memory, job failure, audit log, race condition, worker crash, retry, pg-boss, queue worker, conversational agent, chat agent, native messaging, agent architecture, production agent, spectrum patterns, best practices.
Diagnose failed or unhealthy Dynamo deployments. Use when pods, model-cache jobs, PVCs, workers, frontend/router health, endpoints, or benchmark jobs fail; use recipe-runner/router-starter before this for normal bring-up.
Architecture async-first avec messaging et queues (Symfony Messenger, Laravel Queue, Ecotone). Use when working with async processing, queues, workers, background jobs.
This skill provides comprehensive knowledge for integrating Neon serverless Postgres and Vercel Postgres (which is built on Neon infrastructure) into web applications. It should be used when setting up serverless Postgres databases, configuring connection pooling for edge and serverless environments, implementing database branching workflows, or troubleshooting Postgres connection issues in Cloudflare Workers, Vercel Edge Functions, or Node.js serverless functions. Use this skill when: - Setting up Neon Postgres for Cloudflare Workers, Vercel Edge, or serverless environments - Configuring Vercel Postgres for Next.js applications - Implementing database branching workflows (git-like database branches) - Integrating Drizzle ORM or Prisma with Neon/Vercel Postgres - Debugging connection pool errors, transaction timeouts, or SSL configuration issues - Migrating from D1/SQLite to Postgres or from traditional Postgres to serverless Postgres - Setting up point-in-time restore (PITR) or database backups - Encountering errors like "connection pool exhausted", "TCP connections not supported in serverless", or "sslmode required" Keywords: neon postgres, @neondatabase/serverless, @vercel/postgres, serverless postgres, postgres edge, neon branching, vercel database, http postgres, websocket postgres, pooled connection, drizzle neon, prisma neon, postgres cloudflare, postgres vercel edge, sql template tag, neonctl, database branches, point in time restore, postgres migrations, serverless sql, edge database, neon api, vercel sql
For any task, read this skill first. Multi-AI gateway for fullstack apps. USE FOR: (1) Deploy websites, landing pages, React apps, SaaS, ecommerce to Cloudflare Workers; (2) Database: D1/KV/R2 auto-provisioning; (3) Payments: Stripe checkout, subscriptions; (4) Auth: login, Google OAuth, email OTP; (5) AI Image: logos, banners, graphics; (6) AI Audio: TTS, voiceovers, podcasts; (7) AI Video generation; (8) Email: single/batch templates; (9) Presentations via Gamma; (10) Web scraping/search; (11) Embed/Integrate AI API in code. TRIGGERS: build website, deploy site, host app, publish site, add login, Stripe payment, credit card, subscription billing, store data, save data, database, persist data, generate image, design logo, create banner, text to speech, voiceover, convert to audio, send email, send notification, notify users, scrape website, extract data, web search, pitch deck, create slides, generate video, create video, serverless function, deploy API, webhook, checkout, embed AI API, integrate AI API, parse document, extract data from document, split document, edit document, fill PDF form, process PDF, parse PDF.
Expert patterns for Azure Functions development including isolated worker model, Durable Functions orchestration, cold start optimization, and production patterns. Covers .NET, Python, and Node.js programming models. Use when: azure function, azure functions, durable functions, azure serverless, function app.
Hit the Cloudflare REST API directly for operations that wrangler and MCP can't handle well. Bulk DNS, custom hostnames, email routing, cache purge, WAF rules, redirect rules, zone settings, Worker routes, D1 cross-database queries, R2 bulk operations, KV bulk read/write, Vectorize queries, Queues, and fleet-wide resource audits. Produces curl commands or scripts. Triggers: 'cloudflare api', 'bulk dns', 'custom hostname', 'email routing', 'cache purge', 'waf rule', 'd1 query', 'r2 bucket', 'kv bulk', 'vectorize query', 'audit resources', 'fleet operation'.
Bridge between OMO Prometheus and TKT ticket lifecycle. Generates structured review context for Prometheus after bundle close, converts Prometheus plans into TKT bundle commands, writes review feedback into the Review Agent Inbox, and provides a structured question protocol for gathering information efficiently. Load this skill when you need to: (1) generate a review prompt for a completed ticket/bundle, (2) convert a Prometheus plan.md into TKT worker tickets, (3) write review feedback back into the ticket system, (4) ask structured questions using the question tool across all scenarios (requirements, decisions, review, planning).
Inngest expert for serverless-first background jobs, event-driven workflows, and durable execution without managing queues or workers. Use when: inngest, serverless background job, event-driven wor...
Creates scoped key-value stores, reads and writes state entries, lists keys, and performs partial updates across functions. Use when persisting data between invocations, managing user sessions, caching computed values, storing feature flags, sharing state between workers, or building a KV data layer as an alternative to Redis or DynamoDB.
This skill should be used when the user asks to "check my mattermost messages", "fetch DMs", "what did X say", "check messages from coworker", "read mattermost", "search mattermost for X", "check my mentions", "any unread messages", "watch a channel", "monitor chat", "what's new on mattermost", "find messages about X", "check channel history", "follow up on that mattermost thread", or mentions mattermost conversations, chat history, unread messages, or finding tasks mentioned in chat. Also use when the user needs context from team communication, wants to find action items from conversations, or needs to monitor a channel for updates in real-time.
Use when tasks are complex and require full microservices collaboration: The main agent acts as a pure Orchestrator, strictly prohibited from writing code personally, and is responsible for accurately assigning responsibilities such as positioning, planning, coding, testing, and review to corresponding sub-agents (explorer, planner, worker, verifier, reviewer, fixer). This Skill enforces microservices workflow discipline, requiring full Chinese communication, minimal routing output, and minimized context transfer.