niobium / pixel workshop
give them a purpose
Describe a job. Review a teammate. The bot-build skill designs their voice, character, companion and access from the capabilities on your gateway.
01 / describe
“A sharp-tongued night-shift security witch for my VPS logs, with a tiny three-eyed bat. Ask before restarting anything.”
The skill writes a 120–600 word operator briefing: expertise, working habits, a quirk, voice, approval boundaries, collaboration and delegation. A playful edge stays adult, opt-in and non-explicit.
02 / review
The preview shows the name, role, traits, briefing, adult age, 48×48 character recipe, named companion, tools, skills and requested connections. Network, shell and filesystem access can be changed before creation. No profile is created while the model is designing it.
If the model is unavailable or its response fails validation, the preview is clearly labelled as a local template. Unavailable and disallowed capabilities are excluded.
03 / create
Niobium creates a Hermes profile, writes its briefing, pins reviewed toolsets and skills, disables inherited MCP servers, keeps command approvals manual, and saves the PixelSpec in profile metadata. The model credentials are inherited from the default profile.
Connection requests do not authorize accounts. Workspace and network isolation are enforced on the Hermes host. If setup fails after creation, Niobium identifies the incomplete profile instead of creating another one silently.
04 / work together
Pixels collaborate in persistent DMs and group rooms. A companion helps with a bounded subtask through Hermes’ delegation tools. The parent remains responsible for checking and combining the results.