production-readiness

What This Skill Does

The production-readiness meta-skill acts as the central control plane for ensuring your software services are robust, secure, and maintainable before they are exposed to production traffic. Rather than reinventing operational logic, this skill orchestrates specialized agents and skills across seven critical domains: logging, error handling, performance, security, deployment, testing, and documentation. By running this skill, you receive a holistic, synthesized go/no-go assessment that flags vulnerabilities or gaps that might otherwise be missed by siloed development teams. It serves as a unified audit framework, ensuring your service fails gracefully, observes its own state, recovers from transient failures, and remains thoroughly documented for on-call engineers.

Installation

To integrate this skill into your environment, use the official ClawHub installer. Ensure you have the OpenClaw environment initialized:

npx clawhub@latest install production-readiness

Alternatively, for enterprise environments, you can pull directly from the repository:

clawhub install openclaw/skills/skills/wpank/production-readiness

Use Cases

This skill is designed for critical milestones in the software development lifecycle:

• Initial Launch: Validate that a brand-new service meets enterprise standards before it handles production traffic.
• Major Releases: Assess architectural changes that introduce new potential points of failure.
• Incident Recovery: Perform a root-cause analysis and hardening review after an incident to prevent recurrence.
• Quarterly Audits: Maintain long-term system health by reviewing services that have not been audited in the last 90 days.
• Ownership Transfers: Ensure that new teams taking over a service have all the necessary operational context and documentation.

Example Prompts

1. "Run a full production-readiness audit on the user-authentication-service. Focus specifically on security and observability."
2. "We are planning a major version update to the payment-gateway. Please execute a readiness check and report any gaps in our error-handling patterns."
3. "Conduct a quarterly review for the reporting-engine. Generate a summary report including go/no-go recommendations for current production stability."

Tips & Limitations

• Delegation: This skill relies on other skills being installed. If a sub-skill (like performance-agent) is missing, the meta-skill will report a skipped step. Ensure your dependency tree is clean.
• Scope: It identifies what needs fixing but does not automatically patch security vulnerabilities or rewrite your performance bottlenecks; it provides the map, you perform the remediation.
• Contextual Sensitivity: The accuracy of the assessment depends on the metadata provided. Always ensure your project's configuration files are accessible so the agent can inspect your deployment architecture.