Php Full Stack Developer

A senior, governance-backed PHP full-stack delivery OS for OpenClaw. Emphasizes pre-flight analysis, safe data changes, explicit contracts, and reproducible verification.

This skill is a Markdown-only governance and process helper for PHP work and appears coherent with that purpose. However: 1) INFO_RUNTIME tells the agent to open ~/.openclaw/workspace/* files (SOUL.md, USER.md, MEMORY.md, daily memory files) and to read/write LOG_*.md files; those files may contain PII, credentials, or other sensitive context. 2) The registry metadata does not declare any required config paths, so the skill's intended file access is not made explicit in its manifest. Before installing: - Inspect the contents of your ~/.openclaw/workspace files (USER.md, MEMORY.md, SOUL.md) to ensure they contain no secrets or PII you don't want an invoked skill to read. - Consider running the skill in a sandbox or with limited file permissions first. - Ask the publisher to update the metadata to declare required config paths and make the read/write behavior explicit, or to add explicit user-consent prompts before reading workspace memory. - If you plan to allow autonomous invocation, be aware that the skill can be triggered to access workspace files during agent runs; require explicit user approval for sensitive tasks. If you want, I can (a) list the exact lines in INFO_RUNTIME/SKILL.md that reference workspace files and logging, or (b) suggest a minimal manifest change to declare those config paths.

Type: OpenClaw Skill Name: php-full-stack-developer Version: 0.1.0 The skill bundle is designed to enforce a rigorous, governance-backed workflow for an AI agent performing PHP full-stack development. All instructions, including those in `SKILL.md` and `INFO_RUNTIME.md`, guide the agent towards safe, structured, and transparent operations, emphasizing pre-flight analysis, risk assessment, stop-work conditions, and explicit logging of decisions and conflicts. Instructions to read files like `~/.openclaw/workspace/SOUL.md`, `~/.openclaw/workspace/USER.md`, and memory files are for the agent's internal state management and operational context, not for unauthorized data access or exfiltration. There is no evidence of malicious intent, data exfiltration, unauthorized execution, persistence, or harmful prompt injection.