First-week checklist
Your instance arrives with its models and routing already configured by Hacker Sidekick. Work through this list to make it yours.
Day one
Section titled “Day one”- Sign in at
https://<your-instance>/adminand confirm the top-right shows Admin. How to sign in - Confirm your routing policy with Hacker Sidekick: inherit to let the classifier split ordinary and offensive work, or always default / always sensitive to force one tier. Routing policy
Before inviting members
Section titled “Before inviting members”- Write the org system prompt and switch it on. System Prompt & RoE
- Write the RoE template your engagements should start from and switch it on.
- Add your first skills: your methodology, report format, and anything people ask about repeatedly. Skills
- Add MCP servers for internal tools, and decide whether to allow members’ own MCP servers. MCP Servers
- Connect your own Desktop and check you see Managed by, your skills with the org badge, and your MCP servers. Connect Desktop
Rolling out
Section titled “Rolling out”- Send Hacker Sidekick the member list (emails and who should be admin). Members
- Send members the Desktop beta installer and a link to Connect Desktop to your instance. Desktop finds your instance on its own; keep the instance address handy for anyone whose Desktop doesn’t.
- Check User Admin over the next few days to see who has connected.
- Check Audit & Usage after the first week: tier split, error rate, busiest hours. Audit & Usage
