notion-meeting-notes
Convert meeting material into decisions, action items, owners, dates, and open questions, then save it to an explicitly selected Notion destination.
git clone --depth 1 https://github.com/Devin-AXIS/iPolloWork /tmp/notion-meeting-notes && cp -r /tmp/notion-meeting-notes/examples/plugin-packages/notion/skills/notion-meeting-notes ~/.claude/skills/notion-meeting-notesSKILL.md
# Notion Meeting Notes 1. Separate discussion, decisions, action items, risks, and unanswered questions. 2. Do not infer an owner or deadline. Mark missing values as unassigned or unspecified. 3. Resolve the exact destination page or database before writing. 4. Show a concise preview when the write will create a new page or materially replace existing notes. 5. Verify the saved page and return the resulting link. Keep confidential details within the user-selected Notion scope and avoid copying unrelated workspace content into the notes.
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.