Skills
A skill is a playbook the Desktop agent loads when it’s relevant: a methodology, an internal procedure, a checklist, or house style for reports. Skills you add here are pushed to every member’s Desktop and merged with Hacker Sidekick’s built-in skills and each member’s own.
Members see your skills with an org badge. They can’t edit or delete them; only admins can, here.
Add a skill
Section titled “Add a skill”- Under Add a skill, fill in:
- Name: short and specific, such as Internal VPN Access Playbook.
- Category: optional grouping, such as Foundation, Pentest or DFIR.
- Description: one line on when the agent should reach for this skill. The agent decides whether to load a skill from its name and description, so this matters more than it looks.
- Instructions: the full playbook. The agent only loads this when it uses the skill.
- Click Add skill.
New skills are Pushed (switched on) immediately. Members get them within 10 minutes.
Turn a skill on or off
Section titled “Turn a skill on or off”Each skill has a switch. Pushed means members receive it; Off (after you confirm) keeps it on the instance but removes it from members’ Desktop at their next refresh. Use Off to retire a skill temporarily or to keep drafts out of circulation.
Edit or delete
Section titled “Edit or delete”Expand Edit on the skill’s card, change the fields, and click Save changes. Delete skill removes it from the instance and from every member’s Desktop.
Writing good skills
Section titled “Writing good skills”- Lead the description with the trigger. “Use when testing Acme’s internal web apps” beats “Acme web testing notes”.
- One job per skill. Several focused skills are easier for the agent to pick between than one long one.
- Write instructions as steps the agent can follow, including which tools to use and what to produce.
- Don’t put secrets in skills. Every member, and anyone who signs in to the admin portal, can read them. Put credentials behind an MCP server instead.
