pulumi-component
Guide for authoring Pulumi ComponentResource classes. Use when creating reusable infrastructure components, designing component interfaces, setting up multi-language support, or distributing component packages.
38,472 Skills
搜索范围为本次公开目录;榜单和数量均为记录时的数据。
Guide for authoring Pulumi ComponentResource classes. Use when creating reusable infrastructure components, designing component interfaces, setting up multi-language support, or distributing component packages.
Query the Pulumi Context API, a graph query interface over an organization's infrastructure in Pulumi Cloud. Use when a question is about relationships or reachability across resources and stacks: the impact of a change ("what breaks if I change this?", blast radius), what depend
Debug a Pulumi update or preview that failed: read the failure Pulumi already recorded, find what caused it, and fix it. Load this skill when the user asks to debug, diagnose, or fix a failed update or preview, or points at a failing `pulumi up` or `pulumi preview`. Don't load it
Guidance for working with Pulumi ESC (Environments, Secrets, and Configuration). Use when users ask about managing secrets, configuration, environments, short-term credentials, configuring OIDC for AWS, Azure, GCP, integrating with secret stores (AWS Secrets Manager, Azure Key Va
Hand off the current thread to a new Pulumi Neo task as a one-way transfer. Use when the user explicitly asks to hand off, send, transfer, or continue current work in Pulumi Neo (e.g. "hand this to Neo", "continue in Neo", "/neo-handoff"). Do not load when the user only mentions
Migrate Terraform/OpenTofu projects to Pulumi, including translating HCL source code and/or importing Terraform state into a Pulumi stack. Use when a user wants to convert Terraform to Pulumi, migrate from HCL, or import tfstate into Pulumi. Do NOT trigger for general Terraform-v
Automate Pulumi provider repo upgrades with the `upgrade-provider` tool. Use when upgrading a pulumi provider repository to a new upstream version, running `upgrade-provider`, and addressing its common failure modes like patch conflicts or missing module mappings.
Create, amend, remove, and rebase patches for Terraform provider submodules using `./scripts/upstream.sh`. Use when `upgrade-provider` or manual patch work needs owning-patch lookup, patch conflict fixes, patch/hunk removal, or upstream rebase.
Use this skill to grade running ads as Red (stop), Yellow (hold), or Green (scale), detect creative fatigue, analyze LTV:CAC, and recommend scaling actions. Trigger it when reviewing campaign exports or deciding what to kill, keep, or scale.
Use this skill to turn ad concepts into HTML creative in cookie-cutter, ugly, meme, branded, or native styles, with optional Playwright screenshots. Trigger it when producing, varying, or iterating visual ad assets for testing.
Use this skill to identify and score acquisition channels by audience fit, speed, cost, effort, and learning value, then recommend the top three. Trigger it when choosing where to reach a defined audience, planning go-to-market, or replacing an underperforming channel.
Use this skill to discover and score online communities across Reddit, Slack, Discord, Facebook, LinkedIn, and independent forums. Trigger it when finding where a target audience gathers, planning organic participation, partnerships, or community-led go-to-market.
Use this skill to analyze what a competitor publishes, which content earns estimated traffic, the SEO plays they use, and where gaps exist. Trigger it before creating or refreshing a content strategy or when investigating a competitor's organic content performance.
Use this skill to find, verify, classify, and rank direct, adjacent, and tangential competitors from public web evidence. Trigger it when entering a market, building a competitor set, validating perceived alternatives, or refreshing research after a pivot.
Use this skill to map a competitor's organic search footprint with Keywords Everywhere ranking keywords, traffic estimates, and content-theme clusters. Trigger it when comparing SEO visibility, identifying competitor keyword strengths, or preparing deeper content-gap analysis.
目录记录日期:2026-11-21