Loading...
Loading...
Found 503 Skills
Loop Returns integration. Manage Returns, Merchants, Customers, Integrations. Use when the user wants to interact with Loop Returns data.
Apply when designing or implementing asynchronous processing in VTEX IO services through events, workers, and background handlers. Covers event handler structure, idempotency, retry-safe processing, and moving expensive work out of request-response routes. Use for event-driven integrations, delayed processing, or background jobs in VTEX IO apps.
Emulated Vercel REST API for local development and testing. Use when the user needs to interact with Vercel API endpoints locally, test Vercel integrations, emulate projects/deployments/domains, set up Vercel OAuth flows, manage environment variables, create API keys, configure protection bypass, or test without hitting the real Vercel API. Triggers include "Vercel API", "emulate Vercel", "mock Vercel", "test Vercel OAuth", "Vercel integration", "local Vercel", or any task requiring a local Vercel API.
Emulated GitHub REST API for local development and testing. Use when the user needs to interact with GitHub API endpoints locally, test GitHub integrations, emulate repos/issues/PRs, set up GitHub OAuth flows, configure GitHub Apps, test webhooks, or work with actions/checks without hitting the real GitHub API. Triggers include "GitHub API", "emulate GitHub", "mock GitHub", "test GitHub OAuth", "GitHub App JWT", "local GitHub", or any task requiring a local GitHub API.
Meltwater platform help — media intelligence, social listening, media relations (journalist database + outreach), influencer marketing, social media management, consumer intelligence, Mira AI, API, and integrations. Use when Meltwater Explore searches return noisy results, media monitoring is missing coverage, journalist contacts are outdated, influencer campaigns aren't tracking properly, social publishing isn't scheduling, Meltwater API or Mira AI isn't returning expected data, or CRM/BI integrations aren't syncing. Do NOT use for cross-platform social listening strategy (use /sales-social-listening), cross-platform media relations strategy (use /sales-media-relations), cross-platform influencer marketing strategy (use /sales-influencer-marketing), or email deliverability (use /sales-deliverability).
Sprout Social platform help — Publishing, Smart Inbox, Analytics, Social Listening (add-on), Influencer Marketing, Employee Advocacy, AI Assist, API, Salesforce/HubSpot/Zendesk integrations. Use when Sprout Social posts aren't publishing on schedule, Smart Inbox is overwhelming and hard to triage, analytics reports don't show the metrics you need, social listening queries return too much noise, influencer campaigns in Sprout lack visibility, employee advocacy adoption is low, AI Assist suggestions feel off, CRM sync keeps disconnecting, or you're deciding between Sprout Social and Hootsuite/Buffer/Agorapulse. Do NOT use for social listening strategy across tools (use /sales-social-listening), influencer marketing strategy (use /sales-influencer-marketing), social media management strategy (use /sales-social-media-management), or employee advocacy strategy (use /sales-employee-advocacy).
Reverse-engineer any codebase into a complete Product Requirements Document (PRD). Analyzes routes, components, state management, API integrations, and user interactions to produce business-readable documentation detailed enough for engineers or AI agents to fully reconstruct every page and endpoint. Works with frontend frameworks (React, Vue, Angular, Svelte, Next.js, Nuxt), backend frameworks (NestJS, Django, Express, FastAPI), and fullstack applications. Trigger when users mention: generate PRD, reverse-engineer requirements, code to documentation, extract product specs from code, document page logic, analyze page fields and interactions, create a functional inventory, write requirements from an existing codebase, document API endpoints, or analyze backend routes.
Scans any project repository and generates a "Source of Truth" documentation set in the core-knowledge folder, covering architecture, business logic, feature flags, deployment, and any cloud/serverless integrations.
Build email, calendar, and contacts integrations with the Nylas v3 API. Use when code imports nylas, @nylas/nylas, nylas-python, or user asks about Nylas API, email API integration, calendar API, contacts API, OAuth grants, webhooks, scheduler, notetaker, smart compose, or transactional send. DO NOT use for Nylas CLI commands.
Expert knowledge for Azure Data Factory development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when designing ADF pipelines, mapping data flows, SHIR/SSIS IR, SAP CDC, or CI/CD with ARM/DevOps, and other Azure Data Factory related development tasks. Not for Azure Synapse Analytics (use azure-synapse-analytics), Azure Databricks (use azure-databricks), Azure Stream Analytics (use azure-stream-analytics), Azure Data Explorer (use azure-data-explorer).
Use for all CEL and mito work on integrations that collect from APIs — writing CEL programs, cel.yml.hbs templates, manifest configuration, mock-first development with the mito CLI, system test mock setup, and answering CEL/mito questions. Load this skill whenever any data stream uses the cel input type.
Guide for creating effective skills. Use when you want to create a new skill (or update an existing skill) that extends an agent with specialized workflows, tool integrations, or repo conventions.