research-to-deploy
Researches infrastructure best practices and generates deployment-ready configurations, Terraform modules, Dockerfiles, and CI/CD pipelines. Use when the user needs to deploy services, set up infrastructure, or create cloud configurations based on current best practices. Trigger with phrases like "research and deploy", "set up Cloud Run", "create Terraform for", "deploy this to AWS", or "generate infrastructure configs".
What this skill does
# Research to Deploy Research infrastructure best practices and generate deployment-ready cloud configurations. ## Overview This skill bridges the gap between researching cloud infrastructure patterns and actually deploying them. Instead of spending hours reading documentation, comparing approaches, and manually writing configuration files, this skill automates the entire pipeline: it searches for current best practices on the target platform, synthesizes the findings into a coherent deployment strategy, and generates production-grade Infrastructure as Code (IaC) that you can review and apply directly. The skill supports multi-cloud deployments across GCP, AWS, and Azure, as well as platform-as-a-service providers like Railway, Fly.io, and Render. It generates Terraform modules by default but can also produce Pulumi programs, Docker Compose files, Kubernetes manifests, or platform-specific CLI commands. Every generated configuration includes security hardening, monitoring hooks, and cost optimization annotations based on the latest recommendations from the cloud provider. ## Instructions 1. **Describe what you want to deploy** and where: - "Research GCP Cloud Run best practices and deploy my Node.js API to staging" - "Set up a production Kubernetes cluster on AWS with monitoring" - "Create Terraform configs for a serverless Python function on Azure" 2. **Specify constraints** if you have them: - Budget: "keep monthly costs under $50" - Region: "deploy to us-central1" - Compliance: "needs HIPAA-compliant storage" - Existing infra: "we already use Terraform Cloud for state management" 3. **Let the skill research.** It will search for current documentation, community best practices, and known pitfalls for the specified platform and service. The research phase produces a summary of findings before generating any code. 4. **Review the research summary** and confirm the approach. The skill presents: - Recommended architecture with rationale - Cost estimate based on expected usage - Security considerations and mitigations - Alternative approaches that were considered 5. **Apply the generated configs** after review: - Terraform: `terraform init && terraform plan` - Docker: `docker compose up -d` - Kubernetes: `kubectl apply -f` ## Output The skill produces a structured set of deployment artifacts: - **Research Summary** (Markdown): A concise document covering the best practices found, architectural decisions made, and trade-offs considered. Includes source links. - **Infrastructure Code**: Terraform modules (`.tf` files), Dockerfiles, Kubernetes manifests, or platform-specific configs organized in a standard directory structure. - **CI/CD Pipeline**: GitHub Actions workflow or equivalent CI config that automates testing, building, and deploying the infrastructure. - **Monitoring Setup**: Configuration for health checks, alerting rules, and dashboards appropriate to the target platform (Cloud Monitoring, CloudWatch, or Datadog). - **Cost Estimate**: Annotated breakdown of expected monthly costs based on the chosen resources and expected traffic. - **Runbook** (Markdown): Step-by-step instructions for deploying, updating, rolling back, and troubleshooting the infrastructure. ## Examples ### Example 1: GCP Cloud Run Deployment **User:** "Research Cloud Run best practices and create a deployment for my Express API." The skill will: 1. Search for current Cloud Run documentation on container sizing, concurrency settings, min/max instances, and VPC connector patterns. 2. Generate a `Dockerfile` optimized for Cloud Run (multi-stage build, non-root user, health check endpoint). 3. Create `main.tf` with Cloud Run service, IAM bindings, custom domain mapping, and Cloud SQL connection. 4. Add a GitHub Actions workflow for automated deployment on push to `main`. 5. Include a `monitoring.tf` with uptime checks and alerting policies. ### Example 2: AWS ECS Fargate with Terraform **User:** "Deploy a Python microservice to ECS Fargate, keep costs minimal." The skill will: 1. Research Fargate Spot pricing, right-sizing strategies, and ALB vs API Gateway trade-offs. 2. Generate Terraform modules for VPC, ECS cluster, Fargate service, ALB, and ECR repository. 3. Configure auto-scaling based on CPU utilization with conservative thresholds for cost optimization. 4. Produce a cost estimate comparing Fargate vs Fargate Spot for the expected workload. ### Example 3: Kubernetes on Azure AKS **User:** "Set up a production AKS cluster with monitoring and RBAC." The skill will: 1. Research AKS best practices for node pool sizing, network policies, and Azure AD integration. 2. Generate Terraform for the AKS cluster, node pools, Azure Monitor workspace, and RBAC role assignments. 3. Create Kubernetes manifests for ingress controller, cert-manager, and Prometheus stack. 4. Include a runbook covering cluster upgrades, node pool scaling, and incident response. ## Error Handling - **Unknown platform:** Prompts the user to specify a supported cloud provider or platform. - **Insufficient context:** Asks clarifying questions about the application type, expected traffic, and budget before generating configs. - **Web search unavailable:** Falls back to built-in knowledge of common deployment patterns, noting that the recommendations may not reflect the latest documentation. - **Conflicting requirements:** Identifies trade-offs (e.g., "HIPAA compliance requires dedicated tenancy which increases costs beyond the $50 budget") and asks the user to prioritize. ## Prerequisites - Target cloud provider CLI authenticated (`gcloud`, `aws`, or `az`) - Terraform >= 1.5 installed (for IaC output) - Docker installed (for container-based deployments) - WebSearch and WebFetch tools enabled for best-practice research ## Resources - [Terraform Registry](https://registry.terraform.io/) — official provider and module documentation - [AWS Well-Architected Framework](https://aws.amazon.com/architecture/well-architected/) — cloud architecture best practices - [GCP Cloud Architecture Center](https://cloud.google.com/architecture) — reference architectures and patterns
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.