Teach it your process once — then it's a slash command.
Skills are the department's playbooks: plain markdown files with instructions in your voice. Grantable ships with the core set — prospecting, grant writing, boilerplate, review — and when you describe a workflow of your own, the AI drafts the skill with you. From then on it runs on command.
"Every month you walk the AI through board prep again — pull the year-to-date numbers, use our agenda format, keep it to a page. It does a fine job. It just never remembers how you like it done."
1. the same briefing, again
Mon, June 2
ok board prep: YTD vs budget first, then program updates, our agenda format, keep it to one page…
Mon, July 7
so for board prep — pull YTD vs budget, then program updates, use our usual agenda format, one page max…
the process lives in your head — so you type it out every time, and the fixes never stick
2. written down once
name: Weekly Board Prep
slug: weekly-board-prep
description: Agenda + financial summary for the Friday board sync
1. Pull YTD vs budget from /Library
2. Program updates — one line each
Voice: plain, board-ready, one page
describe it in chat — the AI interviews you, drafts this file, and saves it on your approval
3. now it's a command
/week
/weekly-board-prep yours
Agenda + financial summary for the Friday board sync
/grant-writing
built in
/prospecting
built in
your process, runnable by the whole team — not just rememberable by you
agencies: write it once at the hub and every client workspace gets it
The old way vs. the Grantable way.
You know the old workflow. Here's how it changes.
Re-briefing a capable assistant
- 1
A recurring task comes up
Board prep again — the same job as last month
- 2
Re-explain your process
The steps, the format, the voice — retyped from memory
- 3
Paste last month's example
"Here's the one from May — match this"
- 4
Get a near-right draft
Close — minus the quirks you forgot to mention
- 5
Make the same corrections
The fixes never stick between sessions
- 6
The process stays in your head
When you're out, nobody else can run it
Written down as a skill
- 1
Describe the workflow once
Tell the AI what the skill should do — it interviews you for the details
- 2
It drafts the playbook
A plain markdown SKILL.md: steps, voice, format, what to avoid
- 3
Approve, and it saves
The skill lands in your workspace files under /Skills/
- 4
Now it's a slash command
Type /weekly-board-prep and the whole routine runs
- 5
Edit it like a document
Open the file, sharpen a line, save — no settings panel to fight
- 6
The whole team can run it
Your process, out of your head and into the procedures manual
Put your process in the procedures manual.
Skills are how the department learns the way you work — plain files you can read, edit, and hand to the whole team.