← Back to Skills Marketplace
su-ariel

Epistemic Council

by su-ariel · GitHub ↗ · v1.0.0
cross-platform ⚠ suspicious
573
Downloads
0
Stars
2
Active Installs
1
Versions
Install in OpenClaw
/install epistemic-council
Description
Manage and execute all Epistemic Council pipeline operations including status checks, validations, audits, and adversarial re-challenges.
README (SKILL.md)

Epistemic Council Skill

Use this skill for all Epistemic Council pipeline operations.

Triggers

"run council", "run pipeline", "substrate status", "council status", "health check", "validate claims", "check boundaries", "find gaps", "rechallenge"

How to invoke

Use the exec tool with the epistemic_council working directory:

exec: cd /root/.openclaw/workspace-epistemic-council-bot/epistemic_council && python epistemic_skill.py "run council"

Available commands (replace argument as needed):

  • "run council" — full pipeline run
  • "substrate status" — event counts + last run summary
  • "health check" — risk / integrity scan
  • "validate claims" — re-evaluate challenged-zone claims
  • "check boundaries" — domain boundary audit
  • "find gaps" — orphan + sparse coverage scan
  • "rechallenge" — adversarial re-challenge of top insight

Workspace

/root/.openclaw/workspace-epistemic-council-bot/

Working directory for exec

/root/.openclaw/workspace-epistemic-council-bot/epistemic_council/

Usage Guidance
What to check before installing/running this skill: - Runtime dependencies: The code expects a local LLM (Ollama) reachable at http://localhost:11434 and uses the 'requests' library. Make sure you have the model service and Python dependencies installed in a controlled environment before running. The SKILL.md does not declare these requirements. - Filesystem path: SKILL.md runs Python from /root/.openclaw/workspace-epistemic-council-bot/epistemic_council. Confirm you are comfortable granting read/write access to that path (it will create/modify epistemic.db, memory/, heartbeat-state.json, openclaw-runs/). If you run as a non-root user, update the path or run in a sandbox/container. - Inspect skill_downloader.py and any omitted files: downloader scripts can fetch code at runtime. If present and not clearly benign, review its contents to ensure it doesn't pull code from arbitrary external servers. - Network endpoints: The visible code posts to a localhost model endpoint by default. If you override model_url or code uses other endpoints in omitted files, review them to ensure no unexpected external exfiltration (the provided excerpts do not show external third-party endpoints). - Code correctness / runtime errors: There are small inconsistencies in the code excerpts (e.g., some agent classes expect parameters but are sometimes instantiated without them), which could cause runtime exceptions. Test the skill in a disposable environment first. - Least-privilege test: Run the skill in a sandbox or container with limited filesystem and network access to observe behavior before granting it access to your main environment. If you want, I can: (1) list the omitted files for review, (2) show the contents of skill_downloader.py, or (3) point out the exact lines where constructor/argument mismatches appear so you can patch them before running.
Capability Analysis
Type: OpenClaw Skill Name: epistemic-council Version: 1.0.0 The skill is classified as suspicious due to its broad `shell: true` permission and the use of `subprocess.run` to execute other Python scripts, as well as the inherent prompt injection surface against the local LLM. While the implementation attempts to mitigate direct shell injection by using list-form arguments for `subprocess.run` (defaulting to `shell=False`), and network access is strictly `localhost_only` (preventing direct exfiltration), the power granted by `shell: true` remains a significant vulnerability risk. An attacker might exploit complex interactions or subtle flaws in argument parsing to achieve unauthorized execution or manipulate the LLM's reasoning, leading to compromised data integrity within the `epistemic.db` or `agent_learning.json` files.
Capability Assessment
Purpose & Capability
Name/description (manage Epistemic Council pipeline) aligns with the provided code: detection, adversarial challenges, audits, re-challenges, and substrate reads/writes. However: SKILL.md presents the skill as 'instruction-only / no install spec' while the package includes many Python modules (so it will actually execute bundled code). The skill expects a local LLM service (mentions Ollama and uses http://localhost:11434) but declares no required binaries or dependencies. This mismatch (no declared dependencies but clear runtime requirements) is a design inconsistency users should be aware of.
Instruction Scope
SKILL.md instructs the agent to run a Python entrypoint in a hardcoded workspace path (/root/.openclaw/workspace-epistemic-council-bot/epistemic_council) which gives the skill explicit permission to read/write files under that path (epistemic.db, memory/, openclaw-runs/, heartbeat-state.json, etc.). That file I/O is consistent with a pipeline manager, but the use of an absolute '/root/...' path is environment-specific and surprising. The runtime instructions do not request unrelated system-wide credentials or mark other system paths, but the code will access the workspace and substrate DB — expected for the stated purpose.
Install Mechanism
No install spec is provided (low install risk), but the code relies on external runtime components that are not declared: 'requests' usage and a local LLM (Ollama) are required. There is also a small skill_downloader.py in the bundle (contents not shown in the manifest excerpt) — downloader utilities can introduce higher risk depending on behavior. Overall the install approach is minimal, but missing dependency declarations and the bundled downloader warrant review.
Credentials
The skill declares no environment variables, credentials, or external API tokens, and the visible code does not attempt to read unrelated environment secrets. Network calls are targeted at a default localhost model endpoint (http://localhost:11434). No cloud credentials or unrelated service tokens are requested, which is proportionate to its claimed purpose.
Persistence & Privilege
always:false and user-invocable:true (normal). The skill writes data to its own workspace (epistemic.db, memory/, logs) and updates heartbeat-state.json; that is expected behavior for a pipeline. There is no evidence it modifies other skills or global agent settings.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install epistemic-council
  3. After installation, invoke the skill by name or use /epistemic-council
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Epistemic Council Skill initial release. - Introduces triggers for all Epistemic Council pipeline operations, including running the council, status checks, health checks, claim validation, boundary checks, gap finding, and rechallenge. - Provides instructions for invocation using the exec tool and details the working directory and workspace location. - Lists available commands for specific operations within the pipeline.
Metadata
Slug epistemic-council
Version 1.0.0
License
All-time Installs 2
Active Installs 2
Total Versions 1
Frequently Asked Questions

What is Epistemic Council?

Manage and execute all Epistemic Council pipeline operations including status checks, validations, audits, and adversarial re-challenges. It is an AI Agent Skill for Claude Code / OpenClaw, with 573 downloads so far.

How do I install Epistemic Council?

Run "/install epistemic-council" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Epistemic Council free?

Yes, Epistemic Council is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Epistemic Council support?

Epistemic Council is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Epistemic Council?

It is built and maintained by su-ariel (@su-ariel); the current version is v1.0.0.

💬 Comments