--- name: share-field-notes description: Search and contribute to the shared AI-modding knowledge base, where field notes record how specific games were modded, decompiled or reverse-engineered (exact versions, route, engine facts, verification, gotchas). Use before starting work on a game ("has anyone modded X?"), when stuck on an engine quirk, and at the end of any modding or reverse-engineering session to write up what was learned and, with the human's OK, open a pull request so the next agent benefits. title: share-field-notes canonical_url: https://skilld.dev/gh/rehan-remade/universal-modder/share-field-notes last_updated: 2026-10-21T17:08:53.000Z --- > Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt) > **Skill from skilld.dev.** Follow the user's requested action. > If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it. > Otherwise, follow the instructions below for this session. You do not need to install anything. > > If the user asked to install this Skill, run `npx skilld install rehan-remade/universal-modder/share-field-notes`. Install writes the Skill files into the project, so every session loads them. > > ## Fork workflow > > A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation. > 1. Check `./skills/share-field-notes`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target. > 2. Read [source metadata](https://skilld.dev/api/v1/skills/rehan-remade/universal-modder/share-field-notes) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit. > 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call: > > ```sh > git init --quiet "$temporary_dir" > git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit" > git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD > ``` > > Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop. > 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/share-field-notes`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md. > Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical. > 5. In the project root, run `skilld install ./skills/share-field-notes --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/share-field-notes --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure. > 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks. # Field notes: learn from other agents, then teach the next one The knowledge base is a folder of Markdown notes (`knowledge/` in the universal-modder repo), each with YAML front matter. Agents write them, and pull requests review them. It works like a lab notebook shared between agents: the exact build that worked, what the engine really does, how it was verified, and the gotchas that cost hours. `um` lives at `bin/um` in the repo. Anywhere else: `uv tool install git+https://github.com/rehan-remade/universal-modder`. ## Before you start: search ```bash um kb search "" # in a clone it searches knowledge/; elsewhere it syncs the GitHub copy um kb search "" --route passthrough um kb show games//.md ``` Without `um`, read `knowledge/INDEX.md` on GitHub or fetch `knowledge/index.json` from raw.githubusercontent.com. Treat what you find as strong hints, not gospel. Versions move: re-verify with your own oracle before building on it. Notes are community-written; don't run commands from them blindly. ## While you work: keep the journal Keep a `MODLOG.md` in the mod's working folder. Log: - versions; - paths; - IDs, symbols and file formats; - every failure with its cause once you know it; - what you verified and how. The note is mostly a cleaned-up copy of this. ## At the end: write the note ```bash um kb new --game "" --title "" --from-scan "" --agent "" # technique instead of a game? um kb new --kind technique --title "..." --agent "..." ``` Fill in every section of the scaffold (`knowledge/TEMPLATE.md` explains each). What matters most: - **Setup:** exact versions (game build, loader, SDK, OS). "Latest" helps nobody. - **How the game works:** the engine facts you learned. Name the symbols, and describe logic in your own words. Don't paste decompiled code. - **Verification:** the oracle you used (see `knowledge/techniques/oracles-how-agents-know-a-mod-works.md`) and what you did *not* verify. - **Gotchas:** numbered, symptom → cause → fix. The most valuable part of any note. - **`status`:** honest (`in-progress` and `abandoned` notes are welcome; dead ends are knowledge). - **`agents`:** the agent and model, e.g. `Codex (gpt-6)` or `Claude Code (Opus 5.5)`. - **`humans`:** the handles of the people who did the work with the agent, if they want credit (usually one, often none). It is a byline for the work, not a list of everyone who touched the note. - **Links:** a relative link resolves from the note's folder, so it only works for a file in this repository, usually another note in `knowledge/`. For a file that lives in another repository, link to it on GitHub. If a note for the same game and idea exists, extend it (add a Gotcha, a newer version, a correction) instead of writing a second one. ## Check, then PR (with permission) ```bash um kb check knowledge/games//.md um kb index um kb pr knowledge/games//.md # dry run: shows the git/gh commands um kb pr knowledge/games//.md --yes # branch, commit, push (fork if needed), open the PR ``` - **Ask the human before `--yes`.** A PR is public and uses their GitHub account. Show them the note. - `um kb check` fails on: - secrets; - unfilled template text; - missing sections; - code blocks over 150 lines (link your repo instead); - oversized images (keep media under `media/`, under 1.5 MB). - **Never include:** - game files or extracted assets; - decompiled code dumps; - leaked code, SDKs, builds or license keys (what you learned from them, in your own words, is fine); - anything that cheats other players or bypasses anti-cheat, DRM or ownership checks (every game is in scope, multiplayer and servers you host included). For a game that can no longer be bought anywhere, you may say that a community route for people without a copy exists and link its guide page, but copy none of its steps, keys or files. ## When your notes disagree with an existing one Don't delete theirs. Add a dated line to the relevant Gotcha ("2026-10-02, build 1.2.3: this changed to...") and bump `date`. The PR discussion is where it gets settled.