file-note
Skill0 starsChanged 12 days agoMITView on GitHub
Sort one note into the correct myOS layer folder, conservatively. Use to file a single note; it leaves + flags anything ambiguous rather than misfiling.
In this repository14 other files it gives its agents.
- captureSkill
- capture-to-inboxSkill
- escalate-to-architectSkill
- interview-meSkill
- janitorSkill
- migrateSkill
- process-inboxSkill
- recallSkill
- resumeSkill
- scanSkill
- selftestSkill
- taskSkill
- weekly-reviewSkill
- learn-acceleratorSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 38
Read the note (read_file).
- Very specific: line 42
Now: put it on the properties standard deterministically — don't hand-edit frontmatter: python $MYOS_ENGINES/myos_migrate_note.py --apply …
- Distinctive: line 50
When unsure, leave + flag — an unfiled note beats a misfiled one.
≈ “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
file-note
The atomic vault-sorting primitive. Conservative: misfiling is worse than not filing. When unsure, leave it and flag it.
When to Use
- A single note needs sorting into the right layer folder.
- Called per-item by
process-inbox.
Decision table (top-to-bottom, first match wins)
| The note is… | Folder key (resolve via spine) |
| a raw, unprocessed thought | inbox (leave) |
| messy scratch / experiment | sandbox |
| about an active project | projects |
a dated daily (YYYY-MM-DD) | journal |
| math / programming / coursework | academics (+ subject subfolder) |
| how a system/tool works | systems |
| an external source (book/article/video) | source_material |
| about the myOS system itself | myos |
| retired / superseded | archive |
| none clear, or two fit equally | leave + escalate |
Resolve real paths: python $MYOS_ENGINES/myos_paths.py get <key>.
Procedure
- Read the note (
read_file). - Pick a row. If none clearly wins or confidence < 80% → stop: add
#needs-sorting, runescalate-to-architect, done. Do not move it. - Do not rewrite the body — preserve the user's wording.
- Move the file to the chosen folder (file tool /
terminal mv). By-name[[wikilinks]]survive the move. - Now put it on the properties standard deterministically — don't hand-edit frontmatter:
python $MYOS_ENGINES/myos_migrate_note.py --apply "<new path>". Run it after the move so thetype:is inferred from the destination folder (idempotent; body untouched). Seemigrate. - Report:
filed "<title>" → <folder>orflagged "<title>" #needs-sorting.
Pitfalls
- Never delete. "Remove" = move to the
archivefolder. - Knowledge-layer notes must read fine without plugins (no Dataview/Templater in them).
- When unsure, leave + flag — an unfiled note beats a misfiled one.
Verification
- Filed: the note now resolves under the chosen folder (
python $MYOS_ENGINES/myos_paths.py get <key>) and nowhere else. - Flagged: the note carries
#needs-sortingand an escalation was queued.
Cadence
On demand, or per-item under process-inbox.
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.

