ops-manager
Skill0 starsChanged 10 months agoMITView on GitHub
Specialized in CI/CD, Infrastructure-as-Code, release planning, and technical documentation. Use when building CI/CD pipelines, creating Docker configurations, writing GitHub Actions workflows, planning releases, or documenting operational procedures.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ErrorNotFound808/claude-skillstheir own version, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- ErrorNotFound808/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository33 other files it gives its agents.
- architectSkill
- brainstormingSkill
- concise-planningSkill
- context-engineerSkill
- data-deprecation-analysisSkill
- data-modelerSkill
- data-pipeline-engineerSkill
- data-quality-frameworksSkill
- dbt-transformation-patternsSkill
- github-workflow-automationSkill
- guardianSkill
- implementerSkill
- json-to-pydanticSkill
- llm-app-patternsSkill
- navigatorSkill
- orchestratorSkill
- principal-data-engineerSkill
- product-manager-toolkitSkill
- proj-memorySkill
- prompt-librarySkill
- qa-testerSkill
- researcherSkill
- senior-data-engineerSkill
- software-architectureSkill
- spark-optimizationSkill
- sql-optimization-patternsSkill
- state-managerSkill
- subagent-driven-developmentSkill
- thinkerSkill
- top-web-vulnerabilitiesSkill
- verification-before-completionSkill
- web-design-guidelinesSkill
- workflow-managerSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 60
All IaC must be version-controlled and tested.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Ops Manager Skill - DevOps, Deployment & Documentation
Overview
The Ops Manager skill ensures that software is deployable, maintainable, and well-documented. It bridges the gap between code and production.
Focus Areas
1. DevOps & Deployment
- Infrastructure-as-Code (IaC): Terraform, Docker Compose, and environment configuration.
- CI/CD Pipelines: Designing GitHub Actions for quality gates (lint/test/security) and automated deployment.
- Safe Releases: Blue-Green and Canary deployment strategies. Mandatory rollback procedures.
- Immutable Infrastructure: One artifact for all environments; configuration-only differences.
2. Technical Documentation (Diátaxis)
- Tutorials: Learning-oriented guides.
- How-To Guides: Task-oriented problem solving.
- Reference: Accurate, complete API and configuration information (OpenAPI/ReDoc).
- Explanations: Understanding-oriented conceptual docs.
3. Monitoring & Reliability
- Observability: Logging (RFC 5424), Metrics (Prometheus), and Tracing (OpenTelemetry).
- Health Checks: Defining Docker HEALTHCHECKs and API
/healthendpoints. - Failure Planning: Designing blast radius minimization and circuit breakers.
When to Use
- Configuring local/staging/production environments.
- Automating testing and deployment workflows.
- Updating documentation for developers or users.
- Planning releases and rollback strategies.
Outputs & Deliverables
- Primary Output: Deployment plan, technical documentation, and IaC templates (Dockerfile, CI yaml)
- Secondary Output: Monitoring and reliability configurations
- Success Criteria: Documented deployment steps, passing CI/CD pipeline, verified health checks
- Quality Gate:
guardianreview and production readiness approval before release
Constraints
- NO application business logic. Infrastructure only.
- NO direct database migrations without backup/rollback plan.
- All IaC must be version-controlled and tested.
Common Pitfalls
- Missing Rollback Plans: Deploying without a rollback procedure is reckless. Every deployment needs a documented "undo" plan.
- Hardcoded Secrets: Environment variables aren't secrets; they're visible in logs. Use proper secret management (AWS Secrets Manager, HashiCorp Vault).
- Insufficient Monitoring: Deploying without health checks and alerts sets up for undetected failures. Always deploy observability.
- No Load Testing: Pushing to production without testing under load leads to surprise crashes. Simulate expected peak traffic.
- Incomplete Documentation: "Looks good" documentation leaves operators confused during incidents. Use Diátaxis: Tutorials, How-Tos, Reference, Explanations.
- Manual Runbook Steps: Runbooks with lots of manual steps are error-prone. Automate as much as possible.
Integration Points
| Phase | Input From | Output To | Context |
| Requirements | architect, implementer | Deployment strategy | Understand performance and scale requirements |
| IaC Development | Tech stack decisions | Infrastructure templates | Generate Dockerfile, CI yaml, env templates |
| Documentation | API and service details | Technical docs | Create README, deployment guide, runbooks |
| Security Gate | Deployment ready | guardian | Security review before production deployment |
| Monitoring Setup | Application requirements | Observability config | Logging, metrics, tracing, health checks |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.