Notion
ProductivityCommonly used with
Skills using Notion (67)
agency-os
Notion-as-source-of-truth dispatch board for running your work like an AI agency. One Tasks database is the source of truth; tasks flow Suggestion through Discussion, To-Do, In Progress, and Done with subtasks, recurring cadences, dependencies, and template subtrees. Batch execution fans approved To-Do rows out to parallel agents with per-task model selection. Use when capturing chat to Notion, running the To-Do queue, suggesting, approving, or discussing tasks, or coordinating multi-task batches. Trigger with "/agency-os" subcommands or natural-language variants ("add a suggestion: …", "let's discuss X", "run the queue").
notion_synthesize
Synthesize durable ktx wiki pages and semantic-layer sources from staged Notion pages, databases, data-source rows, and clustered Notion evidence. Load when a WorkUnit contains Notion raw files or Notion evidence chunks.
deep-research
When you want multi-source, multi-step research on a topic — competitor research before a sales call, market research for a new business idea, positioning angles, due diligence on a partnership or podcast guest, tech decision research (which DB, which auth), or any "I need to actually understand X." Combines WebSearch, WebFetch, agent-browser, /last30days (Reddit/X/YouTube/HN/web recency), memory, and Notion. Outputs a structured brief with citations, contradictions, gaps, and recommended next steps. Archives every research run to ~/.config/makerskills/deep-research/archive/ so past work is searchable. Triggers on "/deep-research," "research X," "investigate X," "do a deep dive on X," "look into X," "what's actually happening with X," "due diligence on X," "validate this market." Differs from a one-shot WebSearch: this is multi-pass with verification.
api-mapping
Record and analyze API surfaces of web services
parse-calendar
Parse a monthly content calendar from DOCX, XLSX, Notion, or pasted text into structured calendar-data.json — the source of truth every downstream skill reads. Triggers on "/parse-calendar", "parse the calendar", "import this calendar", "here is the month", "load the content plan", "calendar to JSON", or whenever a client calendar arrives in any format. No calendar yet? /socialforge:ideate-month drafts one in this exact shape.
notion-databases
Query and update Notion databases with explicit database identity, property-aware inputs, bounded reads, and confirmation before material writes.
notion-knowledge
Search connected Notion pages and databases, verify the relevant sources, and produce concise answers that preserve links and uncertainty.
notion-doc
Notion design skill that MUST be used whenever creating documents. When the user asks for a document, report, summary, meeting notes, or review write-up in HTML/Markdown, load this skill first. The content decides the document's structure and outline; this skill only governs the Notion blocks (callouts, toggles, tables, checklists, code, columns, etc.) and visual style.
cf-style-guide
Import a brand voice profile from an existing style guide — a .docx/.pdf document, a URL, or manual input — extracting tone, formality, personality, approved/banned terminology, compliance guardrails, and author profiles into a structured brand-profile JSON at ~/.claude-marketing/{brand-slug}/Brand-Guidelines/, then configure the tracking backend (Google Sheets + Drive, Airtable, or local). Triggers on "/contentforge:cf-style-guide", "import our style guide", "set up a brand from this document", "update the brand profile with new guidelines", "extract our banned terms and disclaimers". Deterministic parsing, no agent. The saved profile is read by every pipeline phase — drafting, brand compliance, humanizer; pairs with /contentforge:brand-setup and /contentforge:cf-switch-backend.
notion
Notion workspace — read/write pages, databases, search, create tasks via Notion API
tasks
Task & project management — GitHub Projects (native), Linear (API), Notion DB (API)
domain-search
Check domain name availability accurately across TLDs using registry RDAP APIs and registry whois. Use when the user asks to check, find, brainstorm, or verify domain names, or asks whether a domain is available, for sale, or expiring.
notion
Search, read, create and update pages and databases in your Notion workspace via the Notion API. Use when the user asks to find, read, or write Notion pages, notes, docs, or database rows.
bulk-update
Update properties or content across many pages in a Notion database with dry-run and error recovery
organize-database
Transform unstructured Notion pages into a well-designed database with proper schema and migration
designer-ic-assessment
Facilitates a structured behavioral assessment interview for IC designer levels, incorporating AI fluency across competency areas. Use this skill when someone wants to run a designer self-assessment, a manager assessment of a designer, or set up an IC level calibration session. Trigger whenever someone mentions designer levels, IC rubric, design assessment, career calibration, manager assessment, or designer growth conversations. Also trigger if someone says they want to evaluate a designer's AI fluency, run a competency interview, or prepare for a calibration meeting.
notion
Notion workspace — read/write pages, databases, search, create tasks via Notion API
tasks
Task & project management — GitHub Projects (native), Linear (API), Notion DB (API)
plugin-notion
Read and edit the user's Notion pages and databases.
notion-research-documentation
Searches across your Notion workspace, synthesizes findings from multiple pages, and creates comprehensive research documentation saved as new Notion pages. Turns scattered information into structured reports with proper citations and actionable insights.
notion
Manage Notion workspace: create pages, query databases, add content blocks. Requires NOTION_API_KEY.
parse-calendar
Parse a monthly content calendar from DOCX, XLSX, Notion, or pasted text into structured calendar-data.json — the source of truth every downstream skill reads. Triggers on "/parse-calendar", "parse the calendar", "import this calendar", "here is the month", "load the content plan", "calendar to JSON", or whenever a client calendar arrives in any format. No calendar yet? /socialforge:ideate-month drafts one in this exact shape.
okhp3-notion-capture-router
Use this skill whenever an agent needs to export, capture, ingest, summarize, route, deduplicate, or reconcile a conversation or content artifact into Notion. It guides connector-enabled agents through choosing a Notion page versus database destination, resolving a workspace-specific URL or ID, inspecting page content or data-source schema before writing, mapping thread metadata and reusable extracts, creating or updating records safely, and verifying the result. Trigger for ChatGPT, Claude, Perplexity, Copilot, Gemini, PDF, Markdown, transcript, knowledge-base, Notion API, Notion connector, page, database, data source, or thread-export requests, even when the user does not name this skill.
job-application-tracker
Automatically syncs Gmail and Google Calendar with a Notion database to keep track of the status of job applications the user has submitted. Use this skill whenever the user asks to "sync my job applications," "update my job tracker," "check where my interviews stand," or something similar — even if they don't explicitly mention Notion, Gmail, or Calendar, and even if they don't have a Notion database set up for this yet. Requires (or guides the user through setting up) the Notion, Gmail, and Google Calendar MCP connectors.
right-composio
Use BEFORE calling any mcp__right__composio__* tool — especially COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, or COMPOSIO_REMOTE_WORKBENCH — and whenever a request involves Notion, Gmail, Google Calendar, Google Drive, Slack, GitHub, Linear, or any other service routed through Composio. Sessions that skip this skill burn 300-500K context tokens on repeated tool searches and inline payloads ($200+ per session observed in cache-write cost). Read once per session, on resume, and any turn that mentions a Composio-fronted service.
cf-style-guide
Import a brand voice profile from an existing style guide — a .docx/.pdf document, a URL, or manual input — extracting tone, formality, personality, approved/banned terminology, compliance guardrails, and author profiles into a structured brand-profile JSON at ~/.claude-marketing/{brand-slug}/Brand-Guidelines/, then configure the tracking backend (Google Sheets + Drive, Airtable, or local). Triggers on "/contentforge:cf-style-guide", "import our style guide", "set up a brand from this document", "update the brand profile with new guidelines", "extract our banned terms and disclaimers". Deterministic parsing, no agent. The saved profile is read by every pipeline phase — drafting, brand compliance, humanizer; pairs with /contentforge:brand-setup and /contentforge:cf-switch-backend.
analyze-paper
Analyze a single research paper deeply and create or update evidence-grounded professional notes in Markdown, Notion, or Feishu/Lark. Use when the user asks to read, analyze, explain, summarize, interpret, or take notes on a paper, or supplies an arXiv link, PDF, DOI, title, project page, code repository, existing note, Notion page, or Lark document. Classify the paper type, prioritize primary sources, draft one shared manuscript, render one or more verified targets, and preserve Markdown as the default fallback.
gt-data-audit
Expert B2B contact data audit framework for RevOps, GTM Engineering, and Sales Operations. Use when running a data quality audit on a CRM (HubSpot, Salesforce, Pipedrive, Close, Attio), scoring a contact data layer across 10 dimensions (coverage, accuracy, freshness, cost, governance, and more), answering benchmark questions on email accuracy, bounce rates, mobile connect rates, or data decay, or validating provider claims (Apollo, ZoomInfo, Cognism, Clay, BetterContact). Triggers on: audit our data, data quality check, is our data the bottleneck, email accuracy benchmark, verified email rate, cost per usable contact, mobile connect rate, data decay, CRM hygiene, ZoomInfo vs Cognism, waterfall vs single source, RevOps audit, data layer for AI agents. Run before a GTM Alpha Playbook or Clay build. Do NOT use for list building (use gt-list-building), Clay workflow setup (use gt-clay), HubSpot admin without data quality scope (use gt-hubspot-admin), or cold email copywriting (use gt-cold-email).
design
Run a Design Execution session for a milestone. Loads full project context deterministically (via design-load.mjs), investigates the open questions in each Ready / In-Progress 📐 Design and 📋 Planning task, proposes a thematic execution order for human sign-off, then walks each task one open-question at a time — debating trade-offs, locking decisions, updating architecture pages, and filing follow-on 🔲 Backlog Code tasks. Use when the user says "design", "design session", "let's run a design session for milestone X", "execute the design tasks", or starts a Design Execution session. Requires a grooming manifest in the central config tree (config/projects/<dir>/grooming.json), shared with the /groom skill.
docs
Run an interactive Docs authoring session for a single 📝 Docs task: load the task, read its declared Source domain(s) live over the web, author into its declared Target surface (a repo file or a Notion page), and open the never-auto-merge output (a draft PR for a repo-file target, or a staged notion.pageEdit intent for a Notion-page target) for a human to review and merge/apply. Use when the user says "docs", "docs session", "run the docs task", "write the docs for X", or starts an interactive Docs-authoring session on a 📝 Docs task. Requires the task to declare a Target surface and Source domain(s) in its body (see § Docs task-body convention below) — do not improvise either.
notion-database-architect
Designs Notion workspaces with linked databases, rollups, formula fields, views and templates. Use when building a Notion system or fixing a workspace that has outgrown its structure.
notion-database-architect
Designs Notion workspaces with linked databases, rollups, formula fields, views and templates. Use when building a Notion system or fixing a workspace that has outgrown its structure.
voc-source-notes
Pull customer signal from AI meeting notes (Granola, Fathom, Otter, Fireflies notes, Notion meeting docs). Covers the conversations your call recorder missed — in-person meetings, conferences, calls on a personal phone. Trigger on /voc-source-notes, "pull my meeting notes", "what came up in meetings this week".
voc-source-notes
Pull customer signal from AI meeting notes (Granola, Fathom, Otter, Fireflies notes, Notion meeting docs). Covers the conversations your call recorder missed — in-person meetings, conferences, calls on a personal phone. Trigger on /voc-source-notes, "pull my meeting notes", "what came up in meetings this week".
service-outline
Generate a new Service Outline or update an existing one from John's modular 10-part service template, adapted to the service type (consulting, AI engineering, software development, web design, AI-driven PPC, branding). Interviews for context first; accepts an uploaded file, file path, or Notion/web URL as an update source. Use when the user asks to write, draft, update, or scaffold a service outline, service document, service brief, or service definition.
brief-intake
Turn raw mess — a Slack thread, meeting transcript, Jira ticket, half-written Notion page, email chain, or paragraph of free-form context — into a structured brief that the downstream skill (adr-generator, design-doc, runbook-generator, exec-summary, deck-builder, tech-comparison-matrix) can consume without further intake. Use whenever the user has unstructured source material and is about to invoke another skilldrop skill, or when a draft is missing the load-bearing context the next step will need.
free-tier-scraper-apis
Use when building zero-cost scraping or data-enrichment pipelines on free API tiers. Covers Gemini free-tier model IDs and rate limits, the generativelanguage REST endpoint and payload, Notion API property JSON shapes, model fallback, and scraping-method choice.
bulk-update
Update properties or content across many pages in a Notion database with dry-run and error recovery
organize-database
Transform unstructured Notion pages into a well-designed database with proper schema and migration
quarterly-rocks-tracker
Tracks your agency's 90-day priorities (EOS "Rocks") so they survive contact with the actual quarter — weekly nudges on progress, an honest on-track/off-track read before every L10 meeting, and a plain done/not-done verdict at quarter close. Use when you keep setting quarterly goals that quietly die by week 6, when you want your agent to prep the Rocks section of your L10 before you walk in, or when you're running EOS/Traction and want the Rocks review to stop being a guessing game.
notion
Work with Notion through the right API — the MCP integration by default, and the internal v3 API (token_v2 cookie, /api/v3/) for the operations MCP provably cannot do: select-option recolor/removal, date formats, reminders, conditional row colours, grouped views, bulk row writes, and anything destructive. TRIGGER when: reading or writing Notion pages, databases, rows, schemas or views; an mcp__plugin_Notion_notion__* call failed, was rejected, or silently did nothing; or the user asks to change how a Notion table looks. DO NOT TRIGGER for Notion-adjacent work that never calls an API (writing prose destined for Notion), or when a task-specific skill already owns the database (flightradar24, update-conventions) — start there and come here only for the underlying technique.
trading-ledger
A trading journal that records the decision, not just the trade — the user reports a trade in plain language (e.g. "bought 500 NVDA at 135", "closed my TSLA position"), you parse it and write it to their Notion database, capturing the entry thesis, the plan, and the emotion; closing a trade updates the matching open row; review compares thesis vs outcome vs execution. Use when the user reports a trade, says log a trade / trading ledger, or asks to review my trades.
competitive-lifecycle-calendar
Build a ranked year-of-moments lifecycle calendar in Notion with competitive evidence pulled from the Email Love MCP. Every cultural moment and commerce peak that matters for a brand, stack ranked Core / Optional / Stretch, and every Core moment backed by what competitor brands actually sent last year, including dates, offers, discount depths, and linked real emails. Use whenever someone asks to build a campaign calendar, marketing calendar, moments calendar, or lifecycle planning calendar backed by competitor data, or says things like "build me a calendar for [brand] with competitive evidence" or "what should [brand] plan around, and what do competitors do". Requires the Notion connector and the Email Love Inspiration MCP.
todo
Manage the user's PERSISTENT cross-session TODO list (data/TODO.md, bidirectionally synced with the Notion page "TODO"). Use when the user triggers /todo, asks to add/list/complete/remove items from their personal list ("adiciona na minha lista", "anota pra depois", "o que tá pendente?", "marca X como feito"), or mentions a future idea worth saving ("uma hora preciso fazer X" → offer to add it). NOT for tracking steps of the current session's task — only for items that must survive the conversation.
keel-ops
Operations & connectors lane router. Routes memory, workspace connectors, and meta/skills-management to the right tool — claude-mem, granola, slack, notion, zapier MCPs, plus find-skills and the claude-skills library. Defers to keel-v2. Use for persistent memory, pulling meeting notes, reading/writing Slack or Notion, wide app automation, or discovering/installing new skills.
workspace-bridge
Notion + Google Workspace bridge for My PM Tools. Provides 16 MCP tools for reading/writing Notion pages and databases, searching Google Drive, reading/writing Sheets, listing/creating Calendar events, and searching Gmail. Extends the core project management workflow with external knowledge and document integration.
conversation-digest
Digest any long conversation, chat thread, support ticket, incident log, company announcement, or meeting notes into a structured summary — core problem, timeline, solution/recommendation, and action items, PLUS a personalized "what YOU need to do" section for the current user. Content can be pasted directly OR pulled automatically from a connected source (Slack thread, Notion page, Linear/Jira issue, Google Drive doc) via MCP. When the source is Slack, the skill auto-detects who the current user is from their Slack profile and highlights the items addressed to them. Use when someone needs to quickly understand "what is the actual problem here and what do I need to do" from a wall of text. Output language auto-matches the input (Vietnamese in → Vietnamese out; English in → English out).
generating-content-briefs
Use when turning a topic into a research-grounded content brief AND wiring it toward a shipped PR — the "brief to merged PR" flow. Auto-triggers on "/seo brief", "write a brief for X", "brief to PR", "give me a content brief and a draft", "turn this topic into a post". Takes a topic (+ optional target keyword/URL), pulls your GSC striking-distance data + the live SERP, then runs the deterministic assembler (scripts/brief-assembly.js) to produce CONTENT_BRIEF.md (target keyword + intent, the striking-distance angle, a headline moat, entities/PAA questions, internal-link suggestions from your own content, a word-count target) plus a draft content file, and opens the draft-to-PR. Composes with finding-underserved-keywords (the striking-distance data) and analyzing-content-gaps (the SERP diff); hand the drafted sections to optimizing-on-page and FAQ blocks to adding-schema-markup.
basalt
Use when the user wants to publish, share, document, or hand off written work — a doc, report, notes, spec, runbook, guide, or deliverable — so a colleague, client, or teammate can read or review it by link. Triggers on "publish this", "document this", "write this up", "share this doc", "put this somewhere reviewable", "make this a page", "send this to my colleague/client", "I need a shareable link for this", "publica esto", "documéntalo", "escribe y publica…", "comparte este doc", "súbelo a un lugar compartible", "pásaselo a mi colega para que lo revise". Also use when a WORKFLOW reaches a publishable artifact with nobody asking — closing a cycle, shipping a report, ending a run — and something has to end at a live URL. Basalt turns markdown into branded, permissioned, versioned pages served by URL — the durable, governed home for AI-authored work. Prefer it over gist / pastebin / Notion / a local file whenever the user wants work to live somewhere a human will actually open and review.
notion-cli
Interact with Notion via the `ntn` CLI — create, read, update, and trash pages; upload files; manage blocks via the public API. Use when the user wants to publish content to Notion, post a blog post or document to a Notion database, upload images to Notion, manage Notion pages from the command line, or asks about ntn / Notion CLI / NOTION_API_TOKEN / Notion integrations.
extract-doc
NOTE: this skill requires connected ~~docs MCPs (Notion, Google Docs, Confluence, Box, Egnyte), which are typically only present in Cowork — the Code variant exists for parity but most users will want the Cowork variant. Pull insights from a single doc or page (Notion, Google Doc, Confluence, etc.) into the standard intake backlog. Use when user says '/extract-doc', 'extract insights from this doc', 'pull learnings from this page', 'mine this Notion page for knowledge', 'extract from this Confluence'. Differs from /intake doc (which captures one structured doc artifact with reaction) — extract-doc decomposes a doc into multiple intake-backlog entries for audit routing. (Code port — ADR-094.)
intake
Capture knowledge from outside the conversation. A single URL or text snippet is clipped whole to intake/clippings/; files/directories/globs are bulk-scanned into the backlogs; `extract <source>` decomposes a source into backlog entries; `doc <source>` captures a structured 5-section reflection (claims/worth-keeping/contested/action/reaction); `thread <id>` pulls a chat/email thread via MCP. Use when user says '/intake', 'intake from', 'import knowledge from', 'scan this file for knowledge', 'onboard this project', 'clip this', 'save this link', 'save this snippet', 'capture this URL', 'clip this thread', 'save this Slack thread', 'capture this email chain', 'extract insights from this doc', 'mine this Notion page', 'capture a doc', 'log notes on this doc'. Unlike /extract (current conversation), /intake captures external sources; clipped/bulk items are reviewed at the next /audit-knowledge run. (Code port — ADR-094.)
sync-decisions
NOTE: this skill requires connected ~~docs MCPs with WRITE access (Notion, Confluence, Google Docs), which are typically only present in Cowork — the Code variant exists for parity but most users will want the Cowork variant. Mirror approved decisions from the knowledge folder out to a connected ~~docs MCP (Notion, Confluence, Google Docs). Use when user says '/sync-decisions', 'mirror decisions to Notion', 'push decisions to wiki', 'sync ADRs to Confluence', 'export decisions externally'. WRITE-side skill — embeds Rule 22 advisory preamble per ADR-016 and requires explicit per-write go-gate. Logs each sync to logs/sync-decisions.md. (Code port — ADR-094.)
uploading-to-notion
Uploads Claude session summaries or markdown reports to Notion. Use for "노션 업로드", "결과 저장", "notion 정리", "세션 요약", "리포트 업로드", "보고서 작성" requests.
fd-direction
12가지 미적 방향(Aesthetic Direction) 템플릿을 기반으로 프로젝트의 디자인 방향을 결정합니다. 컨텍스트와 인스피레이션을 바탕으로 최적의 스타일을 선택하고 조합합니다.
mmk-notion
This skill should be used when the user asks to manage Notion pages, workspaces, teams, people, databases, meetings, comments, users, publishing, subscriptions, emojis, views, or any Notion-related operation using the mmk CLI. Triggers on phrases like "invite to Notion", "publish page", "revoke access", "list teams", "database schema", "AI summary", "meeting notes", "workspace members", "duplicate page", "page config", "publish settings", "list published", "guest pages", "subscription", "add comment", "reply to comment", "list users", "get user", "get page", "update page", "archive page", "lock page", "page markdown", "create page from markdown", "append markdown", "replace markdown", "update markdown", "custom emoji", "database view", "list views".
mmk-notion-comment
Manage Notion page comments — add, list, reply to discussion threads. Triggers on "add comment", "list comments", "reply to comment", "page comment", "discussion reply", "comment on page".
mmk-notion-database
Manage Notion databases — show property schema, query with filters/sorts, trigger AI summary generation, insert/update/upsert/delete records. Triggers on "database schema", "AI summary", "database properties", "detect AI", "ai-summary", "ai-summary-auto", "auto AI summary", "database structure", "query database", "filter", "sort", "database query", "insert records", "update records", "upsert", "delete pages", "bulk insert", "bulk update", "bulk delete", "check duplicates", "find duplicates", "dedupe records".
mmk-notion-database-ai-summary
Bulk AI summary generation across all pages in a Notion database. Triggers on "generate AI summaries for database", "bulk AI summary", "batch AI summary", "run AI summary across database".
mmk-notion-meeting-comment
Post a structured summary comment on a Notion meeting page — extracts action items and decisions from transcript. Triggers on "summarize meeting as comment", "post meeting summary", "comment meeting notes", "meeting action items comment".
mmk-notion-onboard
This skill should be used when the user asks to "invite someone to Notion with email fallback", "invite and send signup email if not a Notion user", "onboard a user to a Notion page", or wants a workflow that tries Notion invite first and falls back to sending a Gmail signup invitation if the user doesn't have a Notion account.
mmk-notion-page
Manage Notion pages — invite, revoke, publish, unpublish, config, publish-settings, duplicate, list-published, markdown (get/create/append/replace/update), transcript, get, update. Triggers on "invite to page", "revoke access", "publish page", "unpublish", "page config", "full width", "publish settings", "duplicate page", "list published", "page markdown", "create page from markdown", "append markdown", "replace markdown", "update markdown", "page transcript", "meeting transcript", "get page", "page by id", "update page", "archive page", "lock page", "erase page".
mmk-paymint-notion-invoice
Batch send Paymint invoices from a Notion database with Notion write-back. Triggers on "batch invoice from notion", "send invoices from database", "notion invoice", "paymint notion", "bulk invoice send".
mmk-paymint-notion-schema
Recommended Notion database schema for Paymint invoice tracking. Triggers on "paymint notion schema", "paymint database setup", "invoice database design", "paymint notion template", "paymint db schema".
mmk-youtube-channel-summary
Fetch recent YouTube channel videos via RSS, filter out Shorts, get metadata and transcripts, AI-summarize, and upsert into a Notion database. Supports multiple channels. Triggers on "youtube channel summary", "channel summary to notion", "youtube rss to notion", "summarize youtube channel", "youtube channel notion sync".
mmk-notion-view
Manage Notion database views — list, get, create, update, delete. Triggers on "database view", "notion view", "list views", "create view", "update view", "delete view", "get view".
mmk-paymint-send
Send payment invoice via Paymint. Triggers on "send invoice", "create invoice", "bill someone", "payment request".
Integration detected automatically from skill content. Some results may be false positives.