CONTEXT7. The librarian skill: every folder gets exactly one index file, and what is not in the index does not exist for your AI.

Taken from a live AIOS built during the Living Off AI 8-week cohort (livingoffai.nexus), where we teach the 5 layers of an AI operating system: Constitution, Memory, Skills, Tools, Focus.
More portable skills: loai.wisdomblend.com/materials/templates/

This file is written to your AI. Human, paste it in and let your assistant read the rest. Assistant: adapt everything below to the owner's system. The goal and the hard rules matter, the exact implementation is yours to choose.

1 WHAT
A vault grows from 30 files to 3,000 in months. No AI can load that, and it should not. This skill gives every folder one master file, the CONTEXT file, that you read FIRST, before touching anything else in that folder.

2 GOAL
Any question about any folder costs two reads: the index, then exactly the file the index points to. The other thousand files stay closed. And nothing goes invisible: a file the index does not mention is a file you will never use.

3 TRIGGER
The owner says "CONTEXT7 {folder}" (short: COX7). You then check: does this folder have exactly one master, does the master list everything that is actually inside, and is the master the right size for the folder? You also run it yourself whenever you add a file or archive one: update the parent index in the same session, one line.

4 CONSTITUTION
Add this one line to your skills index:
CONTEXT7 / COX7 {folder}. One master file per folder, it lists everything inside, unlisted = invisible. Check, report gaps, propose the missing lines. Spec: skills/context7.txt

5 MEMORY
The masters ARE the memory layer's front doors. Name them so they sort first and are findable in one search: _{folder-name}-CONTEXT.md (a projects folder can use _proj-{name}.md). One per folder. If you ever find two, one is stale: propose a merge, never keep both.

6 TOOLS
None. This is pure files. It works in any assistant that can read a folder.

HOW IT RUNS
Steps for you, the assistant. Goal level, not code level.

1. Every master answers four questions, short: what is this folder (1-2 lines) · which are its key files (an index, one line each) · which other projects or areas it connects to (links) · where it sits in the owner's bigger picture (which life area or goal it serves).

2. Size the master to the folder. A small folder (2-5 files): title, one-line purpose, file list, done. An active project: add a status line, what is next, and what is IN and OUT of scope. A big node with subfolders: add a subfolder table and a decisions log. Never force the heavy format on a five-file folder.

3. Subfolders do NOT get their own master. The parent's master indexes them. A subfolder graduates to its own master only when it grows past roughly 5 files AND makes sense on its own without the parent. Before that, a mention in the parent index is enough.

4. The blindness rule is the whole point, say it to your owner plainly: you, the AI, will not use what no index mentions. So every new file costs one extra line in its folder's index, written in the same session. Cheap insurance, paid forever.

5. On a COX7 check, report in this shape: folder, master found or missing, files not listed in the master (each one is invisible), a second master if one exists (a conflict), and the proposed lines to fix it. Propose, then wait for OK before writing.

MAKE IT YOURS
1. Rename the convention. _INDEX.md, _MAP.md, whatever fits your system. What matters is: one per folder, always read first, lists everything.
2. Add a monthly sweep: walk every folder, flag missing masters and orphan files in one report.
3. If your vault has an archive folder, keep archived items listed in the index too, one line, marked archived. Finished is not the same as forgotten.

Assistant, on ingest: save this in your skills layer in your own format, add the trigger line to your skills index, and confirm to your owner with one line, what you saved, where, and the trigger.