432 skills · sorted by relevance
MANDATORY deploy after every code change. Typecheck → deploy → purge CDN → E2E on production → visual verify → fix-forward loop. Workers Builds native CI/CD, D1 Time Travel PIT recovery, D1→R2 long-term backups, wrangler rollback, wrangler secrets management, structured observability, cross-browser smoke tests, rollback procedures, and GitHub auto-configuration.
The English summary is being prepared. Showing the original description.
Busabase-backed App-in-Skill dashboard for a shared LLM gateway's cost and model governance — daily spend trend, cost breakdown by service/model, a canary-rollout status board, and a deterministic cost/error anomaly list. Use when the user invokes $kelly-llm-gateway or /kelly-llm-gateway, or wants to review LLM gateway spend, model routing, canary rollouts, rollback readiness, or cost/error anomalies for services routed through one shared gateway to multiple LLM providers/models. Human actions (promote/rollback/hold a rollout, acknowledge an anomaly) write directly onto the route's own Busabase record — this skill never changes a real routing config.
The English summary is being prepared. Showing the original description.
Restore a thesis, sector, or macro note from a snapshot in _Archive/Snapshots/. Use when user says "rollback", "restore", "revert", "undo sync", or "go back to the previous version".
The English summary is being prepared. Showing the original description.
Prepare safe production launches — pre-launch checklist, monitoring, staged rollout, and rollback. Load when deploying to production, releasing a major change, opening beta access, or the user asks for a launch checklist, go-live plan, rollout strategy, or rollback plan. Not for local-only prototypes. Pairs with ci-cd-and-automation and app-security-hardening.
The English summary is being prepared. Showing the original description.
Large-scale data migrations with validation, rollback, and zero-downtime strategies. Activate on: data migration, database migration, zero-downtime migration, dual-write, backfill, cutover, data validation, schema migration. NOT for: schema evolution in streams (use schema-evolution-manager), API versioning (use api-versioning-backward-compatibility).
The English summary is being prepared. Showing the original description.
Safe database migration manager for zero-downtime DDL changes and rollback plans. Activate on: database migration, schema change, DDL, rollback plan, zero-downtime migration, Prisma migrate, Drizzle kit, Flyway, column rename, table alter. NOT for: query optimization (use database-optimizer), ORM modeling (use data-pipeline-engineer), backup/restore (use devops-automator).
The English summary is being prepared. Showing the original description.
Blue-green and canary deployment orchestrator with traffic shifting and automated rollback. Activate on: blue-green deployment, canary release, rolling deployment, traffic shifting, rollback automation, progressive delivery, Argo Rollouts, Flagger. NOT for: K8s manifest generation (use kubernetes-manifest-generator), CI/CD pipeline setup (use github-actions-pipeline-builder), monitoring (use monitoring-stack-deployer).
The English summary is being prepared. Showing the original description.
Prepare Cloud Worker images with tools already installed, select the new image, and verify startup timing and session placement. The workflow covers rollback when verification fails and removal of superseded images after explicit confirmation.
Assess the security of a machine running OpenClaw through read-only checks. Review remote access, firewall settings, updates, backups, disk encryption, and gateway exposure, then propose staged improvements with evidence and rollback guidance.
Write a pull request description that helps reviewers understand a code change. Use a compact diagram or diff, show before-and-after evidence, and explain how reversible the change is and what areas it may affect.
Map the impact of a proposed change using real dependencies and project documentation. Identify affected code, data, interfaces, tests, and release steps, then compare the implemented changes with the plan to expose gaps and unverified risks.
Plan database structure changes and existing data updates for production systems. Provides migration patterns for adding columns and indexes, switching applications in stages, and documenting recovery steps while accounting for downtime and database locks.
Plan database schema and data changes for production systems. Use staged column replacements, concurrent index creation, and batched data updates to limit disruption, with migration workflows for PostgreSQL, Prisma, Drizzle, Kysely, Django, and golang-migrate.
Test a plan before implementation through structured, challenging questions. Work through decisions in dependency order, receive recommendations with each question, and finish with a clear account of agreed choices, open issues, and scope.
Review Caveman Cloud experiment states, evaluation results, and safety checks to recommend a supported next action. Identify missing or failing evidence and explain execution blocks; the current agent interface reads experiment data without changing its lifecycle state.
Create a one-page service operations guide in HTML. It organizes service details, alerts and first responses, dashboard links, procedures with copyable commands, an on-call schedule, and an incident checklist so teams can find operational instructions together.
Evaluate substantial software changes against the actual problem, current system, and concrete users or components that need them. Choose a sufficient scope, assess consequences, and, when implementation is requested, make the change and verify its behavior.
Help design quorum management for distributed systems, where multiple nodes must agree on decisions. Covers adapting participation thresholds and voting weights to network conditions, performance, and failures, plus membership changes, validation, and rollback.
Coordinate multiple AI agents by adjusting their communication structure and task assignments as workloads change. The skill describes performance monitoring, switching coordination patterns, forecasting agent capacity, and validating changes with rollback when performance worsens.
Assess code change risk, locate complex areas, and inspect file statistics with ruflo analysis commands. The skill also guides running and extending ruflo’s regression guards, automated checks that help catch previously fixed problems.
Research existing code, documents, and relevant sources before producing a practical plan for implementation, migration, debugging, or evaluation. The plan explains key decisions, ordered steps, and validation checks, giving users something concrete to review before execution.
Design a process for AI agents to learn from execution records. Evaluate outcomes, actions, and quality, choose whether to update knowledge, instructions, code, or model parameters, and define independent validation, release checks, and rollback procedures.
Analyze campaign data across advertising platforms, check whether results are comparable, and assess costs and returns. Get budget test proposals with stated evidence, uncertainty, spending limits, and rollback criteria.
Plan and carry out major library and framework upgrades by checking compatibility, identifying changes that require code updates, testing each stage, and preparing rollback steps if an upgrade causes problems.