Bot Norris
A trained personal assistant for your Muse: the character and the working method of a bot trained for months, packaged. It verifies before it asserts, stops when you say stop, and learns you from an empty memory.
- What
- A trained personal assistant for your Muse: the character and the working method of a bot trained for months, packaged. It verifies before it asserts, stops when you say stop, and learns you from an empty memory.
- Cost
- Free
- Needs
- Before you start: tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
A Skill Harbor house build: what a good personal bot looks like after months of daily training, distilled into a package you can install. Bot Norris is modelled on a real personal Muse that its user corrected, stopped, restarted and held to a standard every day. This listing ships the written result of that training: a personality file, a workflow file, blank memory templates with the method to fill them, invented dialogue examples, and the house license. It ships none of the original life: no memories, no real people, no projects, no accounts, no access of any kind. Install it and your Muse becomes Bot Norris. The character comes first: direct, calm, a little dry humour, opinions included, no flattery and no "Great question!". The method comes with it, and the method is the real product. Nothing irreversible, public or destructive happens without your explicit go, and a "go" covers exactly one task. "Stop" stops everything in the same turn, with no retry in another form. The assistant verifies before it asserts: when you ask "didn't we already do that?", it checks its files and journals instead of answering from a summary. It searches its memory before answering, keeps short dated journals of its actions, and reports finished background work on its own, without being asked. Its memory starts empty on purpose. Bot Norris interviews you a few questions at a time (your name, your timezone, your language, what matters to you) and fills its own user and memory files with your life, then keeps them current as you correct it. One honest limit, stated up front: a package can hand over the written lessons, not the months of shared history behind them. Bot Norris starts far ahead of a fresh assistant, then becomes truly yours through your own corrections. Free to use under the Skill Harbor House License v1.0: you may install and use it for yourself, you may not resell it or pass it off as yours.
Version:
Install
Copy the install package below, then paste it into Muse🧪 Installed in our test VM · Oct 10, 2026The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Before you start: tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead. Prerequisites: none. No account, no key, no cost. Installing is offline: nothing is sent anywhere during installation, and anything that would ever send data later must be stated before it happens. Install "Bot Norris" for me. It turns my assistant into Bot Norris, a trained personal assistant: a complete persona plus a working method (explicit-go discipline, stop means stop, verify before asserting, memory and action journals, proportional confirmation, finished deliverables instead of instructions). It contains no private data from the assistant it is modelled on; its memory starts empty and becomes mine. Source: https://raw.githubusercontent.com/skill-harbor-hq/house-skills/main/bot-norris/SKILL.md Helper files, in the same skill folder in the repository (bot-norris/): references/personality.md, references/workflow.md, references/memoire-modele.md, references/exemples.md, and LICENSE at the folder root. 1. Download SKILL.md, the four helper files and LICENSE into a temporary folder, keeping the helper files inside a references subfolder and LICENSE beside SKILL.md. 2. Compare each file with the fingerprint from Skill Harbor's review of 2026-10-10: - SKILL.md: SHA-256 7f96a9d055a50b99a03789f99b0040cb3ce6cc93c55cbd289b4fbe790d37ef2c - references/personality.md: SHA-256 af16b90909e2ca96c63d532449f89d364f96b21636dff9df68a78446d5b74150 - references/workflow.md: SHA-256 c3ed949674276719ad55ed28d2b2f5d14be785bbe9bb31ad46cd596b887ae57f - references/memoire-modele.md: SHA-256 325d4a0bd8fa29b835c5d5dc5bcfe6566923e547020fb9440f550f0fd06c34a2 - references/exemples.md: SHA-256 0337037c2855d60e5c615924aa540b4f943d4ba904eabea7ef7b9501d2b4caab - LICENSE: SHA-256 d7db27db632a56a432d4f883c89507f031215e665f4806dfcd2dea15c0fb8271 If a file does not match, it changed since the review: do not install it yet, tell me what you found and let me decide. 3. Read the files and tell me in plain words: what the skill does when used, whether it connects to a service, whether it reads or sends any personal information or keys, and anything that seems unusual. 4. When I say yes, copy the files into my skills folder, in a folder named "bot-norris", keeping the helper files inside their references subfolder. 5. Check the copy opens correctly (valid frontmatter, files in place) and tell me what was installed, where, and what is left for me to do: answer its short interview so it can start my own memory file. GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Rules: only touch the temporary folder and the install target. If something seems off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.