SkillVaultskills Browse all 1,000+ skills

Reliability · Version 1.2.0 · Reviewed 2026-08-02

Pulumi Observability Design Specialist

Reduce production risk in pulumi service-level signal design and pulumi diagnostic telemetry mapping with evidence, explicit trade-offs, and a verification plan.

4 method steps 6 documented failure modes 5 diagnostic checks 7 quality gates

Designs low-noise signals that expose user impact and causal mechanisms in Pulumi using infrastructure program, stack configuration, state, providers, and previews and preview operations, resource diffs, dependency graph, and provider logs, with explicit attention to nondeterministic program input or renamed logical identity replacing resources during deployment.

₹199 one-time

Get this skill archive

Install in your AI coding tool

SkillVault packages this skill in the open Agent Skills format for five leading coding tools.

What this skill helps you do

  • Pulumi service-level signal design
  • Pulumi diagnostic telemetry mapping
  • Pulumi actionable alert definition

How Pulumi Observability Design Specialist works

You provide

Current signals, alert rules, and recent incidents

It inspects

Symptom-versus-cause coverage for pulumi service-level signal design

It decides

A pulumi diagnostic telemetry mapping design with bounded label cardinality

You verify

Each page has a documented action and a real trigger

What it checks first

Pulumi Observability Design Specialist designs low-noise signals that expose user impact and causal mechanisms in Pulumi using infrastructure program, stack configuration, state, providers, and previews and preview operations, resource diffs, dependency graph, and provider logs, with explicit attention to nondeterministic program input or renamed logical identity replacing resources during deployment. Use it when the work involves Pulumi service-level signal design, Pulumi diagnostic telemetry mapping, Pulumi actionable alert definition.

  1. Every resource replacement in the plan, and whether that resource holds state that cannot be recreated.
  2. Address stability across refactors, since re-indexing destroys and recreates unrelated resources.
  3. Whether the executing principal has broader permissions than the change requires.
  4. Provider version pinning, because an unpinned upgrade introduces unrequested plan changes.
  5. Whether secrets appear in state, which is stored in plaintext regardless of the sensitive marker.

Failure modes it recognizes

  • An immutable attribute change silently forcing replacement of a database or stateful volume.
  • Moving resources between modules without move blocks, causing destroy-and-recreate.
  • A data source resolving at plan time to a value that changes before apply, producing inconsistency.
  • State lock held by a crashed run, blocking every subsequent apply until manually cleared.
  • A count-to-for_each conversion re-creating every resource because addresses changed.
  • Drift silenced with ignore_changes, which permanently disables reconciliation for that path.

Answers it will reject

  • Approving from the plan summary counts instead of reading every replacement line.
  • Using targeted applies to work around a broken dependency graph, leaving state partially applied.
  • Committing state files to version control, exposing secrets and creating infrastructure merge conflicts.
  • Granting the pipeline administrative rights so that any plan will succeed.

Decision rules it applies

  • Any replacement of a stateful resource requires a tested backup and restore path before approval.
  • Prefer move blocks over destroy-and-recreate for refactors; they preserve state and cost nothing.
  • Pin provider versions and upgrade deliberately so plan noise is attributable to intent.
  • If the plan cannot be explained line by line, it has not been reviewed.

Evidence it asks for

  • Export the plan as JSON and programmatically list every replace action.
  • Cross-check each replacement against an inventory of stateful resources.
  • Rehearse the change in a non-production environment carrying representative state.

The method inside

  1. Extract decisions, facts, and unresolved questions needed for pulumi service-level signal design.
  2. Organize pulumi diagnostic telemetry mapping around the reader's next decision or action rather than the source order.
  3. Draft pulumi actionable alert definition with source traceability and no invented behavior.
  4. Run a completeness, consistency, audience, and actionability review before returning the artifact.

Deliverables

  • Pulumi service-level signal design assessment
  • Pulumi diagnostic telemetry mapping decision and action plan
  • Pulumi actionable alert definition verification checklist

Evidence requirements

  • User-visible symptoms and SLO impact
  • Timeline, telemetry, deploys, and dependency state
  • Current mitigations and operational constraints

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Apply the observability design specialist to our Pulumi system before the next production change. We can provide infrastructure program, stack configuration, state, providers, and previews; the main concern is nondeterministic program input or renamed logical identity replacing resources during deployment.

Expected output

Instrument preview operations, resource diffs, dependency graph, and provider logs at the same boundary as the user-visible objective. The dashboard must make nondeterministic program input or renamed logical identity replacing resources during deployment distinguishable from ordinary load. Page only on symptoms that require action, retain causal dimensions within a bounded cardinality budget, and test every alert with a controlled failure.

Boundaries and compatibility

Ideal for

  • Pulumi service-level signal design: produce a decision or artifact grounded in supplied evidence.
  • Pulumi diagnostic telemetry mapping: produce a decision or artifact grounded in supplied evidence.
  • Pulumi actionable alert definition: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Replacing incident command authority
  • Calling a trigger the root cause without a causal chain

Agent compatibility

  • GitHub Copilot Agent Skills
  • Cursor Agent Skills
  • Claude Code Skills
  • OpenAI Codex Skills
  • JetBrains Junie Skills

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.