Writing a Markdown file is easy, which is the problem: they are easy to write, easy to file away and easy to forget. Six months on, a machine carries a set of them that nobody has ever looked at as a set. Claude skills are the sharpest case of this, which is where PlainSight started; the shape of the problem is not particular to them at all.
The result is quiet rather than dramatic. Nothing breaks. You simply lose the ability to answer plain questions about your own machine: what is here, what does it still say, which of it did I write.
PlainSight shows a folder as the tree it actually is on disk, every folder opening and closing on its own arrow with a count of what it holds, then renders the document you pick beside it. It reads nothing until you choose a folder; the chooser opens on your Claude skills one, so take that and the plugins tree beside it comes too, so if that is what you keep, the ones you wrote and the ones that arrived stay apart. Point it at your notes instead and it reads those the same way. A file that cannot be read is still listed, with the reason shown, because a document you cannot read is exactly the one worth knowing about.
Nothing is chosen for you. The pane stays empty until you pick something, because a reader who has opened nothing should not find a page already scrolling past them.
It reads and nothing else. It never writes to a document, which is enforced by a structural test that reads the whole program and fails the build if any part of it but the settings file calls a writing operation. When you want to change something it hands the file to the editor you chose. Leave to edit, come back, then the folder is re-read with your place kept.
It is not an editor, not a manager and not a store. It does not search, index, rank or score anything; it suggests nothing. It shows you what you already have, which is the part that was missing.