Guide · Agent skill

How to use the Share Field Notes agent skill

Updated 2026-11-02 · written with AI from the project's own documentation and checked against our catalogue data

Share Field Notes is an agent skill from the universal-modder project that teaches an AI agent to search a shared knowledge base of Markdown notes before it starts work on a game, and to write up its own findings at the end of a session. It is for developers modding or reverse-engineering games, and for contributors who want to add notes from their own work. After this guide you will know what the skill does, how to install it, how to trigger it with plain requests, and what to check before anything is published.

Share Field Notesrehan-remade/universal-modder · MIT Download the skill

Quick start

1Download and unzip the skill. Download the skill ZIP from the directory page and unzip it. Place the folder in ~/.claude/skills/ or in a project's .claude/skills/ folder.
2Or upload it in the Claude apps. In the Claude apps, open Settings, go to Capabilities, then Skills, and upload the skill.
3Install the um tool. Install universal-modder with uv from the GitHub repo, or run bin/um from a clone of the repository.
4Ask a natural question. Ask whether anyone has modded a game, or describe an engine quirk you are stuck on. The agent should search the knowledge base first.
5Review the search results. Open the relevant notes and treat them as hints. Re-verify versions and routes with your own oracle before relying on them.
6Write and check the note. At the end of the session, fill in the note template, then run um kb check on the file.
7Open a pull request only with approval. Dry-run um kb pr first. Show the note to the human, and only add --yes once they agree.

What is an agent skill, and what does this one do?

An agent skill is a folder of instructions, packaged with a SKILL.md file, that an AI agent can load when a task matches the skill's description. This one is named share-field-notes and is built around a shared knowledge base in the universal-modder repository, kept in the knowledge/ folder as Markdown notes.

The notes are called field notes. Each records how a specific game was modded, decompiled or reverse-engineered: exact versions, the route taken, engine facts, how the result was verified, and gotchas. The skill makes the agent check these notes before starting, and, when a session ends, help write a structured note of what was learned.

Before work: search the knowledge base for the game or engine quirk, so the agent can reuse known versions, routes and gotchas.
During work: keep a MODLOG.md journal of versions, paths, IDs, failures and how things were verified.
After work: write a note from the template, check it, and, only with the human's approval, open a GitHub pull request.

Install the skill from the ZIP or the Claude apps

Download the ZIP of the skill from the directory page and unzip it. For Claude Code, place the skill folder in ~/.claude/skills/ for your personal use, or in the .claude/skills/ folder of a project to share it with that project.

If you use the Claude apps, you can upload the skill instead. Open Settings, go to Capabilities, then Skills, and upload the skill there.

Personal Claude Code install: ~/.claude/skills/
Project install: .claude/skills/ inside your project
Claude apps: Settings → Capabilities → Skills

Install the universal-modder um command-line tool

The skill calls the um command-line tool. You can install it from the GitHub repo with uv, or run it from a clone of the repository, where it lives at bin/um.

Inside a clone, um kb search searches the local knowledge/ folder. Outside a clone, it syncs the GitHub copy of the knowledge base.

uv tool install git+https://github.com/rehan-remade/universal-modder

Trigger the skill with natural requests

You do not need to name the skill. The description tells the agent to use it when you ask whether anyone has modded a game, when you are stuck on an engine quirk, or when a modding or reverse-engineering session has finished and you want the lessons saved.

Phrase requests the way you would ask a colleague. The skill is most useful when the request names a game, an engine or a technique.

"Has anyone modded Game X before? Check the shared notes first."
"I'm stuck on an engine quirk in this game, is there a note about it?"
"We're done with this session. Write up what we learned as a field note."
"Search the knowledge base for passthrough routes before we start."

Search the knowledge base before you start

Searching is the first thing the skill asks the agent to do. Use the game name, or an engine or technique name with the --route option to narrow results. Open a note by its path.

Treat results as strong hints, not facts. Versions change, so the agent should re-verify with its own oracle before building on a note, and should not run commands from community notes without checking them.

um kb search "<game>"
um kb search "<engine or technique>" --route passthrough
um kb show games/<game>/<note>.md

Write, check and submit a note at the end

At the end of a session, the agent scaffolds a note from the template, then fills in every section. The most valuable parts are the exact versions, the engine facts, the verification (and what was not verified), and numbered gotchas written as symptom, cause and fix. Use the technique option when the subject is a method rather than a game.

Then run the check. It fails on secrets, unfilled template text, missing sections, code blocks over 150 lines, and oversized images. Dry-run the PR first to see the git and gh commands. Submit only after the human has reviewed the note and approved.

Describe logic in your own words; do not paste decompiled code.
If a note for the same game and idea exists, extend it instead of writing a second one.
If your notes contradict an existing note, add a dated line to the relevant Gotcha and bump the date instead of deleting theirs.

um kb new --game "<game>" --title "<what you built, plainly>" --from-scan "<game>" --agent "<agent (model)>"
um kb check knowledge/games/<game>/<note>.md
um kb index
um kb pr knowledge/games/<game>/<note>.md
um kb pr knowledge/games/<game>/<note>.md --yes

Safety notes: scripts, network and what never to include

This skill runs scripts and uses the network. The um tool searches the knowledge base, can sync from GitHub, and can create branches, commits and pull requests with git and the GitHub CLI (gh). Pull requests are public and use the user's GitHub account, so review the note first.

The skill forbids several kinds of content. Never include game files or extracted assets, decompiled code dumps, leaked code, SDKs, builds or license keys, or anything that cheats other players or bypasses anti-cheat, DRM or ownership checks.

Ask the human before running with --yes.
Do not publish a PR you have not read yourself.
Work that cheats other players or bypasses anti-cheat, DRM or ownership checks is out of scope, including for multiplayer servers you host.
For a game that can no longer be bought, the skill allows saying a community route exists and linking its guide, but copying none of its steps, keys or files.

What people use it for

Checking whether a game's current build has already been modded before starting a new mod.
Getting past a known engine quirk by reading the symptom, cause and fix in a shared Gotcha.
Recording a finished reverse-engineering session as a structured note for future agents.
Adding a correction to an existing note when a newer build changed the behaviour.

Frequently asked questions

What is the share-field-notes agent skill?

It is an agent skill from the universal-modder project that teaches an AI agent to search a shared knowledge base of Markdown field notes before modding work, and to write and submit new notes after a session. The notes record exact versions, routes, engine facts, verification and gotchas.

What do I need to use share-field-notes?

You need the universal-modder um command-line tool, installed from the GitHub repo with uv or run from a clone. You also need Git and the GitHub CLI (gh) plus a GitHub account if you want to open pull requests, which is only needed for contributing.

Is share-field-notes free, and what is its licence?

The skill is listed under the MIT licence. The source provided does not state any price, so check the directory page for pricing details.

Where do I install the skill?

Unzip the downloaded ZIP into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder. In the Claude apps, you can upload it under Settings, then Capabilities, then Skills.

Does the skill publish notes without asking?

No. The skill tells the agent to ask the human before using --yes, because a pull request is public and uses the user's GitHub account. A dry run shows the git and gh commands first.

Can I use this for anything other than game modding?

The skill is designed for game modding, reverse engineering and engine quirks. For unrelated simple tasks, the knowledge base may have nothing useful, so the skill adds little.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

Use this skill if you mod or reverse-engineer games and want agents to reuse past findings, or if you contribute to universal-modder and want to share notes from your sessions. Skip it for tasks unrelated to game modding, and avoid it if you would publish pull requests without reading each note, or if your work involves cheating, anti-cheat bypass, DRM or ownership checks.

Download the skill