Skip to content
Skills Library
DevOps & cloud · Learning & explanation

ops-quickref

/ops-quickref

AUTO-INVOKE when user mentions ops, runbook, inventory, audit trail, ops repo, sysops, devops, itops, infrastructure operations, fleet management. Ops framework quick reference — capability domains, extension model, and discovery phrases for runbooks, inventory, audit trail, verification.

Repository
aiwg ↗
Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 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.
Content35 / 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 26.10.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

AUTO-INVOKE when user mentions ops, runbook, inventory, audit trail, ops repo, sysops, devops, itops, infrastructure operations, fleet management. Ops framework quick reference — capability domains, extension model, and discovery phrases for runbooks, inventory, audit trail, verification.

Original author description

AUTO-INVOKE when user mentions ops, runbook, inventory, audit trail, ops repo, sysops, devops, itops, infrastructure operations, fleet management. Ops framework quick reference — capability domains, extension model, and discovery phrases for runbooks, inventory, audit trail, verification.

How it works

  1. Canonical access pattern: discover → show
  2. How to use this quickref
  3. What this framework is for
  4. Capability domains
  5. Curated discovery phrases
  6. Schemas
  7. Artifact directory layout
  8. Ops ecosystem (cross-workspace)
  9. When the curated phrases don't fit
  10. Anti-pattern: don't enumerate
Original SKILL.md headings · 134 lines, 812 words
SKILL.md preview
---
name: ops-quickref
namespace: aiwg
platforms: [all]
kernel: true
description: AUTO-INVOKE when user mentions ops, runbook, inventory, audit trail, ops repo, sysops, devops, itops, infrastructure operations, fleet management. Ops framework quick reference — capability domains, extension model, and discovery phrases for runbooks, inventory, audit trail, verification.
triggers:
  - "help with infra or servers"
  - "help me document and operate this infrastructure"
  - "pick a runbook inventory or audit path"
  - "ops runbook"
---

# Ops Framework — Quick Reference

This is your always-loaded directory for the AIWG **ops-complete** framework. It does **not** list every skill. The framework is small (2 base skills) but extends via `sys` / `it` / `dev` / `stream` extensions — discovery is how you find the extension surface.

## Canonical access pattern: discover → show

When you find a candidate via `aiwg discover`, fetch its body with `aiwg show <type> <name> --body`. **Never** use `find`, `ls`, `Glob`, or direct `Read` on `<provider>/skills/` paths — those reflect the kernel-pivot deploy state, not the full surface.

```bash
aiwg discover "<phrase>"             # find — returns ranked candidates
aiwg show skill <name> --body               # fetch — streams the SKILL.md body
```

If your platform's Skill tool errors on a non-kernel skill (expected — most aren't kernel), the fallback is `aiwg show`, never filesystem browsing. Last-resort if `aiwg` itself is broken: read directly from `$AIWG_ROOT/agentic/code/...` (the canonical corpus, always present).

## How to use this quickref

`aiwg show <type> <name>` returns a metadata card. Inspect its outline, then fetch a needed `--section "Heading"` or use `--body` for the full instructions. Fetch required rules with `--rules --with-rule-bodies` before governed work.

1. Identify the **capability domain** the user's need belongs to
2. Pick a **curated phrase** from that domain (or paraphrase the user's words)
3. Run `aiwg discover "<phrase>"` and surface the top match to the user

**Do not enumerate skills from memory.** The extension surface is large and only `aiwg list` + `aiwg discover` show what's actually installed.

## What this framework is for

Operational infrastructure scaffolding. Provides shared agents, schemas, templates, and rules for runbooks, fleet inventory, capability declarations, playbooks, and operational change. Designed to be extended with one or more of `sys` / `it` / `dev` / `stream` for domain-specific work.

## Capability domains

| Domain | Covers | Where it lives |
|---|---|---|
| **Base operations** | Audit trails, runbook step verification | `ops-complete` (always) |
| **Per-host / OS** | Hardware, OS, boot chains, fleet docs | `sys` extension |
| **IT / CMDB** | Asset management, service deployments, DR runbooks | `it` extension |
| **CI/CD** | Pipelines, build automation, fleet-wide tooling | `dev` extension |
| **Streaming infra** | Transcoders, platform integrations, key safety | `stream` extension |
| **Repository maintenance** | Role-aware issue triage, labels, closures, merges, releases, governance handoff | `repo-maintainer` extension |

## Curated discovery phrases

### Base operations

```bash
aiwg discover "ops audit trail"                # → ops-audit-trail
aiwg discover "ops verify"                     # → ops-verify
```

### Inventory & playbooks (schema-driven, framework-wide)

```bash
aiwg discover "ops inventory"                  # → ops (top-level command + related schemas)
aiwg discover "ops playbook"                   # → ops (playbook schemas)
```

### Extension-specific (after `aiwg use ops --ext <name>`)

```bash
# After --ext sys
aiwg discover "host profile"                   # → sys extension skills
aiwg discover "fleet inventory"                # → sys extension skills

# After --ext it
aiwg discover "DR runbook"                     # → it extension skills
aiwg discover "asset provisioning"             # → it extension skills

# After --ext dev
aiwg discover "CI builder pattern"             # → dev extension skills
aiwg discover "pipeline safety"                # → dev extension skills

# After --ext stream
aiwg discover "stream service deployment"      # → stream extension skills
aiwg discover "transcoder health"              # → stream extension skills

# After --ext repo-maintainer
aiwg discover "repo maintainer role-aware"      # → repo-maintainer
aiwg discover "triage issues with collaborator handoff"
```

## Schemas

ops-complete is **schema-driven**. Key YAML metalanguage schemas:

- `OpsInventory` — fleet inventory (hosts / services / capabilities)
- `OpsCapability` — capability declarations (what the fleet can do)
- `OpsPlaybook` — multi-step operational procedures
- `Runbook` — single-task documented procedures
- `IncidentReport` — structured incident write-ups
- `TroubleshootingGuide` — symptoms → diagnostics → fixes

When generating ops artifacts, validate against the schema (the framework ships schema files under `agentic/code/frameworks/ops-complete/schemas/`).

## Artifact directory layout

```
.aiwg/ops/
├── inventory/        # Fleet inventory snapshots
├── runbooks/         # Per-task runbooks
├── playbooks/        # Multi-step procedures
├── incidents/        # Incident reports
├── troubleshooting/  # Diagnostic guides
└── audit/            # Change/action audit trail
```

## Ops ecosystem (cross-workspace)

ops-complete is also part of the broader AIWG ops ecosystem managed via `aiwg ops`:

```bash
aiwg ops init --workspace <name> --ext sys,it,dev   # bootstrap workspace
aiwg ops adopt <path>                               # register a pre-cloned repo
aiwg ops discover <path> --register                 # auto-find orphaned clones
aiwg ops status / list / use / push                 # standard lifecycle
```

## When the curated phrases don't fit

```bash
aiwg discover "<your need, paraphrased>" --limit 5
```

If you don't see ops-related results, the user likely needs to install an extension (`aiwg use ops --ext sys` etc.).

## Anti-pattern: don't enumerate

If a user asks "what ops skills are available?", **do not list from this skill or memory**. Run:

```bash
aiwg list                           # show installed extensions
aiwg discover --type skill "<area>" # find specific skills
```

Versions

The database has no other skills named ops-quickref.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version b5caeabad6ef (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

  • 100sdlc-quickref
    AUTO-INVOKE when user mentions SDLC, requirements, architecture, ADR, use case, user story, test plan, phase gate, inception, elaboration, construction, transition, intake, deploy. SDLC framework quick reference — phase model, capability domains, and curated discovery phrases for aiwg discover.
  • 100ops-status
    OPS on-demand: This skill should be used when the user asks to \"ops status\", \"/ops:ops-status\", or \"are…
  • 100knowledge-base-quickref
    AUTO-INVOKE when user mentions knowledge base, wiki, KB, semantic memory, llm-wiki, knowledge ingest, document corpus. Knowledge-base framework quick reference — discovery phrases for KB ingest/health, semantic-memory kernel skills, llm-wiki profiles.
  • 100setup
    OPS on-demand: This skill should be used when the user asks to \"/ops:setup\", \"configure ops\", or…
  • 100devops-engineer
    DevOps Engineer role skill. Use when you need to produce a deployment guide, define release runbooks, plan infrastructure procurement, or document third-party service integration requirements for a release. Keywords: deployment, release guide, infrastructure, procurement,…
  • 95multivendor-fleet-ops
    Run read-only queries across multivendor device groups with explicit per-device outcomes. Use when the same operational question covers a fleet.

Feedback and reports

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