Tools· Research & Knowledge Management

    notion-skills

    A package of four Claude Skills that turn conversations, research, meetings, and specifications into structured Notion pages with source attribution and task tracking.

    structuringwritingexecutableOpen Source
    Source code
    git clone https://github.com/tommy-ca/notion-skills.git ~/.claude/plugins/notion-skills, then restart Claude Code. Alternatively copy the folder manually into ~/.claude/plugins/. Requirement: a Notion API token from the Notion Developer Portal.

    Description

    Strengths

    Four standalone skills
    Each skill covers its own use case, knowledge capture, meeting preparation, research documentation and spec implementation, instead of a single general-purpose tool.
    Automatic activation
    The skills recognize on their own when they fit the task at hand and start without an explicit call.
    Documented templates per skill
    Each skill ships its own reference material, test scenarios and usage examples.
    Simple installation via the plugin system
    The repository can be cloned directly into the Claude plugin directory, after which the skills load automatically on restart.

    Assessment

    AI features

    • Knowledge Capture Turns conversations and discussions into structured Notion documentation, for example meeting summaries with action items, decision records with rationale, FAQ documents or process documentation.
    • Meeting Intelligence Gathers context from Notion and builds an agenda ahead of a meeting with timing, pre-read materials, discussion talking points and a risk and blocker assessment.
    • Research Documentation Conducts research and documents the findings with source attribution, as a quick brief, comparison matrix, comprehensive report or decision memo.
    • Spec-to-Implementation Breaks specifications down into implementation plans with phases, tasks per component, effort estimates, a dependency map and a structure for progress tracking.

    Suitable for

    • Teams that need to regularly structure meeting notes, research or conversation outcomes in Notion
    • Project work where specifications need to be translated into traceable implementation plans with task tracking
    • Knowledge workers who need a repeatable, documented store for research with source attribution
    • Less suitable for Less suited for purely visual Notion page design, the feature set is not built for that

    Limitations and notes

    • Setup effort Each skill needs its own Notion API token from the Notion Developer Portal, and every database in use must be shared with the integration individually with edit permissions.
    • Claude Code only The skills run as a Claude Code plugin and require installation in the local plugin directory, standalone use outside Claude Code is not supported.
    • Fixed structure rather than free design Each skill follows its own templates and reference material, output is bound to that structure and not meant for free visual page layout.

    Quick start

    1. Clone the repository into the Claude plugin directory: git clone https://github.com/tommy-ca/notion-skills.git ~/.claude/plugins/notion-skills.
    2. Restart Claude Code, after which the four skills load automatically.
    3. Create a new integration in the Notion Developer Portal and copy the API token.
    4. For every database needed, use the Share button to grant the integration edit permissions.
    5. Set the token as an environment variable, export NOTION_API_TOKEN=your_token_here, or store it persistently in the Claude Code settings.

    Tips

    • Address the skills with a natural instruction rather than calling them manually, the matching skill activates on its own.
    • Before first use, check the skill-specific reference, evaluations and examples folders, they hold templates and example scenarios.
    • Keep integration sharing minimal and share only the databases a given skill actually needs.
    • Do not store the Notion API token in code, set it via the NOTION_API_TOKEN environment variable or store it persistently in the Claude Code settings instead.

    Access

    Last reviewed: · Pricing, plans and features are a snapshot in time. Check the provider's own page before deciding.

    In the workshop this becomes your method.

    Whoever sees this process run once wants the agent behind it next. We build that in the workshop From Process to Agent.

    View workshops

    Related resources

    Browse all resources

    Conversation, not pitch

    Understand first, then decide. We take time for an initial conversation, without sales pressure, without obligation.

    Schedule a call