openclaw-council
Skill0 starsChanged 4 months agoMITView on GitHub
Stress-test OpenClaw architecture or production-config changes with an isolated council pass, contradiction check, and independent Codex review. Use when autonomy, reliability, fallbacks, or deployment risk make a one-pass answer too weak.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- nonaammme/openclaw-counciltheir own version, first seen Feb 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- nonaammme/openclaw-council★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository37 other files it gives its agents.
- adr-logSkill
- adversarial-reviewSkill
- ai-writing-detoxSkill
- autonomous-video-pipelineSkill
- browser-tutorial-videoSkill
- codex-execution-packSkill
- continuity-ledgerSkill
- github-mobile-opsSkill
- github-seoSkill
- idea-validationSkill
- illustration-promptSkill
- issue-control-loopSkill
- justdoitSkill
- lazy-seniorSkill
- long-context-dispatchSkill
- parallel-worktreesSkill
- playwrightSkill
- product-councilSkill
- product-shapingSkill
- public-artifact-laneSkill
- readme-generatorSkill
- screenshotSkill
- session-to-postSkill
- spec-bundleSkill
- spreadsheetSkill
- spreadsheet-tabular-analysisSkill
- spreadsheet-xlsx-editSkill
- tool-scoutSkill
- transcribe-basicSkill
- transcribe-diarizeSkill
- transcribeSkill
- triage-findingSkill
- video-builderSkill
- video-render-runSkill
- video-spec-builderSkill
- visual-explainerSkill
- work-shapingSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Do not use when: the change is a quick tweak with no real autonomy, reliability, or rollback risk.
- Distinctive: line 14
Run three independent review surfaces so risky OpenClaw plans get contradiction checks, blind-spot reduction, and an explicit go/no-go gate …
- Distinctive: line 17
Write a short draft plan first so every reviewer sees the same concrete proposal.
- Very specific: line 18
Run the isolated OpenClaw council pass, the contradiction-auditor pass, and the separate codex exec review.
- Distinctive: line 22
All three review passes complete before risky production config changes are treated as approved.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
OpenClaw Council
Metadata
- Trigger when: an OpenClaw design or config change is serious enough to deserve multi-pass review before go-live.
- Do not use when: the change is a quick tweak with no real autonomy, reliability, or rollback risk.
Skill Purpose
Run three independent review surfaces so risky OpenClaw plans get contradiction checks, blind-spot reduction, and an explicit go/no-go gate before production changes land.
Instructions
- Write a short draft plan first so every reviewer sees the same concrete proposal. Keep the plan focused on the actual architecture or config change under review.
- Run the isolated OpenClaw council pass, the contradiction-auditor pass, and the separate
codex execreview. Use~/.codex/skills/openclaw-council/references/prompt-pack.mdwhen you need the exact review prompts or setup details. - Merge and deduplicate the findings into one revised plan with clear critical issues, contradictions, go/no-go guidance, and the gates that must close before the change is safe to apply.
Non-Negotiable Acceptance Criteria
- All three review passes complete before risky production config changes are treated as approved.
- Preview models, proxies, and multi-provider fallbacks are treated as higher-risk until proven stable.
- The revised plan includes rollback and synthetic health checks.
- The final answer distinguishes merged consensus from unresolved contradiction.
Output
- Critical findings first.
- A contradiction section naming hidden dependencies or incompatible assumptions.
- A revised plan and a go/no-go recommendation with explicit gates before go-live.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.