3.8K skills · sorted by relevance
Set up product legal workflows through an interview about company context, review practices, and approval routes. Past launch reviews help establish which risks block release, while connector checks record which tracking and document services actually respond.
Build reusable Convex backend components with their own database tables and a small API, the functions an app calls. It guides component structure, app integration, authentication boundaries, and checks for generated code and type errors.
Help a spawned worker check which date-range helpers and external integrations are available and how to call them. The catalog explains environment settings, local broker access, and availability checks so the worker can choose tools for its task.
Review token contracts and the protocols that accept them for ERC20/ERC721 compliance, privileged controls, and unusual transfer behavior. Produces evidence-based risk assessments and prioritized fixes, with supply and holder analysis when deployed contract details are provided.
Write and run integration tests for GenLayer contracts in a running environment. Check agreement between the leader and validators, real web and LLM calls, and transaction execution results before deploying your contracts.
Use scGPT to convert single-cell gene expression data into numerical representations of cells and genes. These representations support clustering, data integration, cell-type annotation, and analyses of gene perturbations or regulatory relationships.
Design, debug, and tune OpenRouter API integrations. It checks model capabilities, reasoning settings, output limits, and fallback routes, then validates results against quality, cost, privacy, and performance requirements, including failed attempts.
Check which paid advertising integrations NotFair offers, connect ad accounts, and configure MCP connections for agent access. Verify available tools and whether a platform supports reading or changes, and investigate access problems.
Build the backend for an app modeled on an existing service, including login, database access rules, Stripe test payments, email, and integrations through official APIs. Track implementation and security checks in a dedicated checklist.
Compare feature requirements with existing code to identify missing capabilities and integration challenges. Evaluate extending current components, building new ones, or combining both, and save the findings to guide technical design.
Try NeMo Relay through a CLI wrapper, a supported integration, or direct Python, Node.js, or Rust instrumentation. Choose a minimal first run and verify recorded tool and model activity before considering one additional plugin.
Supervised and unsupervised multi-omics integration with mixOmics. Includes sPLS for pairwise integration and DIABLO for multi-block discriminant analysis. Use when performing supervised multi-omics integration or identifying features that discriminate between groups.
The English summary is being prepared. Showing the original description.
Migrate an Attio integration through a contract-led inventory, OpenAPI and documentation diff, shadow validation, canary rollout, reconciliation, and tested rollback. Use when endpoint assumptions, client versions, schemas, or integration architecture must change. Trigger with "upgrade Attio integration", "Attio migration", or "Attio API contract change".
The English summary is being prepared. Showing the original description.
Plan and execute a staged deployment for an external Attio REST integration with secret injection, contract tests, read-only smoke evidence, canary writes, and rollback. Use when releasing Attio-backed services. Trigger with "deploy Attio integration", "Attio rollout", or "Attio release plan".
The English summary is being prepared. Showing the original description.
Build a bounded CI contract gate for an Attio integration using fixtures, schema checks, and an optional read-only smoke request. Use when Attio changes need pull-request evidence without mutating CRM data. Trigger with "Attio CI", "test Attio integration", or "Attio pull request gate".
The English summary is being prepared. Showing the original description.
Deploy Apollo.io integrations to production. Use when deploying Apollo integrations, configuring production environments, or setting up deployment pipelines. Trigger with phrases like "deploy apollo", "apollo production deploy", "apollo deployment pipeline", "apollo to production".
The English summary is being prepared. Showing the original description.
Deploy Claude API integrations to production cloud environments. Use when deploying Claude-powered services to Docker, Cloud Run, ECS, or Kubernetes with proper secret management and health checks. Trigger with phrases like "deploy anthropic", "claude production deploy", "ship claude integration", "anthropic cloud deployment".
The English summary is being prepared. Showing the original description.
Deploy an Alchemy-backed service through environment-scoped credentials, chain assertions, canaries, and rollback gates. Use when promoting an integration to hosted environments. Trigger with "deploy Alchemy integration", "Alchemy production deploy", or "promote an Alchemy service".
The English summary is being prepared. Showing the original description.
Build a synthetic-data CI gate for customer-controlled Abridge integration code without calling undocumented vendor interfaces. Use when adding regression checks to an Abridge deployment repository. Trigger with "test the Abridge integration".
The English summary is being prepared. Showing the original description.
Deploy an Adobe-backed service or App Builder application with isolated environments, immutable artifacts, canaries, observability, and rollback. Use when the task requires adobe integration deployment. Trigger with "deploy Adobe integration", "aio app deploy", or "promote Adobe app".
The English summary is being prepared. Showing the original description.
Detect current high-risk Adobe integration traps before they become production incidents. Use when the task requires adobe integration pitfall review. Trigger with "Adobe pitfalls", "review Adobe integration", or "find obsolete Adobe code".
The English summary is being prepared. Showing the original description.
Design and build an official Apify integration for a company's product - workflow-automation apps (Zapier/n8n-style), AI agent plugins (coding-agent skills+MCP bundles or OpenClaw/Hermes-style harnesses), AI framework packages (LangChain/LlamaIndex-style), or direct application clients via apify-client. Use when planning, creating, or reviewing an integration that exposes Apify Actors, runs, datasets, or key-value stores inside another product.
The English summary is being prepared. Showing the original description.
Guides Metronome usage-based billing integration decisions — event ingestion (single and batch, idempotency, billable metrics), contract design (rate cards, overrides, dimensional pricing, products), invoicing lifecycle (grace periods, finalization, Stripe sync), credit and commit management (prepaid, postpaid, thresholds, auto-recharge), and Stripe integration (arrears invoicing, tax providers, line item limits). Use when building, modifying, or reviewing any Metronome integration — including ingesting usage events, creating customers, contracts, or rate cards, designing billable metric group keys, managing credits and commits, configuring invoicing, syncing invoices with Stripe Billing, billing AI applications for token usage, setting up self-serve (PLG) pricing, reviewing customer health, commit burn, portfolios, or renewals, or migrating from Stripe Billing Meters to Metronome.
The English summary is being prepared. Showing the original description.
Guides Stripe integration decisions across development and test environment planning (separate sandboxes vs the shared test mode sandbox), API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, tax and registrations (Stripe Tax, automatic_tax, product tax codes), Treasury financial accounts, integration options (Checkout, Payment Element), migrating from deprecated Stripe APIs, and security best practices (API key management, API key permissions, webhooks, OAuth). Use when planning, building, modifying, testing, or reviewing any Stripe integration, including choosing a development environment, accepting payments, building marketplaces, integrating Stripe, processing payments, setting up subscriptions, collecting sales tax, VAT, or GST, creating connected accounts, or implementing secure key handling.
The English summary is being prepared. Showing the original description.