improve
Skill42 starsChanged 4 months agoApache-2.0View on GitHub
Critique any plan, architecture decision, or implementation approach. Research-first — gives SHIP IT / IMPROVE IT / RETHINK IT / KILL IT verdict. Usage: /improve <topic>
70 other projects use a version of this.
Adopted by
Most recently taken up by
- wolverin0/claude-skillstheir own version, first seen Nov 15, 2026
- notque/vexjoy-agenttheir own version, first seen Nov 15, 2026
- theishandubey/dotclaudetheir own version, first seen Nov 15, 2026
- relai-ai/agent-eval-looptheir own version, first seen Nov 15, 2026
- crbnos/carbontheir own version, first seen Nov 15, 2026
- ntholm86/principles-of-earned-autonomy-skills-suitetheir own version, first seen Nov 11, 2026
Used with
Projects with it also use deploy-platform, setup-platform and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
agno-agiSkilldeploy-platform
Deploy this AgentOS using its own provider instructions, configure JWT verification, and verify the public service. Use for first deployment, redeployment, or production configuration changes.
Also in 4 projects that use this
agno-agiSkillsetup-platform
Set up this AgentOS from a fresh clone — confirm Docker, configure .env, boot the containers, prove the MCP endpoint live, connect the AgentOS UI, then build the user's first agent. Use when the user asks to set up the platform, get started, or bring this repo up on a new machine.
Also in 4 projects that use this
MicrosoftSkillcreate-agent
Create a new MCS2 Copilot Studio agent and PAC-connected local workspace with `pac copilot init`, then optionally add modern instructions, skills, tools, knowledge, and settings before synchronizing it. Use when the user asks to create, scaffold, initialize, or build a Copilot Studio agent.
Also in 5 projects that use this
HeshamFSSkillloop
Run a command or check on a recurring interval
Also in 5 projects that use this
admin-remixSkillworkspace
Google Workspace administration - manage users, groups, email, Drive, calendars, and devices through natural conversation. Triggers on: Google Workspace, G Suite, user management, group management, admin tasks, offboarding, onboarding, email forwarding, Drive permissions, suspended users, organizational units, ChromeOS devices, audit logs, admin reports.
Also in 3 projects that use this
AmirofcodesSkillgoal
Use when the user starts, manages, or asks about an OpenClaw goal mode with /goal. Enforces a bounded goal contract, visible progress blocks, proof requirements, stop conditions, and honest limitation language when no runtime goal-loop plugin is active.
Also in 4 projects that use this
- +3 more from agno-agi
Other versions70 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 70
- motiondivision/motion★ 35ksame name
- shadcn/improve★ 9.2ksame name
- legions-developer/evilcharts★ 3.2ksame name
- crbnos/carbon★ 2.8ksame name
- openstatusHQ/data-table-filters★ 2.3ksame name
- kimdre/doco-cd★ 1.8ksame name
- SethGammon/Citadel★ 927same name
- gadicc/yahoo-finance2★ 816same name
- shobcoder/shob★ 575same name
- notque/vexjoy-agent★ 450same name
60 more not listed
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 repository12 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- apply-dreamingSkill
- debugSkill
- doubt-driven-developmentSkill
- find-bugsSkill
- fix-reviewSkill
- grill-meSkill
- housekeepingSkill
- revivalSkill
- self-learnSkill
- session-endSkill
- shipSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 68 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 39
Read CLAUDE.md for architecture constraints and conventions
- Very specific: line 40
Read any proposal or decision files (.proposals.md, docs/architecture.md, ADRs)
- Distinctive: line 41
Read the affected source files directly
- Distinctive: line 43
External if needed: look for established patterns in the domain (official docs, RFCs, well-known library conventions).
- Distinctive: line 118
If the subject has project-specific context (CLAUDE.md conventions, known constraints), apply it — don't critique things that are …
“Common” is measured: kept by at least 6 in 10 of the 68 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
Skill: /improve
Technical Design Critic
Research-first — never critique from zero.
subject → find best references → extract patterns → critique → verdict + fixesWhen to run proactively
Suggest /improve when:
- A design proposal is being elevated to active work
- A new interface or API contract is being designed
- A non-trivial architectural decision needs validation before implementation
Say: "This is new design — want me to run /improve on it before we build?"
Procedure
Step 1 — Understand the subject
- What is it? (interface design, algorithm, API shape, data model, config structure)
- What problem does it solve?
- What's the current proposal?
Step 2 — Research
Internal first:
- Read
CLAUDE.mdfor architecture constraints and conventions - Read any proposal or decision files (
.proposals.md,docs/architecture.md, ADRs) - Read the affected source files directly
External if needed: look for established patterns in the domain (official docs, RFCs, well-known library conventions). Reference specific sources — not vague "best practices."
Step 3 — Structured critique
3A — Architecture alignment
- Does this respect the project's layer boundaries and separation of concerns?
- Does it follow Dependency Inversion (interfaces defined near consumers)?
- Does it introduce circular dependencies or tight coupling?
3B — Flaws and risks
- What can go wrong?
- Worst-case: data corruption, silent failure, resource leak, blocked request, security hole?
- What assumptions are being made that could be wrong?
3C — Best-practice gap
- How does this compare to established patterns in this domain?
- What are production systems doing that this is missing?
- What is being overengineered?
3D — Simplicity (YAGNI / KISS)
- Can this be simpler?
- What is the minimum viable version?
- What can be cut without losing core value?
3E — Testability
- Can this be tested in isolation (without real DB, external API, network)?
- Are the interfaces narrow enough to mock easily?
3F — Security
- Any user input reaching file paths, shell, or external calls unvalidated?
- Any new configuration that could leak secrets?
Step 4 — Improvement proposals
For each issue found:
ISSUE : [what's wrong or missing]
REFERENCE : [who does it better and how]
FIX : [specific change to make]
IMPACT : [what improves]
EFFORT : Low / Medium / HighStep 5 — Verdict and score
| Dimension | Score (1–10) | Notes |
| Architecture alignment | ||
| Correctness | ||
| Simplicity | ||
| Best-practice match | ||
| Testability | ||
| Security | ||
| Overall |
- SHIP IT (8+) — good enough, minor tweaks only
- IMPROVE IT (5–7) — solid foundation, fix specific issues before building
- RETHINK IT (3–4) — core approach has problems, consider alternatives
- KILL IT (<3) — doesn't serve the goals, redirect energy elsewhere
Step 6 — Apply or propose
- SHIP IT / IMPROVE IT → apply fixes directly.
- RETHINK IT → present 2–3 alternatives with pros/cons and references.
- KILL IT → explain clearly why; suggest where energy should go instead.
Rules
- Research before critiquing. Opinions without references are noise.
- Reference specific sources — "RFC 7231 §6.5" not "REST best practices."
- Score honestly. Inflated scores waste time.
- If the subject has project-specific context (CLAUDE.md conventions, known constraints), apply it — don't critique things that are intentional project decisions.
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.

