MUD
PassAudited by ClawScan on May 1, 2026.
Overview
This skill is coherent and purpose-aligned, but it can run local MUD engine commands that change persistent game state.
Install only if you intend your agent to run local MUD operations. Before using it, verify the target mud-agent directory and database, and avoid running smoke tests or save/restore operations against a live campaign unless that is intended.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Running the skill can create or change MUD players, characters, snapshots, or image-generation records in the selected campaign.
The skill exposes a general MUD command runner, and the documented examples include commands that can modify game state or trigger configured image generation. This is aligned with the stated MUD operations purpose, but it is operationally meaningful.
python skills/mud/scripts/mud_cmd.py "<command>" ... "register-player --campaign demo" ... "new-character --campaign demo" ... "save --campaign demo" ... "generate-image --campaign demo"
Confirm the target campaign and database before state-changing operations; use a demo campaign or explicit test database for smoke tests.
If the local MUD engine file is unexpected or modified, this helper will run that engine code with access to the MUD database path.
The helper imports or executes a local mud_agent.py from the workspace rather than containing the engine itself. That dependency is expected for this skill, but the user should trust the selected local engine directory.
sys.path.insert(0, str(mud_dir)); from mud_agent import MudAgent, Context ... cmd = [py, str(mud_dir / "mud_agent.py"), "--db", str(db_path)] + shlex.split(command)
Verify the mud-agent directory before use, and use the explicit --mud-dir and --db-path options when operating on a known test or production target.