Devops Engineer
Yikai-Liao/symusic
Creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, and generates Terraform/Pulumi infrastructure templates.
DevOps practices maturity assessment evaluating CI/CD, monitoring, incident response, automation, collaboration, and culture to produce a maturity scorecard with an improvement roadmap.
Install Devops Maturity Model
$ npx skills add FerroxLabs/wayland --skill devops-maturity-model -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install FerroxLabs/wayland devops-maturity-model --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/devops-cloud/devops-maturity-model .claude/skills/devops-maturity-model && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "devops-maturity-model" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/devops-cloud/devops-maturity-model into .claude/skills/devops-maturity-model/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "devops-maturity-model", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/devops-cloud/devops-maturity-modelType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add FerroxLabs/wayland --skill devops-maturity-model -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install FerroxLabs/wayland devops-maturity-model --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .agents/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/devops-cloud/devops-maturity-model .agents/skills/devops-maturity-model && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "devops-maturity-model" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/devops-cloud/devops-maturity-model into .agents/skills/devops-maturity-model/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "devops-maturity-model", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add FerroxLabs/wayland --skill devops-maturity-model -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install FerroxLabs/wayland devops-maturity-model --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/devops-cloud/devops-maturity-model .cursor/skills/devops-maturity-model && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "devops-maturity-model" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/devops-cloud/devops-maturity-model into .cursor/skills/devops-maturity-model/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "devops-maturity-model", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/FerroxLabs/wayland.git --path src/process/resources/skills-library/bodies/skills/devops-cloud/devops-maturity-model--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add FerroxLabs/wayland --skill devops-maturity-model -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install FerroxLabs/wayland devops-maturity-model --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/devops-cloud/devops-maturity-model .gemini/skills/devops-maturity-model && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "devops-maturity-model" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/devops-cloud/devops-maturity-model into .gemini/skills/devops-maturity-model/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "devops-maturity-model", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install FerroxLabs/wayland devops-maturity-modelInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add FerroxLabs/wayland --skill devops-maturity-model -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .github/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/devops-cloud/devops-maturity-model .github/skills/devops-maturity-model && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "devops-maturity-model" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/devops-cloud/devops-maturity-model into .github/skills/devops-maturity-model/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "devops-maturity-model", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add FerroxLabs/wayland --skill devops-maturity-model -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install FerroxLabs/wayland devops-maturity-model --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/devops-cloud/devops-maturity-model .opencode/skills/devops-maturity-model && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "devops-maturity-model" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/devops-cloud/devops-maturity-model into .opencode/skills/devops-maturity-model/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "devops-maturity-model", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
devops-maturity-model- GitHub stars
- 608
- Token cost
- ~3.7k tokens
- SKILL.md length
- 1,503 words
- Files
- 1
- Skills in repo
- 1,194
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
DevOps practices maturity assessment evaluating CI/CD, monitoring, incident response, automation, collaboration, and culture to produce a maturity scorecard with an improvement roadmap.
- Works in 5 steps: How many production deployments happen… → What is the lead time from code commit… → What percentage of deployments cause… → …
- The user asks about devops maturity model
- SKILL.md covers When to Use, Questions to Ask First, Assessment Framework and Scoring Template, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Devops Maturity Model is an agent skill from FerroxLabs/wayland. DevOps practices maturity assessment evaluating CI/CD, monitoring, incident response, automation, collaboration, and culture to produce a maturity scorecard with an improvement roadmap. Use when the user asks about devops maturity model, related techniques, best practices, or needs guidance in this domain. Do NOT use when the request is outside the scope of devops maturity model or requires a different specialized skill.
Its SKILL.md is about 3.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering CI/CD and Incident response. The repository describes itself as: Wayland - The AI Agent That Perceives. Reasons. Acts. Evolves. The licence is Apache-2.0.
When your agent uses it
- The user asks about devops maturity model
- Related techniques
- Needs guidance in this domain
- The request is outside the scope of devops maturity model
Example prompts
- “Use the devops-maturity-model skill to devop practices maturity assessment evaluating CI/CD, monitoring, incident response, automation…”
- “/devops-maturity-model”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- How many production deployments happen per week/month?
- What is the lead time from code commit to production?
- What percentage of deployments cause incidents or require rollback?
- How many environments exist (dev, staging, production)?
- What is the current deployment process (manual, semi-automated, fully automated)?
What it can do on your machine
Read from SKILL.md and the folder at commit 4c030c7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown and template).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Devops Maturity Model loads about 3.7k tokens when it runs. Until then it costs about 112 tokens; SKILL.md has 1,503 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from FerroxLabs/wayland at commit 4c030c7, republished under its Apache-2.0 licence (© FerroxLabs). 1,503 words, ~3,665 tokens.
Download SKILL.mdSave it as
.claude/skills/devops-maturity-model/SKILL.md (or your agent's skills folder).- name
- devops-maturity-model
- description
- DevOps practices maturity assessment evaluating CI/CD, monitoring, incident response, automation, collaboration, and culture to produce a maturity scorecard with an improvement roadmap. Use when the user asks about devops maturity model, related techniques, best practices, or needs guidance in this domain. Do NOT use when the request is outside the scope of devops maturity model or requires a different specialized skill.
- license
- Apache-2.0
- metadata.author
- foundry-skills
- metadata.version
- 1.0.0
- metadata.tags
- assessment devops template testing automation analysis planning
- metadata.category
- devops-cloud
- metadata.subcategory
- cloud-infrastructure
- metadata.disclaimer
- none
- metadata.difficulty
- intermediate
DevOps Maturity Model
You are a senior DevOps consultant specializing in organizational maturity assessments. Your role is to evaluate an organization's DevOps practices across continuous integration, continuous delivery, monitoring, incident management, automation, and culture to produce a structured maturity scorecard. You measure the reality of daily operations, not the aspirations in slide decks.
When to Use
Use this skill when:
- User asks about devops maturity model techniques or best practices
- User needs guidance on devops maturity model concepts
- User wants to implement or improve their approach to devops maturity model
Do NOT use when:
- The request falls outside the scope of devops maturity model
- User needs a different specialized skill for their specific situation
- The topic requires professional consultation beyond general guidance
Questions to Ask First
Delivery Context
- How many production deployments happen per week/month?
- What is the lead time from code commit to production?
- What percentage of deployments cause incidents or require rollback?
- How many environments exist (dev, staging, production)?
- What is the current deployment process (manual, semi-automated, fully automated)?
Team Context
- How many developers and operations engineers are on the team?
- Are development and operations separate teams or integrated?
- Who has access to deploy to production?
- Is there an on-call rotation? How is it structured?
- What is the average tenure of team members?
Tooling Context
- What source control system is used?
- What CI/CD tools are in place?
- What monitoring and alerting tools are used?
- What incident management tools are used?
- What infrastructure management tools are used?
Assessment Framework
Maturity Levels
Level 1: Initial - Processes are ad hoc and chaotic. Success depends on individual effort. Deployments are events. Operations is firefighting.
Level 2: Managed - Basic processes are established. Some automation exists. Deployments are planned. Monitoring covers basics. Siloed teams.
Level 3: Defined - Processes are documented and standardized. CI/CD is the norm. Monitoring is comprehensive. Teams collaborate regularly.
Level 4: Measured - Processes are measured and controlled. Data drives decisions. Proactive operations. Teams share ownership.
Level 5: Optimized - Continuous improvement culture. Innovation is rapid and safe. Operations is effortless. Engineering excellence is the norm.
Dimension 1: Continuous Integration (Weight: 15%)
| Score | Criteria |
|---|---|
| 1 | No CI. Developers integrate manually. Build-breaking commits are common. No automated tests. Integration is painful. |
| 2 | CI server exists. Builds trigger on commit. Some automated tests. Broken builds persist for hours. |
| 3 | CI runs on every PR. Comprehensive test suite. Builds must pass before merge. Build times <15 minutes. |
| 4 | Fast CI (<10 minutes). Parallel test execution. Code quality gates. Security scanning. Dependency checking. |
| 5 | CI is invisible and instant (<5 minutes). Trunk-based development. Pre-merge validation. Automated code review assistance. |
What to Evaluate
- CI pipeline existence and trigger configuration
- Build success rate over last 30 days
- Average build time
- Test coverage enforced in CI
- Code quality checks (linting, SAST, dependency scanning)
- Branch strategy and integration frequency
Dimension 2: Continuous Delivery and Deployment (Weight: 20%)
| Score | Criteria |
|---|---|
| 1 | Manual deployments. Deployment runbooks with 50+ steps. Deployments take hours. Downtime required. Deployments are stressful events. |
| 2 | Scripted deployments. Some automation. Deployment windows scheduled. 30-60 minutes per deployment. Some downtime. |
| 3 | Automated deployment pipeline. One-click or scheduled deployments. Zero-downtime for most services. Feature flags for risky changes. |
| 4 | Continuous delivery to staging. Push-button production deployment. Canary or blue-green deployments. Automated rollback on failure. |
| 5 | Continuous deployment to production. Multiple deployments per day. Progressive rollouts. Automated verification. Deployment is a non-event. |
What to Evaluate
- Deployment frequency (per day, week, month)
- Deployment automation level
- Deployment duration
- Downtime during deployment
- Rollback capability and speed
- Feature flag usage
- Deployment strategy (rolling, blue-green, canary)
Dimension 3: Monitoring and Observability (Weight: 15%)
| Score | Criteria |
|---|---|
| 1 | No monitoring. Problems discovered by users. No logs. No metrics. Flying blind. |
| 2 | Basic uptime monitoring. Server metrics (CPU, memory). Some application logs. Noisy alerts. |
| 3 | Application-level monitoring. Centralized logging. Meaningful alerts with runbooks. APM for key services. |
| 4 | Full observability (metrics, logs, traces). SLO-based alerting. Dashboards for all services. Anomaly detection. |
| 5 | Unified observability platform. Automated root cause analysis. Predictive alerting. Business metrics correlated with system metrics. |
What to Evaluate
- Infrastructure monitoring coverage
- Application Performance Monitoring (APM) coverage
- Log aggregation and search capability
- Distributed tracing implementation
- Alert quality (signal-to-noise ratio)
- Dashboard coverage and utility
- SLO/SLI definitions and tracking
Dimension 4: Incident Management (Weight: 15%)
| Score | Criteria |
|---|---|
| 1 | No incident process. Chaos during incidents. No on-call. No postmortems. Same incidents repeat. |
| 2 | Basic on-call exists. Ad hoc incident response. Some postmortems. No severity classification. |
| 3 | Defined incident process. Severity levels. On-call rotation with escalation. Postmortems for major incidents. |
| 4 | Structured incident command. Automated alerting and paging. Comprehensive postmortems. Action items tracked. MTTR <30 minutes. |
| 5 | Exemplary incident management. Automated remediation for known issues. Blameless culture. Chaos engineering. Learning from every incident. |
Key Metrics to Evaluate
- Mean Time to Detect (MTTD)
- Mean Time to Acknowledge (MTTA)
- Mean Time to Resolve (MTTR)
- Incident frequency by severity
- Postmortem completion rate
- Action item completion rate
- Repeat incident rate
Dimension 5: Infrastructure Automation (Weight: 15%)
| Score | Criteria |
|---|---|
| 1 | All infrastructure manual. Console clicks. Snowflake servers. No documentation. |
| 2 | Some scripts. Partial automation. Mix of manual and automated. Configuration drift. |
| 3 | Infrastructure as Code for most resources. Version controlled. Automated provisioning. |
| 4 | All infrastructure as code. Automated testing. Policy as code. Self-service provisioning. Drift detection. |
| 5 | Dynamic infrastructure. Auto-scaling. Self-healing. Zero-touch operations. Cost-optimized. |
Show full SKILL.md (613 more words)Show less
Dimension 6: Collaboration and Culture (Weight: 10%)
| Score | Criteria |
|---|---|
| 1 | Dev and Ops are adversaries. Blame culture. Knowledge silos. No shared goals. "Throw it over the wall." |
| 2 | Some collaboration on major projects. Shared Slack channels. Occasional joint meetings. Still "us vs them." |
| 3 | Cross-functional teams. Shared on-call. Joint planning. Blameless postmortems. Common tooling. |
| 4 | Full shared ownership. "You build it, you run it." Empathy across roles. Continuous learning. Psychological safety. |
| 5 | Engineering excellence culture. Everyone contributes to platform. Internal tech talks. Innovation time. Community of practice. |
Dimension 7: Security Integration (DevSecOps) (Weight: 10%)
| Score | Criteria |
|---|---|
| 1 | Security is a gate at the end. No automated scanning. Security team reviews sporadically. |
| 2 | Basic security scanning exists. Annual penetration tests. Security requirements are vague. |
| 3 | SAST/DAST in CI/CD pipeline. Dependency scanning. Security requirements in user stories. |
| 4 | Security champions in dev teams. Automated compliance checks. Threat modeling for new features. Container scanning. |
| 5 | Security is everyone's job. Continuous security validation. Automated policy enforcement. Bug bounty. Red team exercises. |
Scoring Template
Dimension Score (1-5) Weight Weighted
───────────────────────────────────────────────────────────────────
Continuous Integration [ ] x 0.15 = [ ]
Continuous Delivery/Deployment [ ] x 0.20 = [ ]
Monitoring and Observability [ ] x 0.15 = [ ]
Incident Management [ ] x 0.15 = [ ]
Infrastructure Automation [ ] x 0.15 = [ ]
Collaboration and Culture [ ] x 0.10 = [ ]
Security Integration (DevSecOps) [ ] x 0.10 = [ ]
───────────────────────────────────────────────────────────────────
TOTAL DEVOPS MATURITY SCORE [ ] / 5.0DORA Metrics Benchmark
Compare against industry benchmarks:
| Metric | Elite | High | Medium | Low |
|---|---|---|---|---|
| Deployment Frequency | On-demand (multiple/day) | Weekly-monthly | Monthly-quarterly | Quarterly-yearly |
| Lead Time for Changes | <1 hour | 1 day-1 week | 1 week-1 month | 1-6 months |
| Change Failure Rate | <5% | 5-10% | 10-15% | >15% |
| MTTR | <1 hour | <1 day | <1 week | >1 week |
Results Interpretation
| Score Range | Maturity Level | Interpretation |
|---|---|---|
| 4.5 - 5.0 | Level 5: Optimized | Engineering excellence. DevOps is a competitive advantage. |
| 3.5 - 4.4 | Level 4: Measured | Strong practices. Data-driven improvement. Minor gaps remain. |
| 2.5 - 3.4 | Level 3: Defined | Solid foundation. Practices are standardized. Ready to measure and improve. |
| 1.5 - 2.4 | Level 2: Managed | Basic processes in place. Significant automation and cultural gaps. |
| 1.0 - 1.4 | Level 1: Initial | Ad hoc operations. High risk. Urgent investment needed. |
Improvement Roadmap by Level
Level 1 to 2 (3-6 months)
- Set up CI for all repositories
- Automate the deployment process (even if not yet continuous)
- Implement basic monitoring and alerting
- Establish an on-call rotation
- Start doing postmortems for all outages
Level 2 to 3 (6-12 months)
- Achieve automated deployments for all services
- Implement comprehensive monitoring and centralized logging
- Define and enforce code quality gates in CI
- Standardize incident response process
- Move infrastructure to code
Level 3 to 4 (6-12 months)
- Implement canary or blue-green deployments
- Define SLOs and implement SLO-based alerting
- Track and improve DORA metrics
- Integrate security into CI/CD pipeline
- Build self-service infrastructure provisioning
Level 4 to 5 (12+ months)
- Achieve continuous deployment
- Implement chaos engineering
- Build automated remediation for common incidents
- Establish engineering excellence culture
- Optimize for developer experience and productivity
Report Template
# DevOps Maturity Assessment - [Team/Organization]
**Assessment Date**: [Date]
**Assessed By**: [Name/Role]
**Team Size**: [Number]
**Service Count**: [Number]
## Executive Summary
[2-3 sentences on overall maturity, key findings, and primary recommendation]
## Overall Maturity: Level [X] (Score: [X.X] / 5.0)
## DORA Metrics
| Metric | Current | Target | Industry Benchmark |
|--------|---------|--------|--------------------|
| Deployment Frequency | | | |
| Lead Time | | | |
| Change Failure Rate | | | |
| MTTR | | | |
## Dimension Scores
[Completed scoring table]
## Strengths
- [Top strengths]
## Improvement Areas
- [Top improvement areas]
## 90-Day Improvement Plan
1. [Initiative] - Owner: [person] - Expected outcome: [result]
2. [Initiative] - Owner: [person] - Expected outcome: [result]
## Next Assessment Date: [Date - recommend quarterly]Process
- Gather information. Ask the user clarifying questions to understand their specific situation, goals, and constraints
- Analyze context. Review the information provided and identify key factors relevant to devops maturity model
- Develop recommendations. Apply domain expertise to create actionable guidance tailored to the user's needs
- Present structured output. Deliver findings in the output format below with clear next steps
- Address follow-ups. Answer additional questions and refine recommendations based on feedback
Output Format
## Devops Maturity Model Analysis
### Assessment
[Key findings and observations]
### Recommendations
1. [Primary recommendation]
2. [Secondary recommendation]
3. [Additional suggestions]
### Action Items
- [ ] [First action step]
- [ ] [Second action step]
- [ ] [Follow-up task]Edge Cases
- Incomplete information: Ask clarifying questions before proceeding with recommendations
- Conflicting requirements: Prioritize the most critical constraint and note trade-offs
- Out of scope requests: Redirect to appropriate specialized skill or professional resource
- Beginner vs advanced: Adjust depth and terminology based on user's experience level
Example
Input: "Help me with devops maturity model for my current situation"
Output:
Based on your situation, here is a structured approach to devops maturity model:
- Assessment: Evaluate your current state and identify key areas for improvement
- Strategy: Develop a targeted plan based on best practices
- Implementation: Execute the plan with specific, measurable steps
- Review: Monitor progress and adjust as needed
© FerroxLabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in src/process/resources/skills-library/bodies/skills/devops-cloud/devops-maturity-model of FerroxLabs/wayland.
Open the folder on GitHubat commit 4c030c7
Compare with similar skills
Devops Maturity Model next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Devops Maturity Model this skillFerroxLabs/wayland | 608 | — | ~3.7k | Automated safety check: Pass | Apache-2.0 | |
| Devops EngineerYikai-Liao/symusic | 189 | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| TMDb Integration Failure Fixeradamayoung/TMDb | 178 | — | ~2.7k | Automated safety check: Pass | Apache-2.0 | |
| Release Itwondelai/skills | 2.4k | — | ~4k | Automated safety check: Pass | MIT | |
| Delivery Managerborghei/Claude-Skills | 874 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Cicd Playbookmohitagw15856/pm-claude-skills | 1.4k | — | ~2.9k | Automated safety check: Notes | MIT |
Similar skills
TMDb Integration Failure Fixer
adamayoung/TMDb
Diagnoses a failing scheduled TMDb Integration run, re-runs transient failures, and fixes real API drift on its own branch with a PR, merging it only when told to.
Release It
wondelai/skills
Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic.
Delivery Manager
borghei/Claude-Skills
Expert delivery management for release planning, deployment strategy, incident response, change management, SLA/error-budget tracking, and DORA metrics across continuous delivery pipelines.
Cicd Playbook
mohitagw15856/pm-claude-skills
Write a CI/CD pipeline playbook for a service or team. An agent skill from mohitagw15856/pm-claude-skills.
Docs Manuals
jh941213/my-cc-harness
Generate user manuals (Diátaxis) and operator manuals (runbooks, deployment guide, configuration reference, incident playbook).
More from FerroxLabs/wayland
All 1,194 skills in this repoStar Office Helper
FerroxLabs/wayland
Install, start, connect, and troubleshoot visualization companion projects for Aion/OpenClaw, with Star-Office-UI as the default recommendation.
Openclaw Setup
FerroxLabs/wayland
OpenClaw usage expert: Helps you install, deploy, configure, and use OpenClaw personal AI assistant.
Tvcontrol Setup
FerroxLabs/wayland
Set up TVControl end to end: install the connector, start TradingView Desktop with its control port open, load a watchlist export, add the indicators they use, and leave a working chart.
Ab Testing Specialist
FerroxLabs/wayland
End-to-end guide for designing, running, and analyzing A/B tests including experiment design, statistical significance, sample size calculation, common pitfalls, and advanced testing patterns.
Academic Writer
FerroxLabs/wayland
Complete academic writing guide covering thesis and dissertation structure, journal article format using IMRaD, literature review methodology, citation management, the peer review process, and…
Accessibility Auditor
FerroxLabs/wayland
Web accessibility expertise covering WCAG 2.2 conformance, audit methodology, ARIA patterns, keyboard navigation, screen reader testing, focus management, form accessibility, and automated vs manual…
Related
Categories
Questions about Devops Maturity Model
What does Devops Maturity Model do?
DevOps practices maturity assessment evaluating CI/CD, monitoring, incident response, automation, collaboration, and culture to produce a maturity scorecard with an improvement roadmap. Devops Maturity Model is an agent skill from FerroxLabs/wayland. DevOps practices maturity assessment evaluating CI/CD, monitoring, incident response, automation, collaboration, and culture to produce a maturity scorecard with an improvement roadmap.
When should I use Devops Maturity Model?
Devops Maturity Model fits situations like: the user asks about devops maturity model; related techniques; needs guidance in this domain; the request is outside the scope of devops maturity model.
How do I install Devops Maturity Model in Claude Code?
Run `npx skills add FerroxLabs/wayland --skill devops-maturity-model -a claude-code`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/devops-cloud/devops-maturity-model in FerroxLabs/wayland) into .claude/skills/devops-maturity-model in your project. Claude Code loads it when a task matches its description.
How do I install Devops Maturity Model in Codex?
Run `npx skills add FerroxLabs/wayland --skill devops-maturity-model -a codex`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/devops-cloud/devops-maturity-model in FerroxLabs/wayland) into .agents/skills/devops-maturity-model in your project. Codex loads it when a task matches its description.
Can I use Devops Maturity Model in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FerroxLabs/wayland --skill devops-maturity-model -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/devops-maturity-model, .gemini/skills/devops-maturity-model, .github/skills/devops-maturity-model and .opencode/skills/devops-maturity-model in your project.
What does Devops Maturity Model need to run?
SKILL.md names no scripts, command-line tools or credentials: Devops Maturity Model is instructions for the agent only.
Does Devops Maturity Model access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Devops Maturity Model safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Devops Maturity Model use?
Devops Maturity Model is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Devops Maturity Model use?
About 3.7k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Devops Maturity Model?
Skills that share tags, products or a category with Devops Maturity Model: Devops Engineer (Yikai-Liao/symusic, 189 stars), TMDb Integration Failure Fixer (adamayoung/TMDb, 178 stars), Release It (wondelai/skills, 2.4k stars) and Delivery Manager (borghei/Claude-Skills, 874 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Devops Maturity Model?
FerroxLabs (a GitHub user) maintains it in FerroxLabs/wayland, which has 608 GitHub stars. The repository holds 1,194 skills in this directory. The repository was last updated on October 6, 2026.
Source: FerroxLabs/wayland on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.