Advocatus
v1.0.0Give voice to all opposition. The Advocatus Diaboli — official adversarial challenger to every doctrine, skill, rule, and assumption in the agency. Use when:...
⭐ 0· 57·0 current·0 all-time
byAutomate@ironiclawdoctor-design
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (adversarial challenger) align with the included files: an opposition registry, results, and a local evaluator script. No unrelated credentials, binaries, or external services are requested.
Instruction Scope
SKILL.md instructs users to edit references/opposition-registry.md and to add or clear entries by editing the DOCTRINES dict inside scripts/advocatus_eval.py. The script reads/writes only local files (registry and results). The requirement to change a Python dict in the script to "clear" a doctrine is an unusual workflow (editing code rather than config) and could enable accidental or unauthorized clearing if file edits are not governed.
Install Mechanism
No install spec; this is instruction-only plus a small local Python script. No downloads, package installs, or archive extraction.
Credentials
No environment variables, credentials, or external config paths are requested. The skill operates entirely on repository-local files.
Persistence & Privilege
The script creates/writes JSON results in a local results directory and expects users to edit files to change doctrine state. It does not request always:true or autonomous invocation privileges. Because clearing doctrines is done by editing the script's DOCTRINES dict, you should treat that file as a change-control surface (audit/commit/permission).
Assessment
This skill appears coherent and low-risk: it runs a local Python script and reads/writes files in the skill folder, with no network or credential use. Before installing or running: (1) review scripts/advocatus_eval.py and references/opposition-registry.md yourself (they're short) to confirm behavior; (2) run the script in an isolated environment or sandbox if you have strict write-policy concerns; (3) treat changes that "clear" doctrines as code changes—use version control, code review, and restricted write permissions so someone cannot trivially mark doctrines as cleared by editing the DOCTRINES dict; and (4) if you prefer safer workflow, request the maintainer move mutable state out of the Python source into a separate auditable data/config file so clearing entries is tracked and governed.Like a lobster shell, security has layers — review code before you run it.
latestvk97b28sfax73cpw4csymqgydns83v7mf
License
MIT-0
Free to use, modify, and redistribute. No attribution required.