/ Directory / Playground / Notion Skills
← All servers ↗ GitHub
● Community tommy-ca 🔑 Needs your key

Notion Skills

by tommy-ca · tommy-ca/notion-skills

Notion workflows on autopilot — four skills activate by task context: capture decisions, prep meetings, document research, turn specs into plans.

tommy-ca/notion-skills is a Claude skills marketplace focused on Notion productivity. Four skills — knowledge-capture, meeting-intelligence, research-documentation, spec-to-implementation — activate automatically based on what you're doing, so you don't have to remember which to invoke. Each writes into Notion databases you share with a Notion integration; setup is a one-time integration token + database share.

▶ Watch demo 📦 Install 💡 Use Cases

Why use it

Key features

Live Demo

What it looks like in practice

notion-skills.replay ▶ ready
0/0

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "notion-skills": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/tommy-ca/notion-skills.git",
        "~/.claude/plugins/notion-skills"
      ],
      "_inferred": false
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "notion-skills": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/tommy-ca/notion-skills.git",
        "~/.claude/plugins/notion-skills"
      ],
      "_inferred": false
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "notion-skills": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/tommy-ca/notion-skills.git",
        "~/.claude/plugins/notion-skills"
      ],
      "_inferred": false
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "notion-skills": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/tommy-ca/notion-skills.git",
        "~/.claude/plugins/notion-skills"
      ],
      "_inferred": false
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "notion-skills",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/tommy-ca/notion-skills.git",
        "~/.claude/plugins/notion-skills"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json
{
  "context_servers": {
    "notion-skills": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/tommy-ca/notion-skills.git",
          "~/.claude/plugins/notion-skills"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add notion-skills -- git clone https://github.com/tommy-ca/notion-skills.git ~/.claude/plugins/notion-skills

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use Notion Skills

Capture a meeting's decisions and action items into Notion

👤 Anyone who runs lots of meetings ⏱ ~10 min beginner

When to use: The meeting just ended and the decisions are still fresh.

Prerequisites
  • Notion integration + shared database — https://www.notion.so/my-integrations → create → share the target DB with it
  • Skill cloned to ~/.claude/plugins/notion-skills — git clone per README
Flow
  1. Paste/describe the meeting
    Capture today's architecture review — we decided to drop DynamoDB for Postgres and move retries to billing.✓ Copied
    → knowledge-capture activates; structured output with Decisions + Action items
  2. Save to Notion
    Save into the 'Decisions' database with proper tags.✓ Copied
    → Page created with properties (date, owner, area)

Outcome: Decisions live in Notion, searchable, linked — not buried in chat scrollback.

Pitfalls
  • Integration doesn't see the DB — Share the database with the integration explicitly from Notion's share dialog
Combine with: memory-bank-mcp

Prep for a meeting with context and a risk list

👤 PMs, TLs, founders ⏱ ~15 min beginner

When to use: Before a meeting where you want to walk in already informed.

Flow
  1. Provide the meeting context
    Meeting: 'Billing migration review' tomorrow 2pm with CTO. Pull related Notion pages and flag risks.✓ Copied
    → meeting-intelligence activates; surfaces related pages
  2. Get agenda + risks
    Produce a 6-item agenda and a top-3 risks list.✓ Copied
    → Agenda items are questions, not topics; risks tied to concrete evidence

Outcome: A pre-brief you can actually use to steer the meeting.

Document a research project with sources

👤 Researchers, analysts, RFC authors ⏱ ~45 min intermediate

When to use: You've been gathering info and want a structured writeup with citations.

Flow
  1. Kick off the research skill
    Research documentation: evaluate Postgres vs DynamoDB for the billing workload. Include citations.✓ Copied
    → research-documentation activates; structured sections; citations inline
  2. Save + link
    Save as a new page in the 'Research' DB; link back to the parent initiative.✓ Copied
    → Page created with relations set

Outcome: Research artifact others can read and trust.

Pitfalls
  • Hallucinated citations — Ask the skill to include URLs you can click; verify a sample before saving
Combine with: paper-fetch-skill · sec-edgar-mcp

Turn a spec into an implementation plan with tasks

👤 Engineers starting a feature ⏱ ~30 min intermediate

When to use: You have a spec doc and need a task breakdown with estimates.

Flow
  1. Feed the spec
    Use spec-to-implementation on this spec; produce tasks + estimates + timeline.✓ Copied
    → Task tree with sizes and dependencies
  2. Mirror into Notion
    Create tasks in the 'Implementation' DB with initiative link and owner.✓ Copied
    → Rows created with parent-child links

Outcome: Ready-to-commit plan with sensible structure.

Combine with: plane-mcp-server · linear

Combinations

Pair with other MCPs for X10 leverage

notion-skills + notion

Underlying Notion MCP handles the API calls; skills shape the output

Let the skill plan the content; let notion MCP execute database writes.✓ Copied
notion-skills + plane-mcp-server

Write implementation plan to Notion AND create Plane work items

After spec-to-implementation, mirror the tasks into Plane for tracking.✓ Copied
notion-skills + memory-bank-mcp

Promote decisions to per-project durable memory

Capture into Notion; copy the decision summary into memory-bank/<project>/decisions.md.✓ Copied

Tools

What this MCP exposes

ToolInputsWhen to callCost
knowledge-capture (SKILL) meeting transcript or notes Right after a meeting 0
meeting-intelligence (SKILL) meeting context + attendees Before a meeting 0
research-documentation (SKILL) topic + constraints Documenting research findings 0
spec-to-implementation (SKILL) spec doc Starting engineering implementation 0

Cost & Limits

What this costs to run

API quota
Bound by Notion API limits
Tokens per call
Moderate — structured output is concise
Monetary
Free
Tip
Share only the databases you actually need with the integration; fewer pages to scan = faster.

Security

Permissions, secrets, blast radius

Credential storage: Notion integration token in env/secret manager. Don't commit it.
Data egress: Writes go to api.notion.com for the databases you share with the integration only.

Troubleshooting

Common errors and fixes

Integration has no access to the database

Open Notion → the database → Share → add your integration.

Verify: In Notion's share dialog, integration is listed
Pages created but properties missing

Database schema must have the properties the skill writes; add or rename to match.

Verify: Compare skill's property list with database columns
Auto-activation fires for unrelated asks

Tighten the SKILL.md description to narrow triggers.

Verify: head ~/.claude/plugins/notion-skills/*/SKILL.md

Alternatives

Notion Skills vs others

AlternativeWhen to use it insteadTradeoff
notion (MCP)You want raw Notion API access, not a set of opinionated workflowsMore flexible, less opinionated
obsidian-mcp-serverYour notes live in ObsidianDifferent tool
claude-content-writer-skillYou care more about voice/style than Notion structureDifferent focus

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills