Agent skill

Dojo Contributing

by dojoengine in dojoengine/dojo

Contributor workflow for dojoengine/dojo. An agent skill from dojoengine/dojo.

Apache-2.0Auto-check passedDevelopment

Install Dojo Contributing

skills CLI
$ npx skills add dojoengine/dojo --skill dojo-contributing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install dojoengine/dojo dojo-contributing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/dojoengine/dojo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/dojo-contributing .claude/skills/dojo-contributing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
dojo-contributing
GitHub stars
478
Token cost
~356 tokens
SKILL.md length
138 words
Files
2
Skills in repo
3
Repo updated
First seen
Licence
Apache-2.0

At a glance

Contributor workflow for dojoengine/dojo. An agent skill from dojoengine/dojo.

  • Works in 6 steps: Identify affected crates and binaries… → Prepare local test databases → If Cairo examples, policies, or core… → …
  • Reviewing changes in this repository
  • SKILL.md covers Core Workflow and PR Checklist
  • Calls cargo, bash and git

What it does

Dojo Contributing is an agent skill from dojoengine/dojo. Contributor workflow for dojoengine/dojo. Use when implementing or reviewing changes in this repository, especially Rust workspace edits, Cairo fixture refreshes, and CI-parity formatting/lint/test checks.

Its SKILL.md is about 360 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Development, covering Linting and formatting. It works with Rust. The repository describes itself as: Dojo is a toolchain for building provable games and applications. The licence is Apache-2.0.

When your agent uses it

  • Reviewing changes in this repository
  • Especially Rust workspace edits
  • Cairo fixture refreshes
  • CI-parity formatting/lint/test checks

Example prompts

  • “/dojo-contributing”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Identify affected crates and binaries from git status and touched files.
  2. Prepare local test databases
  3. If Cairo examples, policies, or core behavior changed, refresh artifacts
  4. Run baseline validation
  5. If Katana behavior is involved, test with a local Katana binary
  6. Run style and lint checks

What it can do on your machine

Read from SKILL.md and the folder at commit 19c258a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • cargo
    • bash
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Dojo Contributing loads about 356 tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 138 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~56
When it runs · the whole SKILL.md, loaded when a task matches
~356

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from dojoengine/dojo at commit 19c258a, republished under its Apache-2.0 licence (© dojoengine). 138 words, ~356 tokens.

Download SKILL.mdSave it as .claude/skills/dojo-contributing/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
dojo-contributing
description
Contributor workflow for dojoengine/dojo. Use when implementing or reviewing changes in this repository, especially Rust workspace edits, Cairo fixture refreshes, and CI-parity formatting/lint/test checks.

Dojo Contributing

Use this skill to make scoped changes in dojoengine/dojo and validate them with repository-standard commands.

Core Workflow

  1. Identify affected crates and binaries from git status and touched files.
  2. Prepare local test databases:
    • bash scripts/extract_test_db.sh
  3. If Cairo examples, policies, or core behavior changed, refresh artifacts:
    • POLICIES_FIX=1 cargo nextest run --all-features --build-jobs 20 --workspace --nocapture policies
    • bash scripts/rebuild_test_artifacts.sh
  4. Run baseline validation:
    • cargo build --workspace
    • cargo nextest run --all-features --build-jobs 20 --workspace
  5. If Katana behavior is involved, test with a local Katana binary:
    • cargo build -r --bin katana
    • KATANA_RUNNER_BIN=./target/release/katana cargo nextest run --all-features --build-jobs 20 --workspace
  6. Run style and lint checks:
    • bash scripts/rust_fmt.sh --fix
    • bash scripts/clippy.sh

PR Checklist

  • Keep the diff focused to the requested behavior.
  • Include fixture/artifact updates when Cairo-driven behavior changes.
  • Record exact validation commands and outcomes in the PR body.

© dojoengine, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .claude/skills/dojo-contributing of dojoengine/dojo.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 19c258a

Compare with similar skills

Dojo Contributing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Dojo Contributing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Dojo Contributing this skilldojoengine/dojo478—~356Automated safety check: PassApache-2.0
Rust Best Practicesfarm-fe/farm5.6k3 repos~1.1kAutomated safety check: PassMIT
Doc Commentsbiomejs/biome26k—~3kAutomated safety check: PassApache-2.0
Rust Hygiene Audittsz-org/tsz577—~1.5kAutomated safety check: PassApache-2.0
Releasexin2017338/lynx-proxy502—~1.1kAutomated safety check: PassMIT
Flowmark Markdown Formatterjlevy/repren374—~631Automated safety check: PassMIT

Similar skills

  • Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.

    5.6k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Doc Comments

    biomejs/biome

    Official

    A skill your agent uses whenever writing or editing Rust //, ///, or //!

    26k GitHub stars~3k tokensUpdated today
    DevelopmentAuto-check passed
  • Run a deep DRY + code-hygiene audit of the Rust workspace and turn the findings into verified, deduplicated, hierarchical GitHub tech-debt issues.

    577 GitHub stars~1.5k tokensUpdated 28 days ago
    DevelopmentAuto-check passed
  • Release

    xin2017338/lynx-proxy

    Publish a new release version of Lynx Proxy. An agent skill from xin2017338/lynx-proxy.

    502 GitHub stars~1.1k tokensUpdated 23 days ago
    DevelopmentAuto-check passed
  • Formats Markdown with the Flowmark auto-formatter for typographic cleanup and semantic line breaks, and helps adopt it across a repository.

    374 GitHub stars~631 tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Rsigma

    timescale/rsigma

    Use the rsigma CLI and MCP server: engine eval, engine daemon, rule lint, rule draft, rule tune, rule backtest, backend convert, mcp serve.

    159 GitHub stars~1.2k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

More from dojoengine/dojo

  • Create A Plan

    dojoengine/dojo

    Conduct a focused technical planning interview to produce an implementable, parallelizable plan or spec with clear dependencies, risks, and open questions.

    478 GitHub stars~1.7k tokensUpdated 5 mo ago
    Auto-check passed
  • Create PR

    dojoengine/dojo

    Create or update a PR from current branch to main, watch CI, and address feedback

    478 GitHub stars~1.1k tokensUpdated 5 mo ago
    Auto-check passed

Works with

Questions about Dojo Contributing

What does Dojo Contributing do?

Contributor workflow for dojoengine/dojo. An agent skill from dojoengine/dojo. Dojo Contributing is an agent skill from dojoengine/dojo. Contributor workflow for dojoengine/dojo.

When should I use Dojo Contributing?

Dojo Contributing fits situations like: reviewing changes in this repository; especially Rust workspace edits; cairo fixture refreshes; CI-parity formatting/lint/test checks.

How do I install Dojo Contributing in Claude Code?

Run `npx skills add dojoengine/dojo --skill dojo-contributing -a claude-code`. Or copy the skill folder (.claude/skills/dojo-contributing in dojoengine/dojo) into .claude/skills/dojo-contributing in your project. Claude Code loads it when a task matches its description.

How do I install Dojo Contributing in Codex?

Run `npx skills add dojoengine/dojo --skill dojo-contributing -a codex`. Or copy the skill folder (.claude/skills/dojo-contributing in dojoengine/dojo) into .agents/skills/dojo-contributing in your project. Codex loads it when a task matches its description.

Can I use Dojo Contributing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dojoengine/dojo --skill dojo-contributing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dojo-contributing, .gemini/skills/dojo-contributing, .github/skills/dojo-contributing and .opencode/skills/dojo-contributing in your project.

What does Dojo Contributing need to run?

Going by SKILL.md and its folder, Dojo Contributing needs the command-line tools its instructions call (cargo, bash and git).

Does Dojo Contributing access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Dojo Contributing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Dojo Contributing use?

Dojo Contributing is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Dojo Contributing use?

About 356 tokens (SKILL.md is roughly 1.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Dojo Contributing?

Skills that share tags, products or a category with Dojo Contributing: Rust Best Practices (farm-fe/farm, 5.6k stars), Doc Comments (biomejs/biome, 26k stars), Rust Hygiene Audit (tsz-org/tsz, 577 stars) and Release (xin2017338/lynx-proxy, 502 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dojo Contributing?

dojoengine (a GitHub organization) maintains it in dojoengine/dojo, which has 478 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on May 6, 2026.

Source: dojoengine/dojo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.