
notion-skills
Comprehensive collection of Claude skills for Notion integration: capture knowledge from conversations, prepare for meetings, conduct research, and convert specifications into implementation plans
- version
- 1.0.0
- GitHub stars
- 69
Install
/plugin install notion-skills@notion-skills-marketplaceRun it inside Claude Code after adding the marketplace with /plugin marketplace add tommy-ca/notion-skills.
Contents
Discovered from sourceSkills 4
Overview
The Knowledge Capture skill transforms conversations, discussions, and unstructured information into organized, structured documentation in Notion. It helps you preserve institutional knowledge by capturing important conversations and converting them into actionable, well-formatted documentation.
When to Use
Use this skill when you need to:
- Convert transcripts or conversation notes into structured documentation
- Create meeting summaries with action items
- Build knowledge base articles from discussions
- Archive important conversations for future reference
- Extract key insights and decisions from discussions
Features
- Smart Content Extraction: Automatically identifies key points, decisions, and action items from conversations
- Structured Organization: Creates well-organized Notion documents with proper hierarchy
- Metadata Capture: Preserves participants, dates, and context information
- Action Item Tracking: Extracts and formats action items with ownership and deadlines
- Cross-linking: Automatically creates links to related documentation and team members
Requirements
- Notion API Access: Integration token with appropriate permissions
- Target Workspace: Notion workspace where documentation will be stored
- Template (Optional): Pre-defined Notion template for consistent structure
Implementation Details
This skill uses the Notion API to:
- Parse input content (text, transcripts, or discussion notes)
- Extract key information using structural analysis
- Format content according to Notion document standards
- Create or update Notion pages with captured knowledge
- Maintain cross-references and relationships
Typical Workflow
Input: Conversation/Discussion
↓
Parse & Extract
↓
Identify: Key Points, Decisions, Action Items
↓
Format for Notion
↓
Create/Update Notion Document
↓
Output: Structured Documentation
Example Use Cases
-
Team Meeting Notes
- Input: Meeting transcript
- Output: Organized meeting summary with decisions and next steps
-
Customer Call Documentation
- Input: Call notes and transcript
- Output: Customer interaction record with key requirements
-
Architecture Discussion
- Input: Design discussion notes
- Output: Architectural decision record with alternatives and rationale
-
Interview Notes
- Input: Interview transcript
- Output: Structured candidate or user research documentation
Configuration
Set up these environment variables or Notion settings:
NOTION_API_TOKEN=your_token_here
NOTION_DATABASE_ID=your_database_id
See Also
- Research Documentation - For research-focused documentation
- Meeting Intelligence - For meeting preparation and follow-up
- Notion API Documentation
Overview
The Meeting Intelligence skill prepares you for productive meetings by automatically gathering relevant context, analyzing past interactions, and creating comprehensive meeting agendas. It helps ensure you enter meetings informed and prepared.
When to Use
Use this skill when you need to:
- Prepare for important meetings
- Gather context about attendees and topics
- Create comprehensive meeting agendas
- Review past interactions with participants
- Identify potential discussion points and blockers
- Prepare background materials for meetings
Features
- Context Gathering: Automatically collects relevant documentation and past interactions
- Attendee Analysis: Gathers information about meeting participants
- Agenda Creation: Generates structured meeting agendas with timing
- Background Materials: Compiles reference materials and context documents
- Risk/Blocker Identification: Surfaces potential issues to address
- Decision Tracking: Monitors previously made decisions relevant to the meeting
Requirements
- Notion API Access: For retrieving documentation and meeting history
- Calendar Integration (Optional): To pull meeting details
- Context Database: Notion database with relevant background information
- Team Database: Directory of team members and their expertise areas
Implementation Details
This skill leverages Notion as a knowledge base to:
- Search relevant documentation and past meetings
- Analyze attendee profiles and expertise areas
- Identify agenda items based on historical context
- Create structured agenda pages in Notion
- Compile background materials and references
- Track follow-up items from previous meetings
Meeting Preparation Workflow
Meeting Request
↓
Extract Meeting Details
↓
Search Relevant Context
↓
Analyze Attendees
↓
Identify Agenda Items
↓
Compile Background Materials
↓
Create Comprehensive Agenda
↓
Output: Prepared Meeting Document
Example Use Cases
-
Executive Status Meeting
- Gathers recent project updates, metrics, and blockers
- Creates agenda aligned with executive focus areas
- Prepares data and trend analysis
-
Client Meeting
- Compiles project history, agreements, and past discussions
- Identifies open items and next steps
- Creates agenda addressing client concerns
-
One-on-One
- Gathers feedback, performance notes, and career development info
- Creates agenda with growth and feedback discussion
-
Cross-functional Planning
- Collects input from all stakeholders
- Identifies dependencies and potential conflicts
- Creates comprehensive coordination agenda
Configuration
NOTION_API_TOKEN=your_token_here
MEETING_DATABASE_ID=your_database_id
CONTEXT_DATABASE_ID=your_context_database_id
ATTENDEE_DATABASE_ID=your_attendee_database_id
See Also
- Knowledge Capture - For documenting meeting outcomes
- Research Documentation - For background research
- Spec to Implementation - For meeting-driven implementation planning
- Notion Database Documentation
Overview
The Research Documentation skill automates the process of researching topics and capturing findings in a well-organized Notion database. It streamlines research by structuring information, tracking sources, and connecting related findings.
When to Use
Use this skill when you need to:
- Research complex topics and document findings
- Compile competitive analysis or market research
- Create literature reviews or research summaries
- Build knowledge bases around specific topics
- Track sources and citations
- Organize research across multiple domains
- Create research reports with sourced information
Features
- Structured Research Capture: Automatically organizes research findings with proper hierarchy
- Source Tracking: Maintains complete source attribution and citations
- Topic Organization: Categorizes findings by theme and relevance
- Cross-referencing: Connects related research across topics
- Evidence Collection: Captures quotes, data, and supporting evidence
- Research Timeline: Tracks how understanding evolved during research
Requirements
- Notion API Access: For creating and updating research documentation
- Research Database: Notion database structure for organizing findings
- Web Access: For gathering information from online sources
- Citation Format Preference: Configured citation style (APA, MLA, Chicago, etc.)
Implementation Details
This skill orchestrates research workflows by:
- Breaking down research topics into focused areas
- Gathering information from multiple sources
- Analyzing and synthesizing findings
- Organizing findings with proper attribution
- Creating relationships between related research
- Generating summary documents and reports
Research Documentation Workflow
Research Topic/Question
↓
Break into Research Areas
↓
Gather Information
↓
Analyze & Synthesize
↓
Extract Key Findings
↓
Organize with Sources
↓
Create Notion Documentation
↓
Output: Research Summary
Example Use Cases
-
Competitive Analysis
- Research competitors and market landscape
- Document features, pricing, and positioning
- Create competitive comparison matrix
-
Technology Evaluation
- Research framework/tool options
- Document pros, cons, and use cases
- Create evaluation report with recommendations
-
Domain Knowledge Building
- Research industry best practices
- Document standards and approaches
- Create reference guide for team
-
Literature Review
- Research academic papers on topic
- Summarize findings and arguments
- Create annotated bibliography
-
Market Research
- Gather market size and trends
- Document customer needs
- Create market analysis report
Configuration
NOTION_API_TOKEN=your_token_here
RESEARCH_DATABASE_ID=your_database_id
SOURCES_DATABASE_ID=your_sources_database_id
CITATION_FORMAT=APA
Citation Formats Supported
- APA
- MLA
- Chicago Style
- Harvard
- IEEE
See Also
- Knowledge Capture - For documenting discussions and insights
- Meeting Intelligence - For research-informed meeting prep
- Spec to Implementation - For research-based implementation planning
- Notion API Documentation
Overview
The Spec-to-Implementation skill transforms project specifications into detailed implementation plans with comprehensive task breakdowns, timeline estimates, and dependency tracking in Notion. It bridges the gap between requirements and execution.
When to Use
Use this skill when you need to:
- Convert project specifications into actionable implementation plans
- Break down complex features into implementable tasks
- Create detailed project timelines with estimates
- Identify dependencies and critical path items
- Generate task checklists with ownership and deadlines
- Track implementation progress in Notion
- Create architectural and technical specifications from requirements
Features
- Smart Requirement Parsing: Automatically extracts requirements and acceptance criteria
- Task Decomposition: Breaks specifications into atomic, implementable tasks
- Dependency Mapping: Identifies and visualizes task dependencies
- Effort Estimation: Provides time estimates for tasks and milestones
- Ownership Assignment: Creates task assignments with clarity
- Progress Tracking: Sets up Notion databases for implementation tracking
- Risk Identification: Highlights potential implementation risks and blockers
Requirements
- Notion API Access: For creating implementation plans and task databases
- Specification Format: Clear specification documents (markdown, PDFs, or text)
- Team Database: Directory of team members and skills (optional but recommended)
- Project Template: Pre-configured Notion template for consistency
Implementation Details
This skill transforms specifications through a systematic process:
- Parse specification document and extract requirements
- Break requirements into user stories and tasks
- Identify technical dependencies and blockers
- Create detailed implementation plan with phases
- Estimate effort for each task
- Assign ownership and set deadlines
- Create tracking structure in Notion
- Generate project dashboard and status reports
Spec-to-Implementation Workflow
Specification Document
↓
Extract Requirements
↓
Break into User Stories
↓
Decompose into Tasks
↓
Identify Dependencies
↓
Estimate Effort
↓
Assign Ownership
↓
Create Notion Plan
↓
Output: Implementation Roadmap
Example Use Cases
-
Feature Implementation
- Input: Feature specification with requirements
- Output: Task breakdown with timeline and ownership
- Tracks: Progress dashboard in Notion
-
Product Launch
- Input: Product specification and launch requirements
- Output: Launch plan with phases, dependencies, and critical path
- Tracks: Multi-team coordination and milestones
-
System Migration
- Input: Migration specification and technical requirements
- Output: Detailed migration plan with phases
- Tracks: Data mapping, system cutover, and rollback procedures
-
Infrastructure Project
- Input: Infrastructure design specification
- Output: Implementation plan with testing and deployment phases
- Tracks: Build, test, and deployment checkpoints
-
API Development
- Input: API specification and endpoint requirements
- Output: Development tasks with testing and documentation
- Tracks: Development progress and integration milestones
Task Hierarchy
Epic (Feature)
├── User Story 1
│ ├── Task 1.1 (Backend)
│ ├── Task 1.2 (Frontend)
│ └── Task 1.3 (Testing)
├── User Story 2
│ └── [Tasks...]
└── Acceptance Criteria
Configuration
NOTION_API_TOKEN=your_token_here
PROJECT_DATABASE_ID=your_database_id
TASK_DATABASE_ID=your_task_database_id
TEAM_DATABASE_ID=your_team_database_id
ESTIMATE_UNIT=hours
Estimate Units
Supported time estimate formats:
- Hours
- Story Points
- Days
- Weeks
- Planning Poker values (1, 2, 3, 5, 8, 13, 21)
See Also
- Knowledge Capture - For documenting design decisions
- Meeting Intelligence - For kickoff meeting preparation
- Research Documentation - For technology research
- Notion Database Documentation
- Agile Task Management Best Practices
Sponsors
Details
- Marketplace
- tommy-ca/notion-skills
- Source
- plugins/notion-skills
- Author
- Anthropic & Notion
- Category
- Community
- License
- MIT
- Keywords
- notion, productivity, knowledge-management, meeting-prep, research-documentation, implementation-planning