Menu

Individual skill

keep-it-simple

0upvotes

Review a diff, design, execution path, or subsystem for unnecessary complexity and propose concrete simplifications. Use during code review or independently when the user is concerned about overengineering, excessive coordination, or code that has become hard to understand or operate.

keep-it-simple/SKILL.md

Read pinned source

Source commit 1acf58f08cca24b764a4352a6c30fed1f7fb9fb6

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
198
Repository last updated
Nov 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Keep It Simple

Find the simplest implementation that meets the actual requirements. Ask what
concrete requirement justifies each additional mechanism. Simplicity includes
runtime behavior and operational burden, not just source length.

## Review the requested surface

Establish the intended behavior, explicit constraints, and demonstrated failure
modes. Distinguish these from hypothetical future needs and conventions inherited
from templates or other skills. Inspect the relevant callers and execution path;
do not turn a focused review into a repository cleanup.

Trace what a reader must understand and what the system must execute. Look for:
Back to top