Skip to main content
skill CX Codex

platform-operations — Claude Code skill for CI/CD and observability

This skill turns release and monitoring requirements into a platform operations plan. Use it when designing CI/CD workflows, production observability, or release safeguards.

MIT ★ 587 updated 2026-10-26

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add rsmdt/the-startup
/plugin install team@the-startup
Open on GitHub

What platform-operations does

The skill reviews an existing build, release, and monitoring setup, then produces a platform operations plan. The plan covers pipeline stages, deployment approach, quality gates, rollback steps, observability, SLOs, and alerts. It also lays out prioritized rollout work.

Its workflow moves from assessing the current stack to designing delivery and reliability controls. Security and dependency checks belong in release gates, and production rollouts need staged verification. Rollback triggers should be set before release; SLO targets should follow observed baseline metrics.

Reference material covers deployment patterns, rollback and pipeline security, SLOs and alerting, and monitoring. It also points to Docker, deployment services, cloud platforms, and infrastructure-as-code tools. The skill produces guidance; it does not deploy the application for you.

What it helps with

  • map pipeline stages from build through post-deploy checks
  • choose a rollout method based on release risk
  • set triggers for production rollback
  • tie SLOs and alerts to observed metrics and response runbooks
  • spot gaps in release flow and production monitoring

Example prompts for the agent

  • Design a CI/CD and observability plan for my service running on AWS.
  • Suggest a canary rollout and define rollback triggers for this project.
  • Review our release workflow and propose quality gates, SLOs, and alert routing.

How to install platform-operations

1Plugin marketplace

/plugin marketplace add rsmdt/the-startup
/plugin install team@the-startup

This installs the whole team plugin with all its skills

2Skills CLI (Vercel)

npx skills add rsmdt/the-startup --skill platform-operations -a claude-code

3Manually: put the files in place

~/.claude/skills/platform-operations/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/platform-operations/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about platform-operations

How do I install platform-operations in Claude Code?

Add the marketplace with /plugin marketplace add rsmdt/the-startup, then install the plugin with /plugin install team@the-startup.

What does platform-operations do?

It assesses release and monitoring practices, then creates a plan covering pipeline stages, rollout strategy, quality controls, SLOs, alerts, and rollback.

How does the skill choose SLO targets?

It bases target recommendations on observed baseline metrics. The plan also connects alerts to actionable runbooks and clear ownership.

Source text

SKILL.md · MIT
---
name: platform-operations
description: Unified platform operations guidance for CI/CD pipeline design, deployment strategies, observability, SLI/SLOs, and incident-ready rollouts. Use when building release workflows, production monitoring, or reliability controls.
---

## Persona

Act as a platform operations architect who ensures delivery pipelines and production observability work as a single reliability system.

**Platform Ops Target**: $ARGUMENTS

## Interface

PlatformOpsPlan {
  pipelineStages: string[]
  deployStrategy: string
  qualityGates: string[]
  rollbackPlan: string[]
  observabilityPillars: string[]
  slos: string[]
  alerts: string[]
}

State {
  target = $ARGUMENTS
  baseline = {}
  plan = {}
}

## Constraints

**Always:**
- Build once, deploy everywhere using immutable artifacts.
- Include security and dependency checks as release gates.
- Define rollback triggers before production rollout.
- Tie alerts to actionable runbooks and clear ownership.
- Base SLO targets on observed baseline metrics.

**Never:**
- Deploy to production without staged verification.
- Alert on noisy/non-actionable internal-only signals when user symptoms are available.
- Skip health checks, post-deploy validation, or rollback capability.

## Reference Materials

- `reference/deployment-strategies.md` — Rolling, blue-green, canary, and feature-flag rollout patterns
- `reference/rollback-and-security.md` — Rollback mechanisms and pipeline security controls
- `reference/slo-and-alerting.md` — SLO calculation, error budgets, burn-rate alerting
- `reference/monitoring-patterns.md` — Metric types, distributed tracing, log aggregation, dashboard design
**Containerization:**
- [Docker](https://docs.docker.com/llms.txt) — Dockerfiles, multi-stage builds, Compose, image hardening, BuildKit, container networking

**Deployment Platforms:**
- [Railway](https://railway.com/llms.txt) — Nixpacks auto-build PaaS, managed Postgres/Redis, per-environment deploys, usage-based pricing
- [Vercel](https://vercel.com/llms.txt) — Edge-first frontend hosting, serverless functions, preview deployments, Next.js-native platform
- [Netlify](https://docs.netlify.com/llms.txt) — Jamstack hosting, Edge Functions, built-in form handling, framework-agnostic deploys
- [Render](https://render.com/llms.txt) — Managed web services, background workers, cron jobs, auto-scaling, private networking
- [Coolify](https://coolify.io/llms.txt) — Self-hosted PaaS alternative, deploy to own servers, 280+ one-click services, no vendor lock-in

**Infrastructure as Code & Cloud:**
- [AWS](https://docs.aws.amazon.com/llms.txt) — EC2, Lambda, ECS, S3, RDS, IAM, CloudFormation, full hyperscaler service catalog
- [DigitalOcean](https://docs.digitalocean.com/llms.txt) — Droplets, App Platform, managed Kubernetes, managed databases, Spaces object storage
- [Pulumi](https://www.pulumi.com/llms.txt) — IaC in TypeScript/Python/Go/C#, multi-cloud provider support, policy-as-code, state management
- [SST](https://sst.dev/llms.txt) — Full-stack IaC framework, AWS/Cloudflare native, live Lambda debugging, resource linking
- [Supabase](https://supabase.com/llms.txt) — Managed Postgres, auth, realtime subscriptions, edge functions, storage, vector embeddings

## Workflow

### 1. Assess Current State
- Identify existing pipeline platform, release flow, and monitoring stack.
- Identify reliability gaps: blind spots, flaky deploys, alert fatigue.

### 2. Design Delivery Flow
- Define build/test/analyze/package/deploy/verify stages.
- Select rollout strategy (rolling/canary/blue-green/flags) by risk profile.

### 3. Design Reliability Controls
- Define SLI/SLO/error budget policy.
- Define metrics/logs/traces correlation and alert routing.

### 4. Implement Safety Nets
- Enforce quality gates, approvals, automated rollback, and drift checks.

### 5. Deliver Platform Ops Plan
- Provide end-to-end pipeline + observability architecture and prioritized rollout steps.

© Rudolf S. · MIT · rsmdt/the-startup

Similar skills

All skills for DevOps and infrastructure →

From the same set50

The whole set →
design-visual design-visual — a design-systems subagent for Claude Code that establishes design tokens, component standards, and WCAG 2.1 AA accessibility foundations. CX Codex ★ 587repo stars research-product research-product — a subagent for Claude Code that transforms strategic uncertainty and vague requirements into prioritized decisions. Analyzes market and competitors, elicits and reconciles requirements, resolves stakeholder conflicts. CX Codex ★ 587repo stars feature-prioritization feature-prioritization applies RICE, MoSCoW, Kano, and value-effort frameworks to rank backlog items. Turns feature debates into structured decisions with documented rationale. CX Codex +1 ★ 587repo stars review-security review-security is a Claude Code subagent that checks code and dependency changes for vulnerabilities and supply-chain risks. It is automatically invoked for PRs affecting security-sensitive flows or dependency manifests. CX Codex ★ 587repo stars build-platform build-platform is a Claude Code subagent that orchestrates delivery platforms with containers, infrastructure as code, and deployment pipelines. It supports reproducible environments and rollback-safe releases. CX Codex ★ 587repo stars document Coordinates parallel documentation generation for source code, APIs, and project architecture. CX Codex +1 ★ 587repo stars api-contract-design api-contract-design is a Claude Code skill for designing and checking REST, GraphQL, or hybrid API contracts before implementation. CX Codex +1 ★ 587repo stars review-robustness review-robustness flags fragile code before merge: abstraction layers nothing needs yet, and shared state handled carelessly in async flows. Useful on PR review and for bugs that surface only under load. CX Codex ★ 587repo stars

Project sponsors

Companies that keep this analytics open