Menu
Read Notion pages and databases using MCP tools. Use when looking up Notion content, reading pages, or querying databases.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Safely add a directory to Claude Code's Bash tool PATH. Use when a binary runs in your terminal but is "command not found" inside Claude Code's Bash tool, when adding a directory to PATH for Claude Code, when configuring CLAUDE_ENV_FILE, or when settings.json env.PATH did not work. Explains why env.PATH replaces rather than appends PATH and is not variable-expanded, why ~/.zshrc PATH exports are dropped, and the supported SessionStart hook fix.
Create or improve a Claude Code skill/slash command with best practices for structure, dynamic context, and safety. Use for creating new skills, improving existing ones, or learning skill authoring.
Launch a dynamic Workflow where the top-tier session model (Fable, or Opus when Fable is unavailable) handles planning and orchestration while implementation subagents run on Sonnet for routine tasks and Opus for complex ones. Use when the user wants to orchestrate a build, a dynamic workflow, a model-tiered build, fable or opus planning with sonnet and opus implementation, or tiered agents.
Open a PR, wait for CI to pass, fix failures, address review comments, and loop until fully green. Use when opening a PR, fixing CI, or addressing review feedback.
Manage recurring tasks in the local Argus daemon via its HTTP API. Use when the user wants to schedule a task locally in argus, create a cron-driven task, fire X every weekday/hour/morning, set up a recurring agent that needs local filesystem access (logs in ~/.argus, local databases, dotfiles), list or update existing argus schedules, or run an argus schedule now. Distinct from /schedule, which creates remote cloud routines without local access.
Generate a handoff prompt to pass context to another agent thread. Use when switching repos, handing off work, or sharing context between agents.
| name | notion |
| description | Read Notion pages and databases using MCP tools. Use when looking up Notion content, reading pages, or querying databases. |
Read Notion pages and databases via MCP tools. This skill covers reading operations only.
| Tool | Use For |
|---|---|
mcp__notion__notion-fetch | Read page content as Notion-flavored markdown |
ReadMcpResourceTool with notion://docs/enhanced-markdown-spec | Get the full markdown spec (useful for understanding page structure) |
If mcp__notion__notion-fetch is not available (e.g., in environments using Keystone), use these tools instead:
| Tool | Use For |
|---|---|
mcp__plugin_thanx_keystone__notion_get_page | Read page metadata (title, properties, dates) |
mcp__plugin_thanx_keystone__notion_get_page_content | Read page blocks (raw Notion API JSON) |
mcp__plugin_thanx_keystone__notion_search | Search for pages by title |
mcp__plugin_thanx_keystone__notion_query_database | Query a database with filters |
mcp__plugin_thanx_keystone__notion_get_database | Get database schema and metadata |
The blocks API returns raw JSON. To extract readable text, parse each block's rich_text[].plain_text fields. Use ToolSearch to discover and load these tools before calling them.
You are helping read Notion data. Use the MCP tools above for all operations.
mcp__notion__notion-fetch with the page URL or ID
The tool returns Notion-flavored markdown. Key things to know about the format:
```ruby){toggle="true"} attribute<table> syntax[d.date](http://d.date))Use mcp__notion__notion-fetch with the page URL.
Use mcp__notion__notion-fetch on the database URL to see its schema and entries.
If a page has mangled content in the markdown output:
#, ##)<table or --- dividersThese indicate sections that were absorbed into code blocks during a bad edit.
Notion pages can return very large responses (100K+ characters) that exceed token limits. When this happens:
python3 -c or jq to extract block text rather than reading raw JSON directlyjq -r '.. | .rich_text? // empty | .[].plain_text' < temp_file.json