VibeRPGSimulator

Submit a spell report

Tested a skill, plugin or MCP server? Send the curator a report with your results. Accepted reports become spells or records here, with credit.

Craft a spell in your browser

Use a skill, plugin, MCP server or subagent that isn't in the library yet? Design its card, icon and battle in the spell creator and send it to the curator. Nothing goes public until the curator checks it. To send usage counts from your session logs instead, use the plugin below.

Craft a spell

With the plugin (easiest)

The plugin counts how often you used the spell from your local session logs. Only those counts leave your machine, plus your OS, CPU architecture and harness versions unless you leave them out. It helps you write the report, can sign it with your SSH key, and sends it only after you say yes.

To test spells on a fixed task, run a Proving Grounds trial with the same plugin. It plays one quest with the spells equipped and once Unarmed (no spells), so the report shows what the spells added.

Claude Code

Add the marketplace and install the plugin:

/plugin marketplace add Demonbane18/vibe-rpg-plugin

/plugin install spell-report@viberpg

Then run:

/spell-report:spell-report

Codex

Add the marketplace:

codex plugin marketplace add Demonbane18/vibe-rpg-plugin

Install spell-report from /plugins. Then type $ and pick spell-report, or run:

$spell-report:spell-report

Upload a report

Download the blank report template. Fill in the JSON header and describe what you tested.

Markdown (.md) with a JSON header, up to 200 KB. No PDF.

A detached .sig file for this report, up to 10 KB.

Up to 6 files: PNG, JPEG, GIF, WebP, MP4 or WebM. The report, signature and attachments must total no more than 4 MB. Phone photos and videos can carry your location; screenshots are safer.

Optional. Lets the curator ask you about the report.

The report and its attachments are emailed to the curator. Leave out secrets and private session logs.

How reports are checked

The curator sees file hashes, whether an SSH signature is valid, whether its key is listed on the GitHub account named in the report, and the usage numbers and environment the plugin recorded.

A valid signature shows who sent the report and that nobody changed it. It does not prove the findings, so include steps to reproduce and public links.

Format

Reports are Markdown (.md) with a JSON header. Screenshots and videos go as separate files, listed with SHA-256 hashes in the header. PDF reports are not accepted.