# Send Production Readiness to your agent
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
## Fast path
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
## Suggested prompts
### New install

```text
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
```
### Upgrade existing

```text
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
```
## Machine-readable fields
```json
{
  "schemaVersion": "1.0",
  "item": {
    "slug": "production-readiness",
    "name": "Production Readiness",
    "source": "tencent",
    "type": "skill",
    "category": "开发工具",
    "sourceUrl": "https://clawhub.ai/wpank/production-readiness",
    "canonicalUrl": "https://clawhub.ai/wpank/production-readiness",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadUrl": "/downloads/production-readiness",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=production-readiness",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "packageFormat": "ZIP package",
    "primaryDoc": "SKILL.md",
    "includedAssets": [
      "README.md",
      "SKILL.md"
    ],
    "downloadMode": "redirect",
    "sourceHealth": {
      "source": "tencent",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-04-30T16:55:25.780Z",
      "expiresAt": "2026-05-07T16:55:25.780Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
        "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"",
        "redirectLocation": null,
        "bodySnippet": null
      },
      "scope": "source",
      "summary": "Source download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this source.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/production-readiness"
    },
    "validation": {
      "installChecklist": [
        "Use the Yavira download entry.",
        "Review SKILL.md after the package is downloaded.",
        "Confirm the extracted package contains the expected setup assets."
      ],
      "postInstallChecks": [
        "Confirm the extracted package includes the expected docs or setup files.",
        "Validate the skill or prompts are available in your target agent workspace.",
        "Capture any manual follow-up steps the agent could not complete."
      ]
    }
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/production-readiness",
    "downloadUrl": "https://openagent3.xyz/downloads/production-readiness",
    "agentUrl": "https://openagent3.xyz/skills/production-readiness/agent",
    "manifestUrl": "https://openagent3.xyz/skills/production-readiness/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/production-readiness/agent.md"
  }
}
```
## Documentation

### Production Readiness (Meta-Skill)

Coordinates all operational concerns into a single readiness review. Instead of duplicating domain expertise, this skill routes to specialized skills and agents for each area, then synthesizes results into a unified go/no-go assessment.

### OpenClaw / Moltbot / Clawbot

npx clawhub@latest install production-readiness

### Purpose

Ensure a service is production-ready by systematically checking every operational concern — logging, error handling, performance, security, deployment, testing, and documentation — before traffic hits it.

A production-ready service:

Fails gracefully under load and partial outages
Observes itself with structured logs, metrics, and traces
Recovers automatically from transient failures
Communicates health to orchestrators and operators
Documents operations so on-call engineers can respond without tribal knowledge

### When to Use

TriggerContextBefore first deployNew service going to production for the first timeBefore major releaseSignificant feature or architectural change shippingQuarterly production reviewScheduled audit of existing servicesAfter incidentPost-incident hardening to prevent recurrenceDependency upgradeMajor framework, runtime, or infrastructure changeTeam handoffTransferring ownership of a service to another team

### Orchestration Flow

Run each area sequentially or in parallel. Each step delegates to a specialized skill or agent — this skill does not re-implement their logic.

┌─────────────────────────────────────────────────┐
│              Production Readiness Review         │
├─────────────────────────────────────────────────┤
│                                                  │
│  1. Logging & Observability ──► logging-observability skill
│  2. Error Handling ───────────► error-handling-patterns skill
│  3. Performance ──────────────► performance-agent
│  4. Security ─────────────────► security-review meta-skill
│  5. Deployment ───────────────► deployment-agent + docker-expert skill
│  6. Testing ──────────────────► testing-workflow meta-skill
│  7. Documentation ────────────► /generate-docs command
│                                                  │
│  ──► Synthesize results into go/no-go report     │
└─────────────────────────────────────────────────┘

### Step Details

Logging & Observability — Structured logging, log levels, correlation IDs, metrics endpoints, distributed tracing, alerting rules
Error Handling — Global error boundaries, retry policies, dead-letter queues, error classification, user-facing error messages
Performance — Load testing results, P95/P99 latency baselines, memory/CPU profiling, database query analysis, caching strategy
Security — Auth/authz verification, input validation, dependency audit, secrets management, OWASP top-10 review
Deployment — Container hardening, rollback strategy, blue-green/canary configuration, infrastructure-as-code review
Testing — Unit/integration/e2e coverage, contract tests, chaos/failure injection, smoke tests in staging
Documentation — API docs, runbooks, architecture diagrams, on-call playbooks, ADRs for key decisions

### Skill Routing Table

ConcernSkill / AgentPathLogging & Observabilitylogging-observabilityai/skills/tools/logging-observability/SKILL.mdError Handlingerror-handling-patternsai/skills/backend/error-handling-patterns/SKILL.mdPerformanceperformance-agentai/agents/performance/Securitysecurity-reviewai/skills/meta/security-review/SKILL.mdDeployment (containers)docker-expertai/skills/devops/docker/SKILL.mdDeployment (pipelines)deployment-agentai/agents/deployment/Testingtesting-workflowai/skills/testing/testing-workflow/SKILL.mdRate Limitingrate-limiting-patternsai/skills/backend/rate-limiting-patterns/SKILL.mdDocumentation/generate-docsai/commands/documentation/

Routing rule: Read the target skill first, follow its instructions, then return results here for synthesis.

### Health & Lifecycle

Health check endpoint (/healthz or /health) returns dependency status
 Readiness probe distinguishes "starting" from "ready to serve"
 Liveness probe detects deadlocks and unrecoverable states
 Graceful shutdown drains in-flight requests before exit
 Startup probe allows for slow initialization without false restarts

### Resilience

Circuit breakers on all external service calls
 Retry with exponential backoff and jitter on transient failures
 Rate limiting configured per endpoint and per client
 Backpressure mechanisms prevent cascade failures under load
 Timeouts set on every outbound call (HTTP, DB, queue)
 Bulkhead isolation separates critical from non-critical paths

### Configuration & Secrets

All configuration externalized (env vars, config service, or feature flags)
 No secrets in code, images, or environment variable defaults
 Secrets loaded from a vault (e.g., AWS Secrets Manager, HashiCorp Vault)
 Configuration changes do not require redeployment
 Feature flags in place for high-risk changes

### Data Safety

Backup strategy defined and tested (RPO/RTO documented)
 Restore procedure verified in a non-production environment
 Database migrations are backward-compatible and reversible
 Data retention policies implemented and enforced

### Operational Readiness

Runbooks exist for top 5 most likely failure scenarios
 SLOs defined (availability, latency, error rate) with error budgets
 SLAs communicated to dependent teams or customers
 On-call rotation staffed and escalation path documented
 Dashboards show golden signals (latency, traffic, errors, saturation)
 Alerting rules configured with appropriate thresholds and severity

### Maturity Levels

LevelNameRequirementsL1MVPHealth check, basic logging, error handling, manual deploy, unit tests, READMEL2StableStructured logging, metrics, graceful shutdown, CI/CD pipeline, integration tests, runbooksL3ResilientDistributed tracing, circuit breakers, auto-scaling, chaos testing, SLOs, on-call rotationL4OptimizedAdaptive rate limiting, predictive alerting, canary deploys, full observability, error budgets, postmortem culture

### Progression Guidance

L1 → L2: Add structured logging, metrics endpoint, and a CI/CD pipeline. Write runbooks for known failure modes.
L2 → L3: Instrument distributed tracing. Add circuit breakers to external calls. Define SLOs and set up on-call.
L3 → L4: Implement canary deployments. Adopt error budgets. Run regular game days. Build predictive alerting.

### On-Call Rotation

Minimum two engineers per rotation (primary + secondary)
Handoff includes review of recent deploys, open issues, and known risks
Escalation targets defined: primary → secondary → engineering lead → VP Eng

### Escalation Matrix

SeverityResponse TimeEscalation AfterStakeholder NotificationSEV-1 (outage)15 min30 minImmediate — exec + customersSEV-2 (degraded)30 min1 hourWithin 1 hour — eng leadSEV-3 (minor)4 hoursNext business dayDaily standupSEV-4 (cosmetic)Next sprintN/ABacklog

### Postmortem Template

## Incident: [Title]
**Date:** YYYY-MM-DD | **Duration:** X hours | **Severity:** SEV-N

### Summary
One-paragraph description of what happened and impact.

### Timeline
- HH:MM — First alert fired
- HH:MM — Engineer paged, investigation started
- HH:MM — Root cause identified
- HH:MM — Mitigation applied
- HH:MM — Full resolution confirmed

### Root Cause
What broke and why. Link to code/config change if applicable.

### Impact
- Users affected: N
- Revenue impact: $X (if applicable)
- SLO budget consumed: X%

### Action Items
| Action | Owner | Due Date | Status |
|--------|-------|----------|--------|
| Fix X  | @eng  | YYYY-MM-DD | Open |

### Lessons Learned
- What went well
- What went poorly
- Where we got lucky

### NEVER Do

NEVER skip health checks — every service must expose health endpoints; no exceptions for "simple" services
NEVER store secrets in code or container images — use a secrets manager; never default env vars with real values
NEVER deploy without a rollback plan — if you cannot roll back in under 5 minutes, you are not ready to deploy
NEVER ignore error budget violations — when the error budget is exhausted, freeze feature work and fix reliability
NEVER treat logging as optional — a service without structured logging is a service you cannot debug at 3 AM
NEVER go to production without runbooks — if on-call cannot resolve the top 5 failure modes without the original author, the service is not production-ready
## Trust
- Source: tencent
- Verification: Indexed source record
- Publisher: wpank
- Version: 1.0.0
## Source health
- Status: healthy
- Source download looks usable.
- Yavira can redirect you to the upstream package for this source.
- Health scope: source
- Reason: direct_download_ok
- Checked at: 2026-04-30T16:55:25.780Z
- Expires at: 2026-05-07T16:55:25.780Z
- Recommended action: Download for OpenClaw
## Links
- [Detail page](https://openagent3.xyz/skills/production-readiness)
- [Send to Agent page](https://openagent3.xyz/skills/production-readiness/agent)
- [JSON manifest](https://openagent3.xyz/skills/production-readiness/agent.json)
- [Markdown brief](https://openagent3.xyz/skills/production-readiness/agent.md)
- [Download page](https://openagent3.xyz/downloads/production-readiness)