purity
Skill2 starsChanged 15 days agoMITView on GitHub
Orchestrates purification agents sequentially to remove code waste.
In this repository21 other files it gives its agents.
- auto-commitSkill
- cleanSkill
- code-reviewSkill
- coverageSkill
- documentSkill
- purifySkill
- refactorSkill
- spae-buildSkill
- spae-checkSkill
- spae-fixSkill
- spae-inspectSkill
- spae-orchestrateSkill
- spae-planSkill
- spae-prepareSkill
- spae-spawnSkill
- spae-specSkill
- spae-verifySkill
- structureSkill
- testSkill
- tipSkill
- troubleshootSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
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
- Very specific: line 18
Run purification subagents sequentially to remove code waste in target code.
- Distinctive: line 41
Always use the subagent tool for subagent invocation.
- Distinctive: line 52
Never run subagents in parallel or concurrently.
- Distinctive: line 62
Every run, halted or not, ended in Report.
- Distinctive: line 69
Keep prose terse while ensuring clarity.
- Distinctive: line 72
Use lists and sub-lists for long sentences and dense paragraphs.
≈ “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.
Files
Purity
When to use
- The user wants to remove code waste autonomously using the
purifyagent.
Goal
- Run purification
subagentssequentially to remove code waste in target code.
Input
- Accept optional arguments (file or folder paths).
Workflow
Halt on any Halt conditions entry after every spawn.
- Purification Loop:
- Spawn a
purifysubagent with the optional argument; await its result. Complete: repeat step 1.No Changes: proceed to step 2.
- Spawn a
- Report: emit the result per Result directives:
Result:Completedwhen the workflow reaches Report without a halt;Haltedwhen a subagent reportsFailed;Failedon any other Halt conditions entry.
Directives
- Always use the subagent tool for subagent invocation.
- Pass the argument verbatim to each subagent; never read or expand file-path arguments.
- Route only from each subagent's
Resultvalue. - Spawn only the subagents the workflow names.
Constraints
- Restrict activities to spawning subagents, reading their results, and reporting; never write files, run git operations, activate skills, or prompt the user mid-run.
- Never run subagents in parallel or concurrently.
- Halt conditions: halt immediately; report per Report, listing
the diagnostic under
Findings:- A subagent
Failedresult. - A subagent result missing or outside the workflow's literals.
- A process failure (crash, timeout,
AgentError).
- A subagent
Verification
- Subagents ran one at a time, in workflow order.
- Every run, halted or not, ended in Report.
- The orchestrator wrote no file.
Result directives
- Minimum words. Maximum signal.
- Return the final execution status block.
- Keep prose terse while ensuring clarity.
- Optimize prose for agent, token, and context efficiency.
- Split actions, findings, and summaries into terse bullet points.
- Use lists and sub-lists for long sentences and dense paragraphs.
- Emit the result template as live markdown—never in a code fence.
- Output nothing outside the template.
Result template
<!-- prettier-ignore-start -->### Execution Summary
- **Actions**:
- [Terse list of actions from spawned subagents]
- **Files**:
- [Terse list of files affected by spawned subagents]
- **Findings**:
- [Terse list of findings from spawned subagents]
- **Summary**:
- [Terse list of summary from spawned subagents]
> **Purity Status** • `[scope]`
> **Result**: [Completed | Halted | Failed]
> **Impact**: [Terse impact statement]<!-- prettier-ignore-end -->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.

