Loading...
Loading...
Found 73 Skills
Creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, and generates Terraform/Pulumi infrastructure templates. Handles deployment automation, GitOps configuration, incident response runbooks, and internal developer platform tooling. Use when setting up CI/CD pipelines, containerizing applications, managing infrastructure as code, deploying to Kubernetes clusters, configuring cloud platforms, automating releases, or responding to production incidents. Invoke for pipelines, Docker, Kubernetes, GitOps, Terraform, GitHub Actions, on-call, or platform engineering.
Logging, testing, cost hygiene, incident triage, and usage metrics for PubNub apps. Covers the correlation fields every send/receive must log, the test pyramid for real-time apps, payload + fan-out cost hygiene, the incident triage runbook, and PubNub usage metrics for billing reconciliation. Use during code reviews, when planning monitoring, when triaging incidents, or when investigating PubNub cost overruns.
Creates runbook.md for DevOps setup. L3 Worker invoked CONDITIONALLY when hasDocker detected.
ALWAYS USE THIS SKILL for anything involving Salesforce Archive (also called Trusted Services Archive) — search, view, unarchive, analyze, mask, and erase (RTBF) archived records via the Archive Connect API, and reading archive job status from the ArchiveActivity object. TRIGGER when: user mentions Salesforce Archive, Trusted Services Archive, archive/unarchive records, ArchiveActivity, archive jobs, archive policy, archive analyzer, archived record search, archive storage, archive failure logs, right to be forgotten / RTBF on archived data, or masking archived PII — including phrasings like 'find records that were archived', 'restore archived data', 'why did the archive job fail', 'download the archive failure log', or 'monitor my archive jobs', AND even when they ask you to explain, give guidance, or write a runbook/doc about these topics rather than run code. SKIP when: the user wants generic data-export/backup unrelated to the Archive add-on, or wants to build the archive policy UI metadata.
Create operational runbooks and standard operating procedures. Document troubleshooting guides and recovery procedures. Use when documenting operational knowledge.
Create or update living documentation from git history (branch diff, current branch, PR, or last N commits) for microservices. Use when users ask to document a feature/funcionalidad, document current branch/branch actual, generate release notes/changelog, explain what changed, or update docs for react, integrator, magento, or all services. Produces docs in each repo's docs/ folder (components, changelogs, adrs, runbooks, guides, technical, bugs, plans, tasks) with traceability to commits/files and Obsidian-compatible frontmatter.
Write a service catalog entry for a microservice or internal platform service — covering service identity, purpose, architecture context, SLAs, API contract summary, data classification, dependencies, operational runbooks, and known limitations. Use when asked to document a service for an internal developer portal, write a service README for a platform catalog, create a service overview page, or onboard a new service to a service registry. Produces a complete service catalog entry suitable for an internal developer portal or wiki.
Guides technical support engineering—customer ticket investigation, reproduction, log and API analysis, root-cause isolation, workaround communication, engineering escalation with evidence, and knowledge-base fixes for product bugs and integration issues. Use when debugging a customer-reported issue, writing a repro for engineering, analyzing API errors, drafting technical replies, or improving support runbooks—not for CS program design, renewals, or billing ops (customer-ops-specialist), production incident command (incident-management-engineer), building product features (fullstack-software-engineer), or company-wide crisis statements and launch announcements (communication-lead), or exec/VIP and community escalation program design (community-executive-escalations-program-manager). Product how-to, macros, and ticket triage without deep debugging: product-support-specialist.
Implement disaster recovery strategies and runbooks. Configure RPO/RTO targets and failover procedures. Use when planning for business continuity.
An engineering runbook — service overview, alerts table, dashboards links, common procedures with copy-pasteable commands, on-call rotation, and an incident-response checklist. Use when the brief mentions "runbook", "ops doc", "on-call guide", "SRE doc", or "运维手册".
Guides CI/CD for agent skills repositories and skill packages—pipeline design (build, test, validate, package), GitHub Actions for PR checks and release promotion, environment gates, secrets hygiene (no secrets in repo), skill-creator integration (quick_validate.py, package_skill.py), .skill artifact strategy, rollback, and operational runbooks for skill releases. Use when the user mentions CI/CD, CI/CD engineer, pipeline design, GitHub Actions, skill validation CI, package skills, release pipeline, deploy skills, PR checks, continuous integration, or skill release workflow—not application-only CI without skill packaging (devops), pre-flight plan go/no-go (build-validator), IDP or golden paths (platform-engineer), org-wide SLO and error-budget programs without pipeline ownership (site-reliability-engineer), or portfolio catalog governance without pipeline YAML (ai-skill-manager).
Transform infrastructure documentation, runbooks, and operational knowledge into reusable Claude Code skills. Convert Proxmox configs, Docker setups, Kubernetes deployments, and cloud infrastructure patterns into structured, actionable skills.