This skill should be used when the user asks to "process my inbox", "organise inbox", "clean up inbox", "zero inbox", or wants to process unprocessed items using the COD Organise phase.
Processes inbox items using COD methodology to organize tasks, notes, and files into actionable or reference systems.
/plugin marketplace add oskar-dragon/claude-code/plugin install vault-manager@claude-codeThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Execute the COD Organise phase for Oskar's inbox. Use todoist-workflow skill for task management.
This is the systematic processing of all unprocessed items (notes, emails, tasks, files) into their proper locations.
Scan common inbox locations for unprocessed items:
find-tasks with projectId: "inbox"Inbox/ folderFor each unprocessed item, determine:
Use the COD decision tree:
Based on the decision for each item:
Inbox/ to appropriate folders (Resources/, People/, etc.)Create Todoist tasks with:
For tasks related to existing projects:
## Tasks section — the project note is the source of truthAfter processing each item:
Goal is ZeroInbox — all items processed and routed.
Show Oskar:
Save any new insights, conventions, or processing patterns to auto memory.
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.