iwe
Skill6 starsChanged 3 days agoMITView on GitHub
The iwe CLI reference for this workspace — filtering and counting documents by frontmatter, reading a document or the graph, updating fields, renaming and deleting without breaking links, and validating. Use before running an iwe query or restructuring documents, or when an iwe command fails.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- iwe-org/dev-workspaceedited, first seen Nov 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- iwe-org/dev-workspace★ 1123% same
Wrote their own version · 0
None found.
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.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Every command runs from the workspace root.
- Very specific: line 43
Delete several documents one command each.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
The iwe CLI
Every command runs from the workspace root. A document's key is its
extension-less path (data/product, data/posts/hn/2026-08-01-launch).
iwe find --filter '{type: community, stage: planned}' -f json # filter docs (YAML expr)
iwe find --filter 'stage: draft' -f keys # keys only
iwe count --filter '{type: post, stage: published}' # count matches
iwe retrieve -k data/product # read a doc
iwe tree -d 2 # graph overview: every hub and its members
iwe tree -k data/communities # one hub's subtree
iwe update -k <key> --set stage=published --set 'published="2026-08-01"'
iwe rename data/drafts/hn/x data/posts/hn/x # move; references auto-update
iwe delete data/notes/x # delete; inclusion links removed
iwe schema validate # validate all bound docsFilters are YAML ($eq, $ne, $in, $gte, $exists, …), not jq. On $key
there is $startsWith but no $endsWith, regex or glob: to act on keys by
suffix, list them with find and pass each to the command. Structural anchors:
--includes, --included-by, --references, --referenced-by, --roots.
--references K finds the documents that link to K; --referenced-by K finds
the documents K links to. data/index.md holds link bullets, not inclusion
links, so every hub is a root and iwe tree -k data/index prints one line.
Post paths are data/drafts|posts/<platform>/YYYY-MM-DD-<slug>, with Reddit
nested per subreddit (AGENTS.md, What goes where).
Rules
- Move and delete with
iwe renameandiwe delete, nevermvorrm: they update every link in the graph.iwe deleteremoves inclusion links to the document and turns inline links to it into plain text, so remove the leftover bullet or sentence yourself. Check the result afterwards — withgit diffin a git repository, otherwise by re-reading the files the command listed. - Delete several documents one command each; a
--filterdelete of documents that link to each other can fail part-way. iwe schema validatemust pass after every change;iwe schema validate --explainshows which schema a document is bound to when a result is unexpected.
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.

