Fix it
utabk/marrow: files to add.
Starting points for the files agents look for, made by fixed templates from public facts. Anything only you know is marked TODO. Read each one, edit it, then add it to your repo yourself. ScBee never changes your repo.
llms.txt
A short description models can read first.
# marrow > Marrow (formerly REA Studio) is a desktop GUI for REA, the reverse engineering MCP: a classic code browser (listing, decompiler, function graph) and all 229 REA tools in one app for macOS, Windows ## Docs - [README](https://github.com/utabk/marrow#readme): what it is and how to install it - [Source](https://github.com/utabk/marrow): the code - [Licence](https://github.com/utabk/marrow/blob/HEAD/LICENSE): MIT
AGENTS.md
Instructions for coding agents that work inside the repo.
# marrow Marrow (formerly REA Studio) is a desktop GUI for REA, the reverse engineering MCP: a classic code browser (listing, decompiler, function graph) and all 229 REA tools in one app for macOS, Windows ## Build and test - Install: TODO - Test: TODO - Run: TODO ## Conventions - TODO: the rules a new contributor (or agent) must follow ## Do not - TODO: files or actions that are off limits
agent.json
A card other agents can read: what this is and what it can do.
{
"name": "marrow",
"description": "Marrow (formerly REA Studio) is a desktop GUI for REA, the reverse engineering MCP: a classic code browser (listing, decompiler, function graph) and all 229 REA tools in one app for macOS, Windows",
"url": "https://github.com/utabk/marrow",
"skills": [
{
"name": "TODO: what it can do",
"description": "TODO: one sentence"
}
]
}
Starting something new? The agent-ready starter is a GitHub template with all of these files, two skills and this check in CI from the first commit.