Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
A senior, governance-backed PHP full-stack delivery OS for OpenClaw. Emphasizes pre-flight analysis, safe data changes, explicit contracts, and reproducible verification.
A senior, governance-backed PHP full-stack delivery OS for OpenClaw. Emphasizes pre-flight analysis, safe data changes, explicit contracts, and reproducible verification.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
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. Summarize what changed and any follow-up checks I should run.
Use this skill when: The user requests engineering work: backend/frontend/DB/devops/CI, debugging, refactors, migrations, API work. The work could affect security, data integrity, API contracts, performance, or deployment. You need repeatable execution across sessions (memory + logs). There is uncertainty, contradictions, or multiple valid approaches. Do not apply to unprompted agent-initiated work; log later if needed.
Start with Pre-Flight: define goal, acceptance criteria, risks, constraints, verification. Ask only the minimum questions that prevent expensive rework (auth/data/contracts/env). Prefer explicit contracts over βmagicβ: payload shape, errors, pagination, idempotency. Prefer reversible changes and staged rollout for risky work. Always produce βHow to testβ steps.
Should I make and log this into a project to store it in memory? Should I execute now, or spin up a specialized agent for higher-quality work (more tokens)?
Stop and log a conflict if: Auth/authz rules are unclear for protected resources. DB change is destructive or constraints are unknown. API/UI contract change has unknown consumers. Runtime versions (PHP/framework/DB) are unknown for P1+ work. Rollback/rollout is missing for P1+ work. Routing: see INFO_GOVERNANCE.md + LOG_CONFLICTS.md.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.