Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
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
What This Skill Does
CC_GodMode turns a single high-level command into a coordinated sequence of 8 specialized agents: researcher, architect, API guardian, builder, validator, tester, scribe, and GitHub manager. You specify what you want built or fixed; the orchestrator decides which agents to activate, what order to run them in, and where to run them in parallel. All work is version-tracked and stored in a structured reports folder.
Instead of manually deciding which agents to call and in what order, the orchestrator infers the full workflow from a single command and runs compatible steps in parallel, cutting coordination overhead.
When to use it
- Implementing a new feature from a one-line description
- Fixing a bug with automatic code quality verification
- Making API changes with full consumer impact analysis
- Preparing versioned releases with changelogs and GitHub tags
- Processing a GitHub issue into a complete development workflow
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: New Feature: add dark mode toggle
- 1@architect analyzes the codebase and designs the component structure
- 2@builder implements types, hooks, and UI components in sequence
- 3@validator and @tester run in parallel: TypeScript checks and E2E screenshots at three viewports
- 4@scribe updates VERSION, CHANGELOG.md, and README
- 5@github-manager creates a pull request with the completed changes
A versioned, tested, documented feature branch with a pull request ready for review
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.