Openclaw Godmode Skill Repo

v5.11.3 – Security Declaration Alignment This release fixes security-scan findings caused by inconsistent runtime declarations in v5.11.2. What changed • Updated runtime declarations to match actual workflow behavior: • requires_binaries: true • requires_credentials: true • requires_network: true • Clarified package behavior: • The package itself remains documentation-only (no install-time executable payload). • Agent workflows may execute shell/network actions at runtime when invoked by the user. • Added explicit runtime transparency: • Required/optional runtime binaries • Optional credentials/environment expectations (e.g. GH_TOKEN, Claude auth, MCP configuration) • Refined security semantics to distinguish: • install-time safety • runtime agent capabilities Why this release v5.11.2 could create a misleading security impression by claiming no network/credentials/code-execution requirements while documenting workflows that use shell, GitHub, Playwright, and web tools. v5.11.3 resolves that mismatch for clearer trust and more accurate scanner interpretation. Compatibility • No breaking workflow changes • Backward-compatible behavior • Metadata/security declaration update only

v5.11.2 - Converts skill to documentation-only, updates ownership/metadata - Fully converted cc-godmode to a documentation-only skill: skill now provides workflow/instructions but does not execute code. - Updated skill metadata: new author (`cubetribe`), repository, tags, and clarified type as `orchestration-docs`. - Added `clawdis.yaml` and `.DS_Store` files; removed legacy `scripts/build-skill.js`. - Explicit note added highlighting that the skill requires no binaries or credentials and does not perform orchestration itself. - Tool and model references clarified as examples; actual implementations depend on OpenClaw setup.

cc-godmode 5.11.1 - Updated SKILL.md with clearer descriptions of workflows, agent roles, and orchestration best practices. - Improved documentation of standard workflows, including diagrams for agent handoffs and quality gates. - Added detailed agent specifications and output formats for all subagents. - Clarified file structure and requirements for build reports and versioning. - Included pre-push and release validation checklist to enforce project integrity.