okhp3-notion-search-strategy
Find content across a Notion workspace and its connected apps by keyword. Chooses between workspace search and AI search, applies creator, date, teamspace, title-only, and content-status filters, respects the search-specific rate limit, and routes around plan-gated filters. Use when the user wants to find, locate, or look up a page, database, or piece of content by name or topic without already knowing where it lives. Does not query structured rows from a known database (use okhp3-notion-query) and does not enumerate everything that exists (use a wave-2/3 workspace-inventory 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-search-strategy
- Scope
- Choosing a search backend
- Filters and plan gating
- Rate limit discipline
- Result triage
- Output contract
- Tooling
OverKill Hill P³ · overkillhill.com · github.com/OKHP3 Finds content by keyword or topic when the user does not already know where it lives. Always load okhp3-notion-core first. | In scope | Out of scope | |---|---| | Keyword/semantic search across Notion and connected apps, filter selection, plan-gate routing | Filtering and sorting rows in a known data source (okhp3-notion-query). Enumerating everything that exists regardless of a search term (a governance-tier skill) | Workspace search: faster, Notion-only, supports exact filters and non-relevance sorting (by lastedited or created). AI search: semantic, includes connected apps (Slack, Google Drive, GitHub, Jira, Microsoft Teams, SharePoint, OneDrive, Linear). Requires Notion AI on the workspace. If the caller does not specify a backend, the default auto-selects AI search when available, otherwise workspace search. Only force a specific mode when the task specifically needs one: force workspace search for exact-filter or non-relevance-sort needs (these cannot combine with AI search), or force AI search when the target is explicitly in a connected app. Available on every plan: location scoping (page, data source, or single teamspa
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- OKHP3/skillz
- Source file
- notion/okhp3-notion-search-strategy/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:55.222Z.
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.