Skip to content

dirien/yet-another-agent-harness / .claude/skills/pulumi-cli

pulumi-cli

Verified

Use for hands-on Pulumi CLI work: running deployments, fixing broken stacks, and managing infrastructure state. Handles: recovering from stuck or interrupted `pulumi up` with pending operations, cleaning orphaned resources from state after out-of-band cloud deletions, protecting critical resources from accidental `pulumi destroy`, moving resources between stacks without recreating them, targeting specific resources during deployment, migrating between backends (local file to Pulumi Cloud, S3), stack lifecycle management, state export/import/repair, CI/CD pipeline setup, and importing existing cloud resources. Use this skill — not the language-specific Pulumi skills — whenever the user's question is about operating, troubleshooting, or recovering Pulumi infrastructure rather than writing program code.

evals/evals.json

View on GitHub
{
  "skill_name": "pulumi-cli",
  "evals": [
    {
      "id": 1,
      "prompt": "My pulumi stack has a stuck pending create operation after a deploy was interrupted mid-way. The stack shows 'pending' operations when I try to run pulumi up again. How do I fix this and get back to a clean state without losing my existing resources?",
      "expected_output": "Step-by-step recovery using pulumi refresh, cancel, state repair, and backup/restore patterns",
      "files": [],
      "expectations": [
        "Recommends pulumi cancel or pulumi refresh --clear-pending-creates",
        "Mentions pulumi state repair as an option",
        "Suggests backing up state first with pulumi stack export --file",
        "Explains that pulumi refresh syncs state with actual cloud resources",
        "Does not suggest destroying the stack as first resort"
      ]
    },
    {
      "id": 2,
      "prompt": "I need to move an S3 bucket resource from my 'dev' stack to the 'staging' stack without destroying and recreating it in AWS. Walk me through the exact commands.",
      "expected_output": "Step-by-step using pulumi state move or export/import with URN identification",
      "files": [],
      "expectations": [
        "Shows how to identify the resource URN (pulumi stack --show-urns or export)",
        "Uses pulumi state move --source dev --dest staging with the URN",
        "Mentions backing up state before the operation",
        "Explains that the cloud resource is not affected by state operations",
        "Shows the URN format: urn:pulumi:<stack>::<project>::<type>::<name>"
      ]
    },
    {
      "id": 3,
      "prompt": "Set up a CI/CD pipeline configuration for Pulumi. I need the environment variables, the login command, and the deployment commands for a non-interactive GitHub Actions workflow that uses ESC for credentials.",
      "expected_output": "CI/CD setup with env vars, pulumi login, stack select, preview, up --yes, and ESC integration",
      "files": [],
      "expectations": [
        "Sets PULUMI_ACCESS_TOKEN environment variable",
        "Sets PULUMI_CI=true for CI mode",
        "Uses pulumi login for authentication",
        "Uses pulumi stack select to choose the target stack",
        "Runs pulumi preview before pulumi up",
        "Uses --yes flag for non-interactive deployment",
        "Shows ESC integration via pulumi config env add or pulumi env run"
      ]
    }
  ]
}
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall