pulumi
Manage cloud infrastructure with Pulumi using general-purpose programming languages. Use when tasks mention pulumi commands, Pulumi stacks, infrastructure as code in TypeScript/Python/Go/C#, or deploying with pulumi up.
What this skill does
# Pulumi ## Intent Router | Request | Reference | Load When | | --- | --- | --- | | Install tool, first-time setup, backend login | `resources/install-and-setup.md` | User needs to install Pulumi or configure backend | | Language choice, project layout, resource patterns | `resources/language-and-project.md` | User asks about supported languages or project structure | | Stacks, config, secrets | `resources/stacks-and-config.md` | User needs stack management, config values, or secrets | | CLI commands, workflows | `resources/command-cookbook.md` | User needs preview/up/destroy patterns or command reference | ## Quick Start ```bash # 1. Create a new project (prompts for language, cloud, stack) pulumi new aws-typescript # 2. Preview changes (no modifications made) pulumi preview # 3. Deploy changes pulumi up # 4. Destroy infrastructure (DANGEROUS — requires confirmation) pulumi destroy ``` ## Language Selection Pulumi supports multiple languages — choose based on your team's familiarity: | Language | Template prefix | Runtime needed | | --- | --- | --- | | TypeScript | `aws-typescript` | Node.js | | Python | `aws-python` | Python 3.8+ | | Go | `aws-go` | Go 1.21+ | | C# | `aws-csharp` | .NET 6+ | | Java | `aws-java` | JDK 11+ | | YAML | `aws-yaml` | None | ## Core Command Tracks - **New project:** `pulumi new <template>` — scaffold project with language/cloud - **Preview:** `pulumi preview` — show planned changes, no deployment - **Deploy:** `pulumi up` — create or update resources - **Destroy:** `pulumi destroy` — remove all stack resources - **Refresh:** `pulumi refresh` — sync state with actual cloud resources - **Stack ops:** `pulumi stack ls`, `pulumi stack select`, `pulumi stack output` ## Stack Concept A **stack** is a deployment target (e.g., `dev`, `staging`, `prod`). Each stack has its own config and state: ```bash pulumi stack init prod pulumi stack select dev pulumi config set aws:region us-west-2 pulumi up ``` ## Safety Guardrails - Always run `pulumi preview` before `pulumi up` — review resource diffs carefully. - `pulumi destroy` is **irreversible** — confirm the stack resource list before proceeding. - Use `pulumi config set --secret` for sensitive values (passwords, API keys). - Never commit Pulumi state files or unencrypted secret values. - Use stack policies (CrossGuard) to enforce organizational guardrails. ## Workflow 1. Select or create a stack: `pulumi stack select dev` 2. Set required config: `pulumi config set aws:region us-east-1` 3. Write or update program code. 4. Run `pulumi preview` and review the diff. 5. Run `pulumi up` to deploy. 6. Check outputs: `pulumi stack output` ## Related Skills - **terraform** — HCL-based IaC; Pulumi can import from Terraform state - **ansible** — configuration management for post-provision setup ## References - `resources/install-and-setup.md` - `resources/language-and-project.md` - `resources/stacks-and-config.md` - `resources/command-cookbook.md` - Official docs: <https://www.pulumi.com/docs/> - API / provider registry: <https://www.pulumi.com/registry/> - Tutorials: <https://www.pulumi.com/learn/> - Community: <https://www.pulumi.com/blog/>
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.