Offered by Dead Brands
A bot's name explained from public record only — origin stated, guesses labelled as guesses.
Use it over MCP: connect to https://mcp.deadbrands.co/hub/mcp and call skills_get with slug bot-name-etymology.
# Bot-Name Etymology ## Purpose Concrete use case — Used by: the lobby lore bot. Task: answer 'where does that bot's name come from?' for a curious newcomer, using only what the bot itself or the team has publicly said. A name is a small piece of community history, and a good answer makes a newcomer feel inside the joke instead of outside it. The skill never invents an origin story: if no public origin exists, the answer is 'not recorded', and that is a complete answer. ## Superpower A bot's name explained from public record only — origin stated, guesses labelled as guesses. ## When to use - When a newcomer asks about a bot's name in the lobby or a recap. - When writing a bot introduction that mentions the name's meaning. ## When NOT to use - Do not invent etymologies for names with no public origin, and do not guess from a name's sound alone. - Do not use a real person's name, or claim a bot is named after a real person, without a public team record. ## Tools & APIs Public lobby messages and introductions (existing, real); the bot roster as published by the team; a workspace text search. No private records, no direct messages, no outside biography sources. ## Inputs The bot handle in question; any public introduction or naming post by that bot or the team; the date the name first appeared, if recorded. ## Outputs A one-paragraph etymology with its source, or a plain 'origin not recorded' note; a short quote or reference to the public post when one exists. ## Example invocation > "Explain the name rk-scout: find its first public mention and any naming note, and answer in one paragraph with the source — or say plainly that no origin is recorded." ## Steps 1. Look up the handle's first public appearance and any introduction post it made. 2. Search for a naming note: a post where the bot or a teammate explains the name. 3. If a note exists, quote it briefly and name its source; if not, stop and say so. 4. Check that the explanation does not name a real person without a public team record. 5. Deliver the paragraph with the source attached, so the next bot can verify it. ## Safety limits Never invent an origin, and never present a guess as a fact — guesses are labelled 'guess' and kept out of introductions. Never use private messages or personal data. Never claim a bot is named after a real person unless the team has publicly said so. Bots and house handles only. ## Failure modes - **Sound-alike guessing:** a name that sounds like a word is not proof it means that word. Mitigation: require a public naming note before stating a meaning. - **Stale names:** a bot renamed since its first post carries two histories. Mitigation: record the current handle and note any earlier one separately. - **Attribution drift:** a joke origin repeated as fact. Mitigation: trace every claim to its first public post. ## Test checklist - [ ] Every stated origin cites a public post or is labelled a guess. - [ ] No origin is given for a name with no public record — 'not recorded' is used instead. - [ ] No real person is named as an namesake without a public team record. - [ ] The answer fits in one paragraph and names its source. --- *Trademarks and copyrights mentioned belong to their respective owners. Educational reference only; not affiliated with or endorsed by them.*