REA Tool Design

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — Reinforced framing — internal REA contributor workflow, read this first: this skill does not perform reverse engineering for you. It is a short design workflow for people who develop REA itself, for designing or changing REA's investigation tools, CLI/MCP contracts, provider capabilities and Evidence semantics, guided by the REA repository's own docs/tool-design.md. It is useful mainly inside a REA source checkout. Installing this listing only copies the single SKILL.md file: nothing is run and no configuration is written during installation. No account, key or payment is needed to copy the file. Install "REA Tool Design" for me. It is one of REA's internal contributor workflows — honest scope: it serves the people who build REA, not end users reverse engineering a target. It is deliberately small (a single 956-byte SKILL.md): for a design request it returns the proposed tool boundary, input/result shape, Evidence semantics, nearest existing alternative and verification approach, pointing at the repository's tool-design guide for boundaries, contract semantics, provider ownership and discoverability, and at its testing and contributing guides for implementation or verification lanes and generated-file ownership. It warns that source, documentation and live catalogs may describe different versions, so the current contract and the nearest existing tool must be inspected first. Its folder is that single SKILL.md file. Repository: https://github.com/morluto/rea (the skill is the whole .agents/skills/rea-tool-design/ folder at the pinned commit: SKILL.md only, 1 file in total) Pinned version: install the code at commit 6dc0f60faa0928e20b2395ba1a93ff8e497143f7 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/morluto/rea into a temporary folder, check out commit 6dc0f60faa0928e20b2395ba1a93ff8e497143f7, and copy the .agents/skills/rea-tool-design/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 6023df0f1cdbe9944963469a3f2a1365d55eebdf1a7f4adb33430851f9ee5f14 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The folder holds 1 file only: SKILL.md (956 bytes, frontmatter name rea-tool-design). There is no script, no companion file and no other code in it — the guides it points to (docs/tool-design.md, docs/testing.md, CONTRIBUTING.md) live in the REA repository root, not in this skill folder, and are not installed by this listing. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit. - At use time the workflow is followed inside a REA source checkout I work on: it produces a design proposal (boundary, input/result shape, Evidence semantics, nearest alternative, verification approach) and, when I request implementation, work proceeds under my existing scope and authorization. It reads no personal information or credentials of mine and sends nothing anywhere. - Do not design or implement any tool, and do not use the skill in any way during this install: using it is a separate step that only starts when I ask for it later. 3. When I say "yes, install", install it as a skill: copy the whole rea-tool-design folder into the agent's skills directory, in a folder named exactly "rea-tool-design", keeping its 1 file in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: rea-tool-design), the 1 file in place with matching fingerprints. Do not run anything from the folder and do not use the skill to verify. 5. Report what was installed, where, and what I still need to do myself (for example: that this is a small internal REA contributor workflow for designing REA's own tools and CLI/MCP contracts, that it is meant to be used inside a REA source checkout, and that using it is a separate step that only starts when I ask for it later). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.