notion-knowledge
Search connected Notion pages and databases, verify the relevant sources, and produce concise answers that preserve links and uncertainty.
git clone --depth 1 https://github.com/Devin-AXIS/iPolloWork /tmp/notion-knowledge && cp -r /tmp/notion-knowledge/examples/plugin-packages/notion/skills/notion-knowledge ~/.claude/skills/notion-knowledgeSKILL.md
# Notion Knowledge Use this skill for questions that require finding or comparing existing Notion knowledge. 1. Confirm the workspace, team, project, or page scope from the request. 2. Search before retrieving full pages. Keep broad searches bounded and refine ambiguous results. 3. Open the smallest set of relevant pages or database records and distinguish current evidence from stale or conflicting notes. 4. Answer with page titles and links when the MCP provides them. State when a claim is an inference. 5. Do not edit Notion during a research-only request. Never invent a page, property, owner, or status that was not returned by the connected Notion MCP.
Search and summarize material from the Acme research service.
Agent-first screenshots — an agent drives the real app via CDP and produces clean, defect-free product screenshots (newsletters, landing pages, social, decks, PR). Dual-channel verification (DOM + pixels + vision) in a capture loop. Use for any "take/redo screenshots of the app" task.
Resolve the correct library and retrieve a small, relevant set of version-aware official documentation before answering a technical question.
Use the current project dependency versions and Context7 documentation to implement or upgrade code without importing APIs from a different release line.
Create an OpenCode plugin for iPolloWork. Scaffolds the plugin file with the correct API shape, tool definitions, and hook registration. Use when the user asks to 'create a plugin', 'write a plugin', or 'make a plugin that does X'.
Launch and control standalone Chrome in a Daytona sandbox via CDP. Use for web sign-in, OAuth, Den Web setup, browser-only flows, or when the app should not be driven through Electron CDP.
Daytona cloud server, Den sandbox, desktop plus cloud e2e, marketplace server, worker proxy, cloud auth, org policies, connect Electron to Den. Use for server-side setup in validated flows.
Daytona development environment overview. Use when the user asks about Daytona setup, Daytona toolbox, dev environment, noVNC, CDP, server sandbox, secrets volume, Electron sandbox, standalone Chrome, validation, or artifacts volume.