okhp3-notion-agent-boundary

原文涵盖的主题

• okhp3-notion-agent-boundary
• Scope
• The four venues
• Decision procedure
• Common misconfigurations to flag
• Output contract
• Tooling
• About

OverKill Hill P³ · overkillhill.com · github.com/OKHP3 Answers the question that started this family: where should this workflow actually live? This skill decides only - it never builds, runs, or converts anything itself. Always load okhp3-notion-core first for the live capability map. | In scope | Out of scope | |---|---| | Venue selection with an explicit tradeoff rationale | Building or driving a Custom Agent session (a future custom-agent-ops skill). Converting a file-based skill to a Notion Skill page or back (a future skill-bridge skill) | | Venue | What it is | Where it lives | Who can use it | Drivable from outside Notion? | |---|---|---|---|---| | Notion Agent | On-demand assistant inside the Notion app, bottom-right corner | Notion UI | Requires Notion AI access | No | | Custom Agents | Autonomous workflows: instructions, triggers, scoped access, model choice, agent-to-agent handoff | Notion, Agents sidebar | Business or Enterprise plan only. Consumes Notion credits | Yes, via MCP session-driver tools | | Notion Skills | A user-owned page marked isskill, containing workflow instructions | A Notion page | Per the workspace's live capability map | Yes, via search-skills / c

这里只展示节选，请以完整原文和当前要求为准。