rea-tool-design
Skill4 starsChanged 29 days agoMITView on GitHub
Design or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.
8 other projects use a version of this, 3 of them edited; 5 new projects in the last 4 weeks, against 0 the 4 before.
Adopted by
Surging: 5 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- AxlZero21/Skillsword for word, first seen Nov 8, 2026
- orbyn-dev/orbyn-fullstack-skillstheir own version, first seen Nov 8, 2026
- Prompt-Motion/ReaReverseword for word, first seen Nov 8, 2026
- zheedevVn/Rea-Unlockword for word, first seen Nov 1, 2026
- kinqsradio/orbyn-fullstack-skillstheir own version, first seen Oct 25, 2026
- laaielichter/Reverseportedited, first seen Oct 20, 2026
Other versions8 projects use a version of this.
Word for word · 3
- Prompt-Motion/ReaReverse★ 4100% same
- zheedevVn/Rea-Unlock★ 4100% same
- AxlZero21/Skills★ 1100% same
Edited · 3
- morluto/rea★ 442k40% same
- laaielichter/Reverseport★ 1837% same
- 17lijunyi/chaichai★ 192% same
Wrote their own version · 2
- kinqsradio/orbyn-fullstack-skills★ 4same name
- orbyn-dev/orbyn-fullstack-skills★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
1 rule. 1 is common, 0 are distinctive, and 0 are very specific to this project.
1
Common
Most of the 5 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 8
Use the tool-design guide for tool boundaries, contract semantics, provider ownership, and discoverability.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
REA tool design
Use the tool-design guide for tool boundaries, contract semantics, provider ownership, and discoverability. Inspect the current contract and nearest existing tool relevant to the analyst question; source, documentation, and live catalogs may describe different versions.
For a design request, return the proposed boundary, input/result shape, Evidence semantics, nearest alternative, and verification approach. Implement when requested, preserving the user's scope and existing authorization.
For implementation or verification, consult testing for the affected consumer and provider lanes, and contributing for generated-file ownership. Read provider/workflow guides only as the task requires.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.