Local Council Execution

by hex

Local Council Execution is an AI Engineering skill for Claude Code, published by hex in claude-council.

658 stars80 forkson hex/claude-councilAdded 2026/08/24+2% in starsRepository updated 2026/08/12

View source on GitHub Download repo ZIP

ai-agentsantigravityclaude-codeclaude-code-plugincodexgeminigrokkimillmmulti-agentollamaopenaiperplexity

Install in seconds

Install Local Council Execution

Copy Local Council Execution into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/hex/claude-council/tree/main/skills/local-council-execution ~/.claude/skills/local-council-execution

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/hex/claude-council.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: skills/local-council-execution/SKILL.md in hex/claude-council
Installs to: ~/.claude/skills/local-council-execution
Collection: One of 4 skills cataloged from this repository
Category: AI Engineering — 2451 skills

What Local Council Execution does

Local Council Execution runs a fallback panel of independent Claude subagents when no external providers are available. It gathers role-based perspectives and synthesizes them for the ask command or local-council flow.

Local Council Execution is cataloged under AI Engineering on DirSkills. Local Council Execution comes from a repository tagged ai-agents, antigravity, claude-code, claude-code-plugin and codex.

Documentation

README

Excerpt

Local Council Execution

When no external providers are configured, convene a council of independent Claude subagents instead. Each member answers from one role, blind to the others; you then synthesize the spread of perspectives.

Read this first — the honest framing is not optional. Every member is Claude. They share priors and training, so agreement between them is weak signal, not validation. The value here is independent angles and blind-spot coverage, not consensus. The output you produce MUST make this explicit and MUST NOT present member agreement as if it were cross-vendor corroboration.

Step 0: Confirm this is a local-council context (guard)

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Local Council Execution

What else does hex publish alongside Local Council Execution?
Local Council Execution is one of 4 skills that DirSkills catalogs from hex/claude-council, the repository it ships in. Its siblings there include Council Execution, Deep Execution and Provider Integration. Each one is a separate skill with its own page in this directory, installs the same way Local Council Execution does, and is maintained by hex in that same repository. The rest of the collection is listed on the hex/claude-council page.
How does Local Council Execution compare to other AI Engineering skills?
Local Council Execution ranks #1856 by stars among the 2451 AI Engineering skills in this catalog. The most-starred ones next to it are Architecture Decision Records, AI-First Engineering and Agentic OS. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Local Council Execution against them. Open each page to compare what they document and how they install.