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
/plugin marketplace add rsmdt/the-startup
/plugin install team@the-startupWhat 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-startupThis installs the whole team plugin with all its skills
2Skills CLI (Vercel)
npx skills add rsmdt/the-startup --skill platform-operations -a claude-code3Manually: put the files in place
~/.claude/skills/platform-operations/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/platform-operations/
1Skills CLI (Vercel)
npx skills add rsmdt/the-startup --skill platform-operations -a codex2Manually: put the files in place
.agents/skills/platform-operations/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add rsmdt/the-startup --skill platform-operations -a cursor2Manually: put the files in place
.cursor/skills/platform-operations/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install rsmdt/the-startup plugins/team/skills/infrastructure/platform-operations2Manually: put the files in place
.github/skills/platform-operations/SKILL.md1Skills CLI (Vercel)
npx skills add rsmdt/the-startup --skill platform-operations -a gemini-cli2Platform CLI
gemini skills install https://github.com/rsmdt/the-startup --path plugins/team/skills/infrastructure/platform-operationsManually: put the files in place
.devin/skills/platform-operations/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
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