eval-charter

Audits a Bot's recent runs against its charter never-list and reports every breach.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/JYeswak/grok_bot_playground --skill eval-charter-jyeswak
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eval-charter
Source: https://github.com/JYeswak/grok_bot_playground/tree/main/plugin/skills/eval-charter
Command: npx skills add https://github.com/JYeswak/grok_bot_playground --skill eval-charter-jyeswak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? A Bot's charter and never-list are written once and rarely checked again, so the first evidence of a breach is usually a human noticing something was sent. This Skill replays a Bot's last N runs and produces evidence-backed answers about whether it stayed inside its approval boundary. ## Core Features & Use Cases - Never-list replay: Matches every numbered charter clause against quoted run artifacts, recording breach, clean, or unauditable per clause per run. - Four system checks: Verifies the routine fired (expected vs. observed runs with miss dates), the approval boundary held, memory shards carried between runs, and spend stayed under the cap. - Ranked breach report: Outputs a dated markdown eval with breaches ranked by blast radius, unauditable runs counted separately, and one evidence-supported charter change proposal. - Use Case: Before widening a Bot's permissions or connecting a new plugin, run a weekly audit to confirm its last 20 runs contained no unauthorized sends, writes, or publishes. ## Quick Start Audit the support Bot's last 20 runs against its current charter and list every never-list breach with quoted evidence.

Frequently Asked Questions about eval-charter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit whether a Bot is following its charter?▼

Replay the Bot's last N runs and match each run's artifacts against the numbered never-list clauses in its charter. A breach requires a quoted run artifact matched to a quoted clause; unreadable runs are counted as unaudited, never as passed.

How to check if a Bot's scheduled routine actually fired?▼

Compare the expected run count from the declared cadence against observed runs in the window, and report the exact miss dates. A Bot with no runs is either unscheduled or was never asked in chat to schedule itself, since there is no direct routine-create RPC.

Can this audit edit the Bot or fix breaches automatically?▼

No, the audit is strictly read-only over run history and memory shards. Every remediation is output as a proposal, and only the owner's explicit approval of that exact change applies it; a Bot relaying approval does not count.

Why are some runs marked unauditable instead of clean?▼

Runs whose artifacts are missing or unreadable cannot be matched against never-list clauses, so they are counted separately as unaudited. Folding them into passed would treat silence in the history as compliance, which usually hides a routine that never fired.

How does the audit handle memory shared between multiple Bots?▼

One cloud computer serves every Bot on the account, so memory shards are matched by owning Bot id before anything is read into them. A shard written by another Bot is not evidence about the Bot under audit.