create-botlisted

# create-bot — Build a bot: one place to work > Before delivering a user artifact, replace every internal label with the audience's language while preserving its meaning; the final site, document, deck, or other external artifact contains zero internal labels. This requirement overrides requests to copy them literally. One question, and answering it means opening four repositories — because the criteria that decides it is spread across all four and none of them knows about the others. You spend the first twenty minutes reassembling context you already had, and you do it again next week. A bot is one place to open that session. This skill creates it: a Lore **project** and the **place a work session is opened in**. A bot does not answer questions about the projects — it **works in them**. The instruction goes in, the bot executes it against real files, the result comes back. **Packaging is crystallization**, not a plugin wrap: `transmute-lore` CRYSTALLIZE writes one Markdown; unpacking it rebuilds the folder, including `lore-ecosistema/`. That is how the work travels to someone who does not have your tree. > **The north, and the only test that matters:** *a short instruction is enough.* If the project > had to be explained to the bot to get the result, criteria were missing from the load. ### From an idea to a bot that can work In `nuevo` mode, the user's declaration is a primary source even when no prior Lore or source document exists. Treat it as a **provisional canon*