devops

Guides DevOps—CI/CD pipelines, GitOps, release management, container delivery, observability, and SRE practices for build/deploy systems. Use when building or fixing pipelines, implementing GitOps, tuning alerts and SLOs, or managing on-call/incidents for delivery infrastructure—not for IDP/golden paths/developer portals (platform-engineer), raw VPC/IaC design (infrastructure-engineer), rollout cutover planning (deployment-strategist), security gates (devsecops), app features (senior-fullstack-developer), multi-team program coordination (technical-program-manager), or incident program design (severity, on-call, postmortems, paging integrations—incident-management-engineer). For Kubernetes cluster bootstrap, Helm releases, add-ons, and cluster-level debugging, use cluster-deployment-engineer. App latency profiling and load testing: performance-engineer. ML safeguard serving: ml-infrastructure-engineer-safeguards. RL training platform jobs: ml-systems-engineer-rl-engineering.

Jump to install

Repository: daemon-blockint-tech/Agentic-Enteprises-Skill
Last source activity: May 20, 2026 at 01:05
Detected SKILL.md language: English
Stars: 7
Forks: 1

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/daemon-blockint-tech/Agentic-Enteprises-Skill --skill devops

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

6 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

ab-testing-engineer

Guides experimentation engineering for A/B and multivariate tests—hypothesis framing, primary/secondary/guardrail metrics, design (A/B, A/B/n, MVT), sample size and power, duration and seasonality, allocation and randomization units, SRM checks, instrumentation, analysis plans (frequentist and Bayesian workflow level), stopping rules, readouts, rollout/kill decisions, and experiment registry hygiene (sound statistical practice only). Use for "A/B test", "A/B testing engineer", "experiment design", "sample size calculator", "statistical significance", "power analysis", "split test", "experiment readout", "guardrail metrics", "SRM", "randomization unit", "experiment duration", "multivariate test", "holdout", or "experiment analysis". Not for analytics stack build (analytics-data-engineer), marketing copy (cmo-advisor), roadmap-only (cpo-advisor), ML model experiments (ml-research-engineer-safeguards), or privacy/legal review (compliance-engineer).

2026-05-20

actuarial-analyst

Guides hands-on actuarial analyst work for insurance, reinsurance, and pension—reserving and loss development (IBNR, triangles, chain-ladder diagnostics), pricing and rate indication support (experience, trend, credibility, basic GLM at spec level), data validation and model I/O review, reporting packs and workpapers, assumption application under actuary direction, and statutory tie-outs at analyst depth. Use when the user mentions actuarial analyst, loss development, IBNR, reserve analysis, rate indication, pricing support, actuarial workpaper, triangle analysis, credibility, experience study, actuarial reporting, or reserve roll-forward—not actuary sign-off (actuary), consulting engagements (actuarial-consulting), assumption governance (assumption-setting), ALM strategy (asset-liability-management), P&C legal depth (property-casualty-insurance), charts only (data-visualization), or ETL-only pipelines (data-scrubbing).

2026-05-20

actuarial-consulting

Guides actuarial consulting engagements—client scoping and SOW design, stakeholder communication (CFO, risk, boards, regulators at overview level), due diligence and M&A actuarial support, reserving/pricing/capital review programs, model validation and opinion support, regulatory interaction prep, and deliverable governance (memos, exhibits, management presentations). Use when the user mentions actuarial consulting, actuarial engagement, reserve opinion, due diligence actuarial, model validation engagement, actuarial memo, SOW actuarial, regulatory actuarial, M&A reserves, or actuarial review—not deep technical modeling execution (actuary), P&C line education only (property-casualty-insurance), legal advice (commercial-counsel), or generic management consulting without actuarial lens (business-consultant).

2026-05-20

View all from this repository

name

devops

description

DevOps

When to Use

Build, fix, or optimize CI/CD pipelines and release automation
Implement GitOps, artifact promotion, container delivery, or environment automation
Set up service observability, SLOs, alerting, and runbooks for delivery infrastructure
Operate on-call workflows for build, deploy, and runtime reliability issues
Standardize deployment mechanics for application teams

When NOT to Use

Design rollout strategy, cutover, rollback triggers, or release risk tiers → deployment-strategist
Build internal developer portals, golden paths, or platform-as-product roadmaps → platform-engineer
Provision core cloud networks, IAM, or Terraform modules as the main task → infrastructure-engineer
Add security gates, SBOMs, artifact signing, or CI threat modeling → devsecops
Design SEV programs, paging policy, or postmortem process → incident-management-engineer
Deep SLO/error-budget program, PRR, reliability engineering per service → site-reliability-engineer

Related skills

Need	Skill
SLOs, error budgets, PRR, reliability ownership	`site-reliability-engineer`
Cloud VPC, IAM, Terraform modules	`infrastructure-engineer`
Managed cloud services and networking	`cloud-engineer`
SAST, SBOM, OIDC hardening, pipeline security	`devsecops`
Data pipeline SLAs and warehouse ops	`data-system-ops-lead`
App code, APIs, UI	`senior-fullstack-developer`
Rollout strategy, cutover plans, change tiers	`deployment-strategist`
IDP, golden paths, developer portal, platform APIs	`platform-engineer`
Cross-team milestones, RAID, launch council	`technical-program-manager`
SEV model, on-call program, postmortem process	`incident-management-engineer`
K8s cluster deploy and operations	`cluster-deployment-engineer`
App profiling, load tests, perf regression	`performance-engineer`

Core Workflows

1. CI/CD pipeline design

Standard stage order:

checkout → lint/test → build → publish artifact → deploy non-prod → integration/e2e → promote prod

Checklist:

Pipeline as code in repo; versioned with application
Reproducible builds (locked deps, pinned base images)
Parallelize independent jobs; cache dependencies
Artifact immutability (digest, not floating tag)
Manual or policy gate before production
Rollback path documented and tested quarterly

See references/cicd_releases.md for GitHub Actions, GitLab CI, and deployment patterns.

2. GitOps and environments

Declare desired state in git (Helm, Kustomize, Terraform for apps)
Sync via Argo CD or Flux; drift detection enabled
One branch or path per environment; promotion via PR
Secrets never in git—use External Secrets / sealed secrets
Audit sync events and failed reconciliations

See references/gitops_environments.md for promotion flows and config layering.

3. Observability and SRE

Minimum observability per service:

Signal	What to capture
Metrics	RED/USE: rate, errors, duration, saturation
Logs	Structured JSON, correlation ID, no secrets
Traces	Critical paths and cross-service calls

SLO workflow: pick SLI → set target and error budget → alert on burn rate → review in weekly ops.

See references/observability_sre.md for SLI examples, alert hygiene, and runbook links.

4. Incident and on-call

Triage severity (customer impact, data risk)
Mitigate (rollback, scale, feature flag)
Communicate status on cadence
Post-incident review within 48h for SEV1–2
Track action items to closure

See references/incident_oncall.md for severity matrix and handoff template.

5. Developer platform (optional)

Golden paths: template repos, standard pipelines, local dev parity
Self-service environments with guardrails
Cost and quota visibility per team

See references/platform_engineering.md for IDP scope and build-vs-buy.

When to load references

Pipelines and releases → references/cicd_releases.md
GitOps and env promotion → references/gitops_environments.md
Metrics, SLOs, alerts → references/observability_sre.md
Incidents and on-call → references/incident_oncall.md
Internal developer platform → references/platform_engineering.md

devops

Source facts

Install options

Review the source files

More from this repository

More from this repository

DevOps

When to Use

When NOT to Use

Related skills

Core Workflows

1. CI/CD pipeline design

2. GitOps and environments

3. Observability and SRE

4. Incident and on-call

5. Developer platform (optional)

When to load references

DevOps

When to Use

When NOT to Use

Related skills

Core Workflows

1. CI/CD pipeline design

2. GitOps and environments

3. Observability and SRE

4. Incident and on-call

5. Developer platform (optional)

When to load references