Menu
Execute a Meseeks task from Organizer or a task file. Use when Igor asks to seek, seek in Codex, do a task, pursue a task, or resolve a Meseeks task with Codex.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Import tasks from TickTick into the Meseeks task system, sync link groups from TickTick Inbox, or create TickTick tasks from local link files. Use when the user asks to fetch TickTick tasks, import from TickTick, sync TickTick, pull tasks from TickTick, discover their inbox ID, or push curated local links back into TickTick.
Create simple Meseeks task or reference folders in the right public/private root. Use when the user asks to create a task, backlog item, inbox capture, reference note, imported task, or source-backed task file.
Scrape tweets and web content, saving results as structured markdown files. Use when the user asks to scrape a tweet, scrape a URL, fetch tweet content, save a link, archive a post, or process a list of links to scrape.
Turn a completed side-chat discussion into one paste-ready prompt for the main chat. Use when Igor asks for a prompt, handoff, copy-paste instruction, or main-thread message after using a side conversation to debate, inspect, or decide implementation details.
Unclutter the Meseeks task system by directly organizing messy task folders, references, imports, tags, status tags, duplicates, stale active work, and public/private placement. Use when the user asks to unclutter, clean up tasks, organize everything, or fix task-system clutter.
Read a full Meseeks task conversation from Convex MCP, especially when the user says Learn from task, asks to read a /task/ URL, references a PROD task, or wants project instructions improved from a prior task failure. Use this to recover the original user intent, assistant visible say() output, internal action/debug timeline, and steering corrections, then update MasterPlan, skills, or task files so the mistake does not repeat.
| name | seek |
| description | Execute a Meseeks task from Organizer or a task file. Use when Igor asks to seek, seek in Codex, do a task, pursue a task, or resolve a Meseeks task with Codex. |
Act on the task. Do not stop at planning unless a blocker makes execution unsafe or impossible.
files/README.md. If execution changes task tags or task placement, also read files/TAGS.md._index.*, child tasks, linked references, sibling duplicates, repo files named by the task, and relevant source metadata.If the task is clear enough to execute, act on it immediately. Do not write a plan just because the task has multiple steps.
If the task is not clear enough to execute, invoke the Plan skill first. Plan should question assumptions, ask Igor concrete questions when needed, and keep breaking down the task until the work is clear enough to execute.
Once Plan makes the task clear enough, return to Seek and execute. Seek is the actor.
Use Plan when the task is raw, ambiguous, misplaced, mixed public/private, likely duplicated, missing enough context, or likely to be solved incorrectly by guessing.
Ask Igor before continuing when:
Ask concrete questions, not open-ended planning theater. If one reasonable assumption is safe, state it and proceed.
class:* tag according to files/TAGS.md.If execution reveals the task is already done, verify that fact, then say so and suggest completing or deleting the task according to files/README.md.