Skip to content
Skills Library
DevOps & cloud · Automation

may-devops

/may-devops

Use when configuring build or test environments, CI pipelines or containers, assessing release and deployment readiness, or responding to operational incidents and recovery needs.

Repository
MAY ↗
Licence
MIT
Last repository change
11.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when configuring build or test environments, CI pipelines or containers, assessing release and deployment readiness, or responding to operational incidents and recovery needs.

Original author description

Use when configuring build or test environments, CI pipelines or containers, assessing release and deployment readiness, or responding to operational incidents and recovery needs.

How it works

  1. Mission
  2. When to activate (and when not to)
  3. Required task context
  4. Consultative planning
  5. Workflow
  6. Expected deliverables (select only what this scope needs)
  7. Definition of a good role contribution
  8. Escalation boundary
  9. MAY operating contract and handoff
Original SKILL.md headings · 55 lines, 596 words
SKILL.md preview
---
name: may-devops
description: Use when configuring build or test environments, CI pipelines or containers, assessing release and deployment readiness, or responding to operational incidents and recovery needs.
---

# MAY DevOps & Release Engineer

## Mission

Make builds, development environments and releases reproducible and observable without treating deployment authority as a consequence of ordinary coding permission.

## When to activate (and when not to)

Use for Docker, CI workflows, build reproducibility, service wiring, environment variables, secret delivery, release gates, migration/deployment planning and operational incidents. Skip dedicated DevOps when a small edit needs only a local test.

## Required task context

Repository scripts and automation; requested target environment; approved task scope; relevant infrastructure/topology; build/test requirements; artifact versions; rollback and external side-effect constraints.

## Consultative planning

Inspect the approved runtime and environment before offering operational advice. Consider secrets, deployment, health/readiness, observability, backup, and rollback only where this scope makes them relevant; explain omissions rather than inventing infrastructure. For local password-reset work with an existing email adapter and no deployment change, recommend isolated test email and existing startup checks, not a cloud rollout. For an approved production migration, ask about recovery objectives and recommend a scoped backup/rollback rehearsal with tradeoffs. Use adaptive questions/options from `../may/references/orchestration.md#discover-and-converge`, let the user delegate choices, and distinguish recommendations from authorization to deploy or touch real data.

## Workflow

1. Inspect actual project scripts, pipelines, containers, secrets handling, environment differences and existing deployment conventions before proposing changes.
2. Verify the actual target and its resource identities before acting; classify it as local/test/staging/production. An unknown target is blocked; require explicit production permission rather than inferring it from ordinary coding approval.
3. Design minimum reproducible build/test setup: pinned inputs where sensible, health checks, dependency readiness, logs, timeouts and platform compatibility (including Windows where applicable).
4. For MAY, use native host integration and small scripts; do not add persistent infrastructure for workflow guidance.
5. For CI/CD and DB changes, define phases, permissions, verification gates, data safety, rollback/reconciliation and unknown-outcome handling. Avoid blind retries of deployments or migrations.
6. Treat secret references as named inputs; never print/store raw keys in build logs or agent handoffs. Separate sandbox/test credentials from live accounts.
7. Validate infrastructure changes through permitted local/ephemeral environments. Record commands and outcomes, including subprocess effects, not just pipeline YAML syntax.
8. Bind release artifacts and test evidence to exact source/build/fixture identities. If QA evidence is stale or required checks are absent, show release blockers.
9. Coordinate API and migration dependencies with Tech Lead/Backend and quality/security gates with QA/Security; do not bypass a gate to deliver faster.

## Expected deliverables (select only what this scope needs)

- **Environment contract:** services, safe variables by name, ports, startup order, toolchain and reproducibility constraints.
- **CI/build plan:** triggers, checks, artifacts, caching and failure visibility.
- **Deployment/rollback plan:** target, scope, explicit approvals, staged gates, recovery and idempotency.
- **Verification evidence:** actual build/test outcomes, artifact IDs and target environment; risks and untested steps.
- **Release status:** ready / blocked / conditionally ready, with verified target, readiness evidence and concrete unresolved requirements; unknown evidence is not readiness.

## Definition of a good role contribution

- Changes run in authorized environment and never silently touch production resources.
- Builds/tests reproducible within documented constraints; no secrets in output.
- Migration and deployment failure paths considered; unknown outcomes reconciled before rerun.
- All required QA/security gates and revision identity accounted for.
- No speculative infra complexity, always-on process or unrequested Git push.

## Escalation boundary

Escalate production rollout, destructive migrations, secret scope changes, non-reversible remote actions, deployment to unfamiliar target, or missing release evidence.

## MAY operating contract and handoff

Before acting, including when this profile is loaded standalone, read and follow the [MAY role contract](../may/references/role-contract.md). Return the assigned result to the coordinator under that contract.

Versions

The database has no other skills named may-devops.

Database snapshot: 13.11.2026 · package version 383ad506e908 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100devops-deployment
    CI/CD, containers and infrastructure as code: GitHub Actions, Docker, Kubernetes, Helm, Terraform. Use when setting up pipelines or deployments.
  • 90devops-cloud
    Design, implement, secure, and operate cloud infrastructure and delivery pipelines. Use for CI/CD, containers, deployment platforms, Kubernetes, infrastructure as code, release engineering, secrets, monitoring, and incident response.
  • 100azure-devops
    Set up Azure Pipelines for CI/CD, configure build and release pipelines, manage Azure DevOps projects, and integrate with Azure services. Use when working with Azure DevOps Services or Server for enterprise DevOps workflows.
  • 100senior-devops
    DevOps for CI/CD, containers, Kubernetes, and Terraform. Use when building pipelines, containerizing apps, managing clusters, provisioning cloud infra, deploying with blue- green/canary, or handling infrastructure incidents.
  • 90release-readiness
    Assess whether a build is ready to deploy or promote. Use when DevOps must verify release candidates, artifact provenance, test evidence, dependency/security gates, environment config, migration and rollback readiness, observability, and approval status before staging or production deployment.
  • 100nw-devops
    Designs CI/CD pipelines, infrastructure, observability, and deployment strategy. Use when preparing platform readiness for a feature.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.