Skip to content
TrustedSkillsbeta
Back to all skills

Dojo Test

Checked
dojoengine·vlatest·testing·MIT

Automates rigorous testing of AI agents within a simulated environment using dojoengine's customizable scenarios.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add dojoengine/book --skill dojo-test -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

dojoengine

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned dojoengine/book at 093849a7a6.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
093849a7a6
Manifest
skills/dojo-test/SKILL.md
Scanned
1 file, 299 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill automates the creation of rigorous tests for Dojo models and systems using Cairo's test framework and Dojo’s testing utilities. It generates test files including setup functions (like spawn_test_world), model and system registration, test functions with assertions, cheat code usage for manipulating execution context, state verification, and unit/integration test structures. The skill guides the user through specifying what to test and desired state assertions.

When to use it

  • Write tests for game systems (e.g., "move system").
  • Test specific models (e.g., "Position model").
  • Add unit tests for combat logic.
  • Create integration tests for different components.

Key capabilities

  • Generates test files with spawn_test_world() setup.
  • Includes model and system registration in generated tests.
  • Creates test functions with assertions.
  • Supports cheat code usage to manipulate the execution context during testing.
  • Provides for state verification within tests.
  • Facilitates both interactive (guided) and direct test generation.

Example prompts

  • "Write tests for the spawn system"
  • "Test that the move system correctly updates Position"
  • "Add unit tests for combat logic"

Tips & gotchas

  • The skill requires familiarity with Cairo's testing framework.
  • Tests are run using the command sozo test (e.g., sozo test test_spawn).
  • Unit tests should be placed within model files, while integration tests reside in a dedicated "tests" directory.