notion-databases
Query and update Notion databases with explicit database identity, property-aware inputs, bounded reads, and confirmation before material writes.
git clone --depth 1 https://github.com/Devin-AXIS/iPolloWork /tmp/notion-databases && cp -r /tmp/notion-databases/examples/plugin-packages/notion/skills/notion-databases ~/.claude/skills/notion-databasesSKILL.md
# Notion Databases 1. Resolve the exact database and inspect its current properties before composing filters or writes. 2. Use bounded queries and return only the properties needed for the task. 3. For create or update operations, show the target database, record identity, and changed properties first. 4. Preserve existing properties that the user did not ask to change. 5. Re-read the affected record after a write and report the resulting URL or identifier. Ask for clarification when multiple databases have similar names. Never guess select values, relation targets, people, dates, or status fields.
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.