agent-production-operations
Operate an evaluated agent with tools and authority in production through a runtime control plane covering versioning, staged rollout, fallback, cost and latency budgets, tool health, human escalation, disablement, and trace-to-eval feedback. Do not use for building agents, designing evals, or general release, SRE, security, or platform engineering — those methods stay with their specialist skills.
magnus919 · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add magnus919/agent-skills --skill agent-production-operations技能说明
name: agent-production-operations description: >- Operate an evaluated agent with tools and authority in production through a runtime control plane covering versioning, staged rollout, fallback, cost and latency budgets, tool health, human escalation, disablement, and trace-to-eval feedback. Do not use for building agents, designing evals, or general release, SRE, security, or platform engineering — those methods stay with their specialist skills. license: MIT compatibility: Agent harness with file read/write and terminal access. No network or runtime dependency required by the bundle itself. metadata: spec-version: "1.0" tags: agent, production, operations, runtime, control-plane, rollout, fallback, disablement
agent-production-operations
A runtime control plane for taking an evaluated agent with tools and authority into controlled production operation. This bundle bridges the gap between passing evaluations and safe production use: it defines how an agent is versioned, rolled out, monitored, constrained, escalated, and disabled — and how production evidence feeds back into evaluation and release decisions.
The bundle does not build agents, design evaluations, run release pipelines, or own infrastructure. It composes those concerns from existing specialist skills and owns only the runtime control decisions between them.
When to load this
Load this bundle when you are operating an agent that:
- Has passed evaluation and is cleared for production consideration.
- Has tools with side effects and delegated authority that must be gated.
- Needs a staged rollout with progressive authority expansion.
- Must be monitored for cost, latency, tool health, and authority usage in production.
- Requires a defined fallback, escalation, and disablement path.
- Should feed production traces and incidents back into evaluation cases and release-gate updates.
When not to use
Do not load this bundle for:
- Building or designing an agent from scratch — route to the appropriate framework skill (LangGraph, CrewAI, AutoGen, etc.).
- Designing agent evaluations or observability — route to agent-evals-and-observability.
- General release engineering (CI/CD pipelines, artifact promotion) — route to release-engineering.
- General site reliability engineering (incident response, SLO definition, error budgets) — route to site-reliability-engineering.
- General security engineering (threat modeling, vulnerability assessment) — route to secure-software-engineering.
- General platform infrastructure (compute, networking, storage) — route to platform-engineering.
- Performing a production-readiness review — route to production-readiness; this bundle consumes readiness outcomes, it does not produce them.
- Conducting an incident postmortem — route to incident-learning; this bundle consumes incident records as escalation and feedback inputs.
Autonomy is not assumed uniform
This bundle explicitly does not assume all agents share the same autonomy, user population, or side-effect profile. Agent profiles are distinguished by capability class and side-effect surface:
| Profile | Example | Authority | Escalation trigger | Fallback |
|---|---|---|---|---|
| Read-only | Internal search agent | Query-only; no mutation, no user-data access | Uncertainty above threshold; result quality degradation | Return cached/static results |
| Side-effect-capable, internal | CI triage bot | Issue/PR comments, label management, branch creation | Tool failure > 5% in window; authority breach attempt | Disable tool, escalate to human |
| Side-effect-capable, customer-facing | Support agent with account access | Read PII, suggest actions, no mutation without confirmation | Any PII access without explicit consent; cost breach > 10% of budget | Degrade to read-only, escalate immediately |
Every control-plan decision (authority, escalation, fallback, disablement) in this bundle is parameterized by the agent's autonomy profile. A read-only agent and a side-effect-capable agent operating on customer data receive different thresholds and different escalation paths.
Runtime control plane routing
The bundle composes the following specialist skills. Load them when their domain is the active concern; the bundle owns the cross-domain coordination.
| Concern | Specialist skill | When to load | What the bundle adds |
|---|---|---|---|
| Agent evaluation and observability | agent-evals-and-observability | Designing evals, instrumenting observability, detecting regression | Trace-to-eval feedback loop; eval-case generation from production incidents |
| Release engineering | release-engineering | Release pipeline design, artifact promotion, CI/CD | Agent-specific staged rollout with authority gating; rollback triggers tied to agent health |
| Site reliability engineering | site-reliability-engineering | Incident response, SLO/SLI definition, error budgets | Agent-specific latency/cost budgets; tool-health SLOs; escalation handoff to incident command |
| Security engineering | secure-software-engineering | Threat modeling, trust-boundary validation, secure design | Agent authority contracts with side-effect boundaries; disablement security (revoke, not just stop) |
| Platform engineering | platform-engineering | Compute, networking, storage, service infrastructure | Agent sandboxing requirements; tool-execution isolation preferences |
| Production readiness | [production-readiness](../produc |