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.
Target: Search & knowledge management. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- okhp3-notion-capture-router
- Use this skill when
- Scope
- Operating principles
- Workflow
- 1. Define the capture request
- 2. Resolve and inspect the destination
- Connector operation map
OverKill Hill P³ · overkillhill.com · github.com/OKHP3 Turn conversations and other content artifacts into useful Notion pages or database records. The skill teaches an agent-enabled platform how to use Notion as a destination without assuming a particular user's account, workspace taxonomy, page hierarchy, or database schema. The source may be a live conversation, an exported transcript, a PDF, Markdown, research notes, or another structured artifact. The destination may be: 1. A page export containing the complete source or a clearly labeled summary and extract set. 2. A database export containing one thread/content record, one record per reusable extract, or another schema requested by the user. Use the user's requested destination and schema as the authority. Names such as “Chat Threads” or “Extracts” are examples, not required Notion structures. Use it when the user asks to: export a conversation, transcript, research result, or file into Notion create or update a Notion page, database row, or data-source record design a reusable Notion capture or ingestion workflow turn a thread into a summary, outline, decision record, checklist, or reusable extracts deduplicate or reconcile
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- OKHP3/skillz
- Source file
- .agents/skills/okhp3-notion-capture-router/SKILL.md
- Fixed revision
- 7b187777d42ab7bc7bab1e5f2c940cd3139ecebf
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: OKHP3/skillz · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-10T10:00:53.640Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.