# Rea Tool Design

> Design or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.

- Skill: `pinkpixel-dev/rea-tool-design` (Agent Skill)
- Install (CLI): `npx get-skill add pinkpixel-dev/rea-tool-design`
- Raw SKILL.md: https://api.skillmd.com/api/skills/pinkpixel-dev/rea-tool-design/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: pinkpixel-dev (https://skillmd.com/u/pinkpixel-dev)
- Updated: 2026-11-11
- Page: https://skillmd.com/skills/pinkpixel-dev/rea-tool-design

---


# REA tool design

Use the [tool-design guide](../../../docs/tool-design.md) 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](../../../docs/testing.md)
for the affected consumer and provider lanes, and
[contributing](../../../CONTRIBUTING.md) for generated-file ownership. Read
provider/workflow guides only as the task requires.

