Skills

A skill is a workflow Brain has learned and can replay on demand. Sales follow-ups, weekly syntheses, coachee check-ins, deal-room digests — anything you do more than once and want consistent.

You should turn a workflow into a skill when:

• You do it more than once a week.
• You want consistent format / tone / structure each time.
• It involves multiple tools (mail + calendar + CRM, say).
• A teammate would benefit from the same recipe.

You don’t need a skill for one-off tasks — just ask Brain in plain English.

Type /create-skill — or just say “help me build a skill”. You can start from scratch, or right after Brain has done a workflow you want to keep.

/create-skill

Brain interviews you with a few quick questions — the goal, when it should fire, what it needs, and one example — then drafts a complete skill (trigger, parameters, steps) from your answers, instead of leaving you in front of a blank template. It also reviews its own draft and tightens it before showing you, so the first version is already solid.

Check the preview, reply to confirm, and the skill is saved to your private vault — available next time you mention it.

Mention it by name in chat:

Run the “weekly Acme synthesis” skill.

Or describe the situation and Brain picks the right skill:

It’s Friday, time for the weekly synthesis.

You can also see your skills with:

/skills

When you correct Brain’s execution of a skill (“not that format — keep the bullet style”), Brain captures the correction in the skill itself. Next run reflects it. To rewrite a skill explicitly:

Update the “weekly Acme synthesis” skill — add a section for next week’s calendar.

To have Brain critique and sharpen an existing skill, say:

/review-skill <name>

Brain reads the skill, proposes a tighter version — clearer trigger, cleaner steps — and you approve before anything changes.

Your skills are private by default, kept in your encrypted vault. When one is worth spreading, share it with your team:

/share-skill <name>

This publishes it to your organisation — everyone on your verified email domain. Teammates browse shared skills with /org-skills, preview one with /org-skill <name>, and import it into their own vault. You can also browse the team gallery in your browser at org.nitroxbrain.com.

Anything Brain can do in normal chat:

• Read from your connected accounts.
• Draft mail, summaries, slides outlines.
• Create calendar events.
• Update HubSpot deals.
• Save notes to your vault.

A skill is not magic — it’s a recipe that uses the same building blocks as any other Brain turn.

• Send messages without confirmation (still draft-first).
• Use integrations you haven’t connected.
• Run on a schedule (no cron — you trigger them manually).

If a skill runs but produces a wrong result, treat it like any wrong Brain reply: correct in chat, and the next run incorporates the correction. If it consistently fails, ask Brain to show me the skill’s steps and edit them by hand.