rea-tool-design skill

by morluto·morluto/rea·459k stars·MIT

Audit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.

A100/100content scan

Is the rea-tool-design skill safe?

Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-11-10.

No findings.

Install the rea-tool-design skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.

git clone --depth 1 https://github.com/morluto/rea.git /tmp/rea
mkdir -p ~/.claude/skills
cp -r /tmp/rea/.agents/skills/rea-tool-design ~/.claude/skills/rea-tool-design

available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

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 provider-backed work, exercise the analyst's task through REA and compare relevant native provider and independent artifact observations where available. Check applicable partial results, recovery and session boundaries; report what was not exercised. For failure guidance, follow design recovery around the failure. Use workflow verification to select evidence for the proposed contract instead of seeking provider API parity.

For an audit, follow audit existing tools: scope representative tasks, exercise the live workflow, and distinguish reproduced bugs, supported limitations, design opportunities and unverified claims. Check relevant rendered MCP prompts, guided workflows and packaged skill advice against the live contracts and exercise their suggested handoffs. Report working alternatives and evidence limits as well as findings.

For wording audits and agent trials, use focused tool-description trials. Start with representative workflow boundaries and repeat failures or ambiguous outcomes; keep actual arguments and supported final claims separate. Reuse the repository's evaluation tooling and report actual runtime/model versions and synthetic versus production coverage rather than copying a harness into a skill.

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.

More skills from morluto/rea

Area-analysis-optimizationOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.
Area-changelog-updatePrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.
Area-ci-tests-auditAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.
Areverse-engineer-anythingReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.
Areverse-engineer-anythingReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.
Areverse-engineer-anythingReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.

All agent skills → · MCP servers