agentleFS
Flop19Flop19/legal-workspace-starter/.claude/skills/file-it/SKILL.md

file-it

Skill8 starsChanged 50 days agoMITView on GitHub

Make a correction or a settled outcome permanent instead of losing it with the session, routing it automatically to where it belongs. This helps the workspace compound.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Don't file one-off mistakes, temporary matter status or unsettled analysis.

    line 13
  2. Distinctive:

    If a topic file becomes difficult to scan and contains distinct subtopics, propose splitting it into more specific files.

    line 37
  3. Distinctive:

    Update a counsel-brief section's As of date when its content is substantively updated or reconfirmed, not merely reworded.

    line 52
  4. Distinctive:

    An entry that already exists gets edited, not duplicated: Check directly related summaries and references, and include any necessary …

    line 54

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

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

File it

Durable facts, positions or feedback get lost when a session ends. This skill routes what should outlast the session to the place it belongs, in the shape that place needs, confirmed before it's written.

AGENTS.md says when to raise this skill.

Don't file one-off mistakes, temporary matter status or unsettled analysis. An authoritative document arriving is a reason to inspect it, not automatically to adopt its contents as a standing position.

Where it goes

Route each item separately, but group related changes into one proposal and confirmation.

  1. Durable knowledge — a conclusion, a fact, or a change to either → knowledge/. The high-level picture every session needs goes in counsel-brief.md, under its matching heading; everything else goes in the knowledge/<topic>.md whose name already covers it — check existing files for overlapping topics before creating a new one. Cite the source where it lives. If a supporting document is in desk/, propose moving it to the relevant matter's docs/ folder or, for company-level documents, knowledge/sources/. Include the move and any reference updates in the filing proposal.
  2. Taste or working style — correct, but not how the user wants it → knowledge/preferences.md, one line carrying the rule and why it matters.
  3. A recurring process is wrong — the steps, format or quality bar of work that repeats → edit the matching skill in .claude/skills/, so the correction applies on every run. If no skill covers it and the issue has come up before, offer to write one.
  4. How every session should behave — a standing rule or routing habit that isn't tied to one procedure → AGENTS.md.

If a topic file becomes difficult to scan and contains distinct subtopics, propose splitting it into more specific files. Move entries rather than copying them, update references, and retain the parent file only if it still contains useful general content. Include the split in the filing proposal.

Writing it

  • Propose the destination and exact addition or replacement; obtain confirmation before writing. Never write into knowledge/, a skill or AGENTS.md silently.
  • Give each distinct fact or position a descriptive heading, followed by Date · Position/Fact · Source. Keep Position/Fact brief — executive-summary style. Date is when the fact or position was established or substantively reconfirmed, not when its wording was edited. Source points to the supporting document or records the user's dated confirmation. Keep counsel-brief summaries concise.
  • Update a counsel-brief section's As of date when its content is substantively updated or reconfirmed, not merely reworded.
  • An entry that already exists gets edited, not duplicated. Check directly related summaries and references, and include any necessary updates in the same proposal.
  • Write the why, and ask if it isn't obvious. Without the reason, the rule can't be applied to edge cases.
  • Confirm in chat what was filed and where.

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.