inngest-workflow
Create Inngest workflows for durable execution. Use when building agent workflows, approval flows, scheduled tasks, or any multi-step async process.
Discover Databases skills, compare source repositories and read the instructions for each workflow.
Create Inngest workflows for durable execution. Use when building agent workflows, approval flows, scheduled tasks, or any multi-step async process.
Deploy and manage Vercel projects via CLI. Use when deploying apps, managing environment variables, configuring domains, or pushing secrets to Vercel. Triggers on deploy, vercel, env vars, production.
Add a new Skill Recordings product to the support platform. Use when user says "add product", "new app", "onboard [product name]", or similar.
Guide user through support platform setup. Use when user says "set up", "configure", "I'm on step X", or provides API keys/credentials.
CLI for Skill Recordings Support Agent platform. Use when investigating support issues, debugging workflows, inspecting Front/Inngest data, or managing app integrations.
Enforce TDD workflow (red → green → refactor). Use for any code change that is testable.
Build Front plugins using the Plugin SDK. Use when creating sidebar plugins, composer plugins, or extending Front's UI. Triggers on plugin, front plugin, sidebar plugin, composer plugin, @frontapp/plugin-sdk.
Convert between Front URL IDs (base-10) and API IDs (base-36 with prefix). Use when working with Front inbox, conversation, or message IDs.
Create SDK adapters for new app integrations. Use when onboarding a new Skill Recordings product, implementing the SupportIntegration interface, or scaffolding a new app.
Implement human-in-the-loop approval flows. Use when adding Slack approvals, dashboard review queues, action gating, or trust-based auto-approval.
Implement vector search for knowledge retrieval. Use when adding RAG, semantic search, knowledge base features, or context building for the agent.
Reference for Front REST API integration. Use when working with Front API schemas, nullable fields, webhooks, or debugging Front SDK issues.
Commit all changes with validation, conventional commit message, GPG signing, and push to origin
Create or update a pull request for the current branch
Create a new feature branch from a beads issue with proper prefix, worktree, and beads initialization
Sync with remote using smart rebase/merge selection based on push status
Convert Spec Kit task list markdown files to bd (Beads) issues with proper hierarchy
Check development status - uncommitted changes, last commit, beads tasks, and PR status
Ensures clear understanding before any code changes, asks clarifying questions when requirements are ambiguous, discusses trade-offs, and protects the codebase from unintended alterations.
Generate Vitest unit tests for new features/components to prevent regressions
Systematic debugging of code to find root causes, fix bugs, and prevent regressions. Use whenever an error, bug, or unexpected behavior appears.
Critical guardrail for Supabase database operations ensuring multi-tenant isolation with publication_id filtering, proper use of supabaseAdmin, avoiding SELECT *, error handling patterns, and secure server-side...
Next.js 15 API route patterns, NextRequest, NextResponse, error handling, maxDuration configuration, authentication, request validation, server-side operations, route handlers, and API endpoint best practices....
AI content generation with OpenAI and Claude, callAIWithPrompt usage, prompt storage in app_settings, structured outputs, response format validation, multi-criteria scoring, rate limiting, JSON schema, and AI A...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.