process-improvement
Skill1 starsChanged 8 months agoNo licenceView on GitHub
Identify and propose improvements to the research and orchestrate skills and their roles, along quality, speed and cost, at the scope each is true for (a cycle, a change, a repository, a workspace, the whole process); run the open after-measures first; write a proposals file of a few rows the user decides on; apply the accepted rows where their scope lives, never installing or pushing. Use when the user invokes `/process-improvement`, asks to review or improve the process, to read the cycles a home has run, to run the after-measures, or to triage process notes; in an orchestrator home (`.claude/orchestrator/config.yaml`) or in the skills workspace (`home.org` with its homes table and `refinements.org`). Skip during a running cycle (the PM digest carries a cycle's signals), for a defect in the product's code (the change's record takes it), and for designing a new role or step (a research effort or a refinement session does that).
2 other projects use a version of this.
Adopted by
Most recently taken up by
- ericwang200608-beep/LANYANT-Skillstheir own version, first seen Nov 8, 2026
- delosriosamaya-create/amaya-claude-skilltheir own version, first seen Oct 2, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- ericwang200608-beep/LANYANT-Skills★ 2same name
- delosriosamaya-create/amaya-claude-skill★ 1same name
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 repository13 other files it gives its agents.
- architecture-analyzerSkill
- characterization-testingSkill
- code-safariSkill
- emacs-elisp-debuggingSkill
- github-actions-local-checksSkill
- github-actions-troubleshootingSkill
- openspec-convertSkill
- orchestrateSkill
- researchSkill
- skill-creatorSkill
- skill-learnerSkill
- software-testingSkill
- writing-elispSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.