agentleFS
iwe-orgiwe-org/dev-workspace/.claude/skills/iwe/SKILL.md

iwe

Skill11 starsChanged 2 days agoMITView on GitHub

The iwe CLI reference for this workspace — reading documents and hubs, finding by title, text, frontmatter or graph position, creating, renaming and deleting without breaking links, normalizing 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

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 1

    1. iwe-org/marketing-workspace★ 624% 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.

  • In this repository8 other files it gives its agents.

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
  1. Very specific:

    Every command runs from the workspace root.

    line 8
  2. Very specific:

    Run iwe normalize after any manual edit, then iwe schema validate before you call the change done.

    line 45

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

The iwe CLI

Every command runs from the workspace root. A document's key is its extension-less path (data/spec/timer).

iwe retrieve -k data/spec/timer                                  # read a doc
iwe retrieve -k data/plans --expand-includes 1                   # hub + children
iwe find --fuzzy timer -f keys                                   # fuzzy title+key match
iwe find --lexical "session log storage" -f keys                 # full-text ranking
iwe find --included-by data/plans -f keys                        # all docs under a hub
iwe find --references data/spec/timer -f keys                    # backlinks
iwe find --filter '{stage: done}' --included-by data/plans-archive:0 -f keys  # frontmatter query
iwe tree -k data/plans -d 2                                      # subtree overview
iwe new "My plan" --key data/plans/20260801-my-plan --content "" # create at an explicit key; the title is required
iwe update -k data/features/foo --set stage=accepted --unset status  # set and remove frontmatter fields
iwe rename <old-key> <new-key>                                   # move; references auto-update
iwe delete <key>                                                 # delete + reference cleanup
iwe normalize                                                    # run after manual edits
iwe schema validate                                              # the gate (exit 0 = clean)
iwe stats                                                        # counts; Broken Links and Orphans sections only when there are any

Filters are YAML ($eq, $ne, $in, $gte, $exists, …), not jq. Structural anchors: --includes, --included-by, --references, --referenced-by, --roots.

Rules

  • Move and delete with iwe rename and iwe delete, never mv or rm: they update every link in the graph and print how many documents they changed. The reference updates are part of the change; in a git repository, git diff shows them. iwe delete removes inclusion links to the document and turns inline links to it into plain text, which is then yours to reword or remove.
  • iwe new reads the document body from piped input when it gets no --content, and waits for it; pass --content "" for an empty document.
  • --set FIELD=VALUE parses the value as YAML, so a value that contains a colon and a space needs quotes of its own: --set 'description="Version 0.2.0: break timers."'.
  • Run iwe normalize after any manual edit, then iwe schema validate before you call the change done.
  • iwe schema validate --explain shows which schema a document is bound to when a validation result is unexpected.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.