Skip to content
cccskills
FreePublished on GitHub

platform-operations

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.

The English summary is being prepared. Showing the original description.

rsmdt/the-startup575 stars(GitHub 575 + cccskills 0)

Run score Not tested

See how to install

Files included (5)

  • SKILL.md3.9 KB
  • reference/deployment-strategies.md3.3 KB
  • reference/monitoring-patterns.md10.3 KB
  • reference/rollback-and-security.md2.1 KB
  • reference/slo-and-alerting.md4.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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 — Dockerfiles, multi-stage builds, Compose, image hardening, BuildKit, container networking

Deployment Platforms:

  • Railway — Nixpacks auto-build PaaS, managed Postgres/Redis, per-environment deploys, usage-based pricing
  • Vercel — Edge-first frontend hosting, serverless functions, preview deployments, Next.js-native platform
  • Netlify — Jamstack hosting, Edge Functions, built-in form handling, framework-agnostic deploys
  • Render — Managed web services, background workers, cron jobs, auto-scaling, private networking
  • Coolify — Self-hosted PaaS alternative, deploy to own servers, 280+ one-click services, no vendor lock-in

Infrastructure as Code & Cloud:

  • AWS — EC2, Lambda, ECS, S3, RDS, IAM, CloudFormation, full hyperscaler service catalog
  • DigitalOcean — Droplets, App Platform, managed Kubernetes, managed databases, Spaces object storage
  • Pulumi — IaC in TypeScript/Python/Go/C#, multi-cloud provider support, policy-as-code, state management
  • SST — Full-stack IaC framework, AWS/Cloudflare native, live Lambda debugging, resource linking
  • Supabase — 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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Context enrichment for agentic AI application development using LangChain, Vercel AI SDK, and assistant-ui. Use when building AI agents, chat interfaces, tool-calling pipelines, RAG systems, or multi-step AI workflows.

The English summary is being prepared. Showing the original description.

rsmdt/the-startup575Updated Oct 25, 2026

Deep-research analysis of a codebase, a topic, or both. Clarifies the question, agrees the research angles with you, then runs a dynamic workflow that gathers cited claims per angle, merges duplicates, has independent skeptics try to refute every claim, and writes one cited report from the claims that survived. Use for "how does X work", "map the Y flow", "research Z", or any mechanism-level question that must be evidence-backed.

The English summary is being prepared. Showing the original description.

rsmdt/the-startup575Updated Oct 25, 2026

REST and GraphQL API design patterns, OpenAPI/Swagger specifications, versioning strategies, and authentication patterns. Use when designing APIs, reviewing API contracts, evaluating API technologies, or implementing API endpoints.

The English summary is being prepared. Showing the original description.

rsmdt/the-startup575Updated Oct 25, 2026

System architecture patterns including monolith, microservices, event-driven, and serverless, with C4 modeling, scalability strategies, and technology selection criteria. Use when designing system architectures, evaluating patterns, or planning scalability.

The English summary is being prepared. Showing the original description.

rsmdt/the-startup575Updated Oct 25, 2026

Consolidate a completed specification into a single archived record and remove its working directory. Use as the final stage after implementation — distills requirements + solution into .start/archive/[NNN]-[name].md and deletes the .start/specs/[NNN]-[name]/ directory.

The English summary is being prepared. Showing the original description.

rsmdt/the-startup575Updated Oct 25, 2026

Required first step before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation.

The English summary is being prepared. Showing the original description.

rsmdt/the-startup575Updated Oct 25, 2026

See all skills by rsmdt

Report a problem with this skill