close-arc
Skill6 starsChanged 3 months agoNo licenceView on GitHub
Close an open **arc** — mark its narrative complete (`closed`) or explicitly set aside (`abandoned`), and audit that its closing conditions were actually met. Use this when the user says things like "close the X arc", "we're done with this arc", "abandon arc Y", "wrap up the arc". An arc cannot be `closed` while any of its inquiries are still `open` — this skill invokes `vault_check_transition` to enforce that and surfaces the blockers concretely. Arcs that trail off without explicit closure are the vault's biggest smell; spending two minutes on this skill is how that's avoided.
In this repository26 other files it gives its agents.
- document-featureSkill
- recommend-skillsSkill
- seed-skill-templateSkill
- architecture-diagramSkill
- catchupSkill
- dataflow-diagramSkill
- engineering-journalSkill
- format-layout-diagramSkill
- review-exchangeSkill
- review-guideSkill
- rust-source-layoutSkill
- sharable-artifactSkill
- sweep-commentsSkill
- technical-proseSkill
- define-scopeSkill
- discussSkill
- frame-problemSkill
- open-arcSkill
- open-inquirySkill
- plan-featureSkill
- propose-designSkill
- reconcile-vaultSkill
- record-decisionSkill
- submit-explorationSkill
- synthesizeSkill
- vault-searchSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 5 are distinctive, and 7 are 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.
7
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.