Loading...
Loading...
Found 9 Skills
Migrate Terraform projects to Pulumi. Use when users need to move infrastructure from Terraform to Pulumi, translate HCL configurations, or convert Terraform modules to Pulumi components.
Platform migration to Shopify — from WooCommerce, Magento, BigCommerce, data transfer, URL redirects
Migrate workloads from Google Cloud Platform to AWS — including AI and agentic workloads regardless of cloud provider. Triggers on: migrate from GCP, GCP to AWS, move off Google Cloud, migrate Terraform to AWS, migrate Cloud SQL to RDS, migrate GKE to EKS, migrate Cloud Run to Fargate, Google Cloud migration, migrate from OpenAI to Bedrock, move off OpenAI, switch from ChatGPT API to AWS, migrate from Gemini to Bedrock, migrate LangChain to Bedrock, migrate LangGraph to AWS, migrate agentic workloads to AWS, move AI workloads to AWS, migrate my AI app to AWS. Runs a 6-phase process: discover GCP resources from Terraform files, app code, or billing exports, clarify migration requirements, design AWS architecture, estimate costs, generate migration artifacts, and collect optional feedback. Clarify must finish before Design, Estimate, or Generate. Includes AI provider migration guidance (for example, OpenAI to Amazon Bedrock) by selecting closest-fit Bedrock model families for required modality, latency/quality targets, context windows, and cost constraints. Model mapping is compatibility-guided, not 1:1 parity; validate prompts, tool-calling behavior, and eval metrics before cutover. Do not use for: Azure or on-premises migrations to AWS, AWS-to-GCP reverse migration, general AWS architecture advice without migration intent, GCP-to-GCP refactoring, or multi-cloud deployments that do not involve migrating off GCP.
Guide for migrating to Polar from other payment platforms (Stripe Billing, Paddle, Lemon Squeezy, Gumroad). Use this skill when: (1) Planning a migration from another payment provider to Polar; (2) Migrating customer data and subscriptions; (3) Running parallel systems during transition; (4) Mapping products and pricing between platforms; (5) Handling payment method migration; (6) Communicating migration to customers; (7) Testing migration in sandbox before production.
Migrate workloads from Google Cloud Platform to AWS — including AI and agentic workloads regardless of cloud provider. Triggers on: migrate from GCP, GCP to AWS, move off Google Cloud, migrate Terraform to AWS, migrate Cloud SQL to RDS, migrate GKE to EKS, migrate Cloud Run to Fargate, migrate App Engine to Elastic Beanstalk, Google Cloud migration, migrate from OpenAI to Bedrock, move off OpenAI, switch from ChatGPT API to AWS, migrate from Gemini to Bedrock, migrate LangChain to Bedrock, migrate LangGraph to AWS, migrate agentic workloads to AWS, move AI workloads to AWS, migrate my AI app to AWS. Runs a 6-phase process: discover GCP resources from Terraform files, app code, or billing exports, clarify migration requirements, design AWS architecture, estimate costs, generate migration artifacts, and collect optional feedback. Clarify must finish before Design, Estimate, or Generate. Includes AI provider migration guidance (for example, OpenAI to Amazon Bedrock) by selecting closest-fit Bedrock model families for required modality, latency/quality targets, context windows, and cost constraints. Model mapping is compatibility-guided, not 1:1 parity; validate prompts, tool-calling behavior, and eval metrics before cutover. Do not use for: Azure or on-premises migrations to AWS, AWS-to-GCP reverse migration, general AWS architecture advice without migration intent, GCP-to-GCP refactoring, or multi-cloud deployments that do not involve migrating off GCP.
Use when migrating to another AI platform — exports all stored memories, context, preferences, and instructions so you can import them elsewhere
Expert in course platform selection and implementation - comparing Teachable, Kajabi, Thinkific, and custom solutions. Covers LMS selection criteria, platform migrations, tech stack decisions, and building vs buying. Use when "course platform, lms, teachable, kajabi, thinkific, course hosting, learning management system, which platform, " mentioned.
Guide for migrating forms from the legacy JsonForm/FormModel system to the new TanStack-based form system.
Guide users through Dynatrace upgrade from classic/2nd-gen to 3rd-gen. Assess tenant readiness, run tracking queries, identify migration actions for dashboards, entity queries, IAM, management zones, OpenPipeline, service detection, logs, K8s, RUM, synthetic, alerting. Includes cloud integration migration (AWS, Azure, GCP) from classic to new (Smartscape on Grail): connection discovery, metric mapping, and cutover. Keywords: upgrade, migrate, classic, gen3, phase2, phase3, readiness, cloud integration, AWS, Azure, GCP, classic connection, new connection, Smartscape on Grail, fleet management, Site Reliability Guardian (SRG), classic pipeline, log processing pipeline, bizevents pipeline, pipeline upgrade, classic processing rules, ActiveGate, authToken, auth token, DynaKube, dynatrace-operator, classicFullStack, Platform token, enable RUM on Grail, RUM migration, mobile RUM, web RUM, Experience Vitals.