메뉴
Turn work into a scheduled task that runs unattended — "every morning", "each Friday", "remind me in an hour", "run this weekly" — or adjust an existing schedule. Use whenever the operator wants something recurring, delayed, or re-timed.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Produce or modify Word documents (.docx) as real files — reports, memos, letters, proposals, or any deliverable the operator will open in Word. Use when the requested output is a Word file, or when an existing .docx needs content extracted, edited, or restructured. Not for spreadsheets, decks, or PDFs — those have their own skills.
Read, extract from, combine, split, watermark, fill, or produce PDF files. Use whenever a .pdf is the input or the deliverable — merging reports, pulling text or tables out, rotating scans, filling forms, or generating a polished PDF from content.
Build or edit slide decks (.pptx) as real files — pitch decks, briefings, status readouts — or extract content from existing ones. Use whenever slides or presentations are the input or the deliverable. Not for documents, spreadsheets, or PDFs.
Produce, edit, or clean spreadsheets (.xlsx/.csv/.tsv) as real files — reconciliations, trackers, budgets, data cleanups, format conversions. Use whenever the deliverable is a spreadsheet or an existing one needs work, including messy tabular data that needs restructuring. Not for Word/PDF/deck outputs.
Compose the operator's daily brief — schedule, things waiting on them, ongoing work, and heads-ups — rendered as a polished HTML artifact, optionally on a recurring schedule. Run only when the operator explicitly asks for their brief (or /daily-brief), or when executing a scheduled brief task. An ordinary question about today's calendar is answered directly, not with a brief.
Conversational first-run companion for the Cowork archetype — verify the workspace is ready, import existing Claude Code/Cowork state, prove the setup on a real task, learn the operator's writing voice, and wire the first scheduled task. The mechanical setup (archetype, plugins, dependencies, folders) belongs to the setup wizard; this skill picks up where it leaves off.
| name | schedule |
| description | Turn work into a scheduled task that runs unattended — "every morning", "each Friday", "remind me in an hour", "run this weekly" — or adjust an existing schedule. Use whenever the operator wants something recurring, delayed, or re-timed. |
protoAgent's scheduler runs full agent turns on a cadence — any cron
expression, or a one-shot at an ISO timestamp. The tools: schedule_task,
list_schedules, cancel_schedule.
Rescheduling, rewording, pausing: find it with list_schedules, then cancel
and re-create with the revised prompt/cadence. Confirm which task before
touching anything if more than one could match.
You are compressing this conversation into a prompt that will run cold, with no access to anything said here. The discipline:
daily-inbox-digest,
friday-metrics-rollup.0 8 * * 1-5 = weekday
mornings); an ISO datetime for one-shots ("remind me in an hour" =
now + 1h). If the operator didn't give a clear cadence, propose one and
confirm before creating.Then call schedule_task. Read the created task back to the operator —
name, cadence in plain words, and one-line summary of what it will do —
so a mis-distilled prompt gets caught now, not at 6am.
Scheduled tasks here run on this machine: they can touch local folders, use any cron cadence, and their results land in the activity thread. Big recurring deliverables can also pair with a workflow recipe — mention it when a task outgrows a single prompt.