Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/jclem/notion-tasks --skill tasksコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Reference for designing and implementing Notion Worker workflows with typed triggers, durable steps, replay-safe data flow, and idempotent side effects
Scaffold a Notion Worker workflow by choosing typed triggers, designing durable steps, and generating replay-safe TypeScript
Review Notion Worker workflows for trigger typing, unstable step order, non-serializable results, swallowed failures, secret handling, and duplicate side effects
| name | tasks |
| description | Working with Tasks and Task Templates. |
Use this skill to create, update, and explain tasks in the Tasks database and repeating-task definitions in Task Templates. Treat Task Templates as the source of truth for repetition. Do not manually create a batch of future recurring tasks; the worker creates and maintains them.
Before using this skill: Replace the Tasks and Task Templates links above with links to the Notion data sources the agent should manage.
Create a page in Tasks and set:
Date rules:
Put checklists, instructions, links, and other longer material in the page body.
Create one page in Task Templates. Set these user-managed properties:
Add reusable instructions and checklists to the template page body. Use unchecked to-do items in a template. The body is copied when each new task is created. Editing template body content later affects future tasks only; it does not overwrite content in existing task instances.
Do not create the six-month set of tasks yourself. For Regularly templates, the worker creates and reconciles occurrences through the next six calendar months after the template workflow runs, and the nightly workflow maintains that window.
Use Regularly when dates belong to a fixed calendar cadence, whether or not earlier tasks are complete.
Examples:
The worker materializes the next six months and links every instance to the same template.
Use After completion when the next task should be scheduled relative to the day the current task is completed. The next task is created only after completion.
Examples:
Starts is still required. It supplies the initial task date; later dates are calculated from completion.
Prefer these forms in Schedule:
| Meaning | Schedule value |
|---|---|
| Every day | Daily |
| Monday through Friday | Weekdays |
| Every Monday | Every Monday |
| Monday and Thursday each week | Every week on Monday and Thursday |
| Every two weeks | Every 2 weeks |
| Every month | Monthly |
| The 20th of every month | Every month on the 20th |
| Last Friday of every month | Last Friday of every month |
| Every February 6 | February 6 |
| First Saturday of February | 1st Saturday of February |
| Second Saturday of February | 2nd Saturday of February |
The ordinal yearly form supports first through fifth and last, weekday names, and month names. For example, “every year on the 2nd Saturday of February” should be stored as 2nd Saturday of February.
A raw FREQ=... RRULE is an escape hatch only when the friendly language cannot
represent the request.
Every generated repeating task has its occurrence date in Start.
Example: a monthly task starting September 20 with no deadline uses Starts = September 20, Schedule = Every month on the 20th, and an empty Due Offset Days.
When the user says to make an existing task recurring:
For Starts, use the existing task Start when possible; fall back to an existing Due date for a due-only task. If neither exists and the user did not give a first date, ask for the first occurrence date.
Editing a template synchronizes these properties to every related instance, including completed history:
The worker preserves instance state such as Status and Completed At. Regular reconciliation may reschedule future Start and Due values when the schedule changes.
Template page body content is copy-on-create and is not synchronized into existing tasks.
After creating or editing a template, inspect:
A valid template has an empty Schedule Error and a populated Schedule Description and RRULE after the update workflow runs.
If Schedule Error is not empty:
Common validation failures include:
Do not edit these unless following the existing-task conversion procedure above:
On Tasks:
On Task Templates:
Completing a task means setting Status = Done. The completion workflow records Completed At and, for an enabled After completion template, creates exactly one successor.