Notion 3.7 Agent Skills: Turn Your Best Prompts into Team (or Solo) Shortcuts
Good prompts die in chat history. Solo freelancers and tiny studios repeat the same ritual every week: rewrite this like my brand, turn notes into a PRD, make an exec brief. Notion 3.7 (15 Sep 2026) adds reusable Agent skills — and export to Claude Code, Cursor, Gemini, Grok, and friends. You need a “build three skills this week” guide, not a feature dump.
This is a skills-library playbook for freelancers. Plan gates for Custom Agents / MCP / post-meeting automation should be re-checked on Notion’s live plans page before you upgrade.
Affiliate disclosure: some Notion or tool links may be affiliate later. Feature availability below is from Notion’s 15 Sep 2026 release notes as of 21 Sep 2026 (SAST) — re-check plan gates and pricing before you commit. Not a guarantee of hours saved or client wins.
What a “skill” is (reusable instructions, not another chatbot personality)
A skill is a reusable instruction pack that teaches Notion Agent how you work. Not a cute persona. Not a one-off chat. Examples from Notion’s own framing: generate a monthly business review in your team’s format; critique a doc the way your lead would; turn raw notes into a PRD.
You create a skill once (often by chatting with Notion Agent), park it in a skills library, then run it with / in an Agent chat when you need it. Related skills can live in a Notion database so a studio shares one hub and stays on the latest version.
That is the opposite of “paste the same mega-prompt from Notes every Monday.” If you already keep proposal prompts in ChatGPT, this is the same idea — stored next to the work: ChatGPT prompts for freelance proposals.
Solo freelancer setup — skills library without a big team
You do not need a 40-person ops team. Solo setup that works:
- Create a private Skills database (or page) in your workspace.
- Add three properties at most: Job type, When to run, Export target (Notion only / also Cursor / also Claude Code).
- Write skills in plain language: input → steps → output format → “never do X.”
- Run via
/in Agent chat; paste the client page or meeting notes as context. - When a skill stabilises, export the
SKILL.mdNotion generates if you also work in Cursor or Claude Code — same instructions, less drift.
Notion can also suggest skills from work you already do. Use that as a starter list, then delete anything fluffy. Async clients across time zones benefit when every status brief looks the same — packaging only; we are not inventing hour-savings stats.
Worked mini-example: take the proposal opener you reuse for web MVPs. Skill name “MVP proposal polish.” Input = bullet scope + deadline. Steps = tighten problem statement, list three deliverables, add assumptions, end with a single next-step question. Output = Markdown the client can paste into email. Never-do = no fake case studies, no “guaranteed ROI.” Run it twice this week; keep the edit that made the second pass cleaner.
For the broader “stop retyping the same reply” habit outside Notion, see Automate the replies you type every day.
Three starter skills to ship this week
1. Proposal polish Input: rough scope notes + your rate card rules (no secrets). Output: client-ready proposal sections — problem, approach, timeline, assumptions, next step. Never: invent testimonials, guarantee outcomes, or change your published rates.
2. Meeting → action list Input: messy notes or transcript summary. Output: decisions, owners, due dates, open questions — table format. Never: invent attendees who were not there; never auto-email clients without your review.
3. Client status brief Input: this week’s tasks + blockers. Output: five-line exec brief — done / next / risk / ask. Never: paste unpaid invoices, passwords, or private Slack drama into the skill text itself.
Ship all three as separate skills. Run each once on a real (non-secret) job. Edit the instruction after the first ugly output — that edit is the skill.
Writing-tool landscape still matters when the skill’s output needs a second pass: Best AI writing tools 2026.
Exporting skills to Claude Code, Cursor, Gemini, Grok
When the work leaves Notion — coding agents, terminal agents, other chat UIs — Notion can write the skill as a SKILL.md plus approved supporting files. Download into Claude Code, Codex, Cursor, Gemini, or Grok. When the Notion copy changes, Notion marks it so you know to pull the latest.
Practical rule: Notion stays the source of truth for the instruction. Local agents get a copy. Do not maintain three divergent versions of “proposal polish” in three apps.
Export when: you already live in Cursor for client MVPs, or Claude Code for repo work. Skip export when: the skill only ever runs on Notion pages (status briefs, meeting cleanup).
One trap: exporting once, then editing only the local copy. Two weeks later Notion and Cursor disagree on tone rules. Fix: change the skill in Notion first, pull the fresh SKILL.md, then re-run the local agent. Same habit as keeping one rate card — one source of truth.
Buy/skip sheet: Free/Plus habits vs Business/Enterprise agent features
| Need | Stay on Free/Plus habits | Lean Business/Enterprise agent features | Skip / wait |
|---|---|---|---|
| Reusable prompts for solo work | Build a skills library; run with / | Only if you need Custom Agents at scale | If you never reuse prompts |
| Auto post-meeting recap → DB | Manual skill run after calls | Custom Agents post-meeting automation (Notion: Business/Enterprise) | If you hate meeting notes entirely |
| Connect GitHub / Amplitude via MCP | Skip until you need it | Custom MCP connections (beta; Notion: Business/Enterprise) | If tools are already elsewhere |
| Sub-agents for multi-step workflows | Keep skills small and sequential | Custom Agents calling sub-agents | If you have one simple job type |
| Export skills to Cursor / Claude Code | Yes — when work leaves Notion | Same export; plan for Agent seats separately | If you never leave Notion |
Re-check Notion’s live plan matrix before you pay — do not invent Free vs Business skill caps from memory. Release notes put Custom Agents, MCP connect, post-meeting automation, Agent SDK, and related admin APIs on Business/Enterprise with some items in beta.
What not to put in a skill
- API keys, passwords, payroll files, unpublished financials
- Client PII you would not put in a shared Google Doc
- Unreviewed legal clauses presented as “approved language”
- Promises of income, rankings, or guaranteed outcomes
- Blanket “always send to the client” automation without a human confirm
Skills encode process. Secrets and final legal sign-off stay outside.
This week — create one skill from a prompt you already reuse weekly
Open last week’s chat history. Find the prompt you pasted at least twice. Turn it into one Notion skill with: name, input, steps, output format, never-do list. Run it on one real non-secret page. Export only if you will use the same skill in Cursor or Claude Code this month.
Sources: Notion 3.7 release (15 Sep 2026), Notion Help, Notion AI product — re-check plan gates at paste time.
Soft next step
If you want the 3 starter skills worksheet on one page (~$2–3 / R30–50), that’s the printable sheet. Everything above stays free.
Get the 1-page 3 starter skills worksheet
Optional one-page printable of this free guide. Not a guarantee of clients, savings, or income.