Council v2

This skill is plausibly what it says, but review these points before installing or using it on real secrets: - Behavior vs docs: The documented synthesis examples (e.g., approve+approve+reject -> approve) conflict with the code in scripts/synthesize.py, which requires an average >0.75 to return 'approve'. Test the synthesizer on representative reviewer JSON to confirm the actual behavior and, if needed, update either the docs or code. - Sensitive data: council.sh constructs an orchestration prompt containing the full content under review and prints it to stdout (or JSON). That content will be forwarded to whatever model providers your OpenClaw installation uses. Do not run reviews on files with secrets, credentials, or private data unless you have explicitly configured safe provider handling and logging controls. - Provider configuration & provenance: The skill itself does not hold API keys; it expects the agent/platform to supply model providers (OpenRouter or direct providers). Make sure your OpenClaw model/provider configuration enforces provider diversity if you want the intended cross-provider council. Also verify the origin of this package (README references a GitHub repo) if provenance matters for your environment. - Sanity checks: Run the synthesizer locally with mock reviewer JSON to validate exit codes and outputs. Review the role prompts to ensure they match your threat model (e.g., ensure 'Security & Risk' actually flags the issues you care about). If you rely on mechanical blocking for security decisions, explicitly test the 'critical' finding flow. If you want, I can produce a short test plan (example reviewer JSON inputs and expected outputs) to validate the synthesizer behavior and expose the docs/code mismatch.