Skip to content
SkillCheatSheet Sign in

rea-tool-design

An AI agent skill from morluto/rea, scored 49 out of 100 by code.

49/ 100D

Code score by group

  • Spec20/20
  • Description7/20
  • Procedure0/15
  • Done criteria0/15
  • Resources7/10
  • Scripts5/8
  • Safety7/7
  • Upkeep3/5

It loses the most points in Procedure (15), the group that checks whether the steps are numbered, read the context first and say what to do when something fails.

What the author says it does

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

This is the description in the skill's own SKILL.md, written by its author, not by SkillCheatSheet.

Repository
morluto/rea
Folder
.agents/skills/rea-tool-design
License
MIT
GitHub stars
453,855
SKILL.md lines
44
Other files
0

Add rea-tool-design to your agent

npx skills add morluto/rea --skill rea-tool-design

The command uses the open skills CLI. A skill is instructions and scripts your agent will follow, so read it first: open the folder on GitHub at the commit that was scored.

More skills from morluto/rea

  1. rea-changelog-update

    Prepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.

    59C
  2. rea-analysis-optimization

    Optimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache…

    57C
  3. reverse-engineer-anything

    Reverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a…

    56C
  4. rea-ci-tests-audit

    Audit 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 o…

    54D

All skills in morluto/rea

Scores come from a snapshot of 300 public GitHub repositories taken on 12 November 2026. Every score is the result of fixed checks run by code; no AI is involved. How scoring works.