Morning, midday, and evening summaries
Prepare time-specific task summaries for the conversation or a separately authorized push channel, without treating a cached list as current truth.
Task planner Skill
Install the WeeklyPlanner Task Planner Skill
Give a compatible AI workspace a reusable way to capture tasks, review the week, triage an inbox, and propose schedule changes while WeeklyPlanner remains the source of truth.
Distributed as a local Skill directoryDesigned for Skill-capable Codex and Claude environments
Reusable planning workflows
The current V1 Skill routes explicit WeeklyPlanner requests into focused workflows instead of applying one oversized prompt to every situation.
Inbox triage
Review unscheduled tasks, separate unclear items from actionable work, and propose dates or groups before changing the plan.
Weekly review
Use day-review and planning context where available, preserve coverage limits, and distinguish historical commitments from a current snapshot.
Schedule assistance
Preview task moves, ask for explicit confirmation, apply approved patches atomically, and read the affected tasks back after the write.
Direct task management
Create tasks, list today or this week, find overdue work, mark numbered results complete, move tasks, delete tasks, and inspect groups.
Planning patterns
Summarize aggregate planning context and task patterns without exposing raw event rows or inventing a fulfillment rate when coverage is incomplete.
A real plan, not a mock integration
Your assistant works through a scoped connection
Create a revocable key in WeeklyPlanner, connect a compatible agent, and let the workflow read or update the same plan you can inspect in the app.
- Your request
- Task Planner Skill
- Scoped MCP or API
- WeeklyPlanner plan
A workflow layer, not another task database
The Skill, connector, and planner have different jobs. Keeping those layers separate makes the workflow easier to inspect and safer to update.
The Skill supplies the playbook
It defines when to use WeeklyPlanner, which workflow to run, how to interpret task state, and when the agent must preview or confirm a change.
The connector supplies the tools
A registered WeeklyPlanner connector maps logical operations such as list_tasks and update_task to scoped product access. The Skill never bypasses that boundary.
The planner keeps the record
Tasks, groups, dates, time blocks, and review data stay in WeeklyPlanner. The agent reads back affected tasks instead of maintaining a separate invisible list.
Install V1 without inventing a one-click setup
The current Skill is a local directory containing SKILL.md, workflows, and references. There is no universal installer across AI clients, so use the local Skill import method documented by your compatible client and keep the directory intact.
- 1
Add the complete Skill directory
Import or copy task-planner through the client-supported local Skill mechanism. Do not copy only SKILL.md; its workflows and references are part of the operating contract.
- 2
Start a fresh session
Ask the agent to use task-planner for a WeeklyPlanner request. The Skill discovers session capabilities at runtime instead of assuming a connector is available.
- 3
Connect capabilities separately
If the session cannot expose WeeklyPlanner operations, configure or register the connector through your platform's approved setup flow. Installing the Skill does not install, authenticate, or restart a connector.
- 4
Verify with one narrow read
List tasks for a specific day or week without writes. Only after the result is correct should you authorize one clearly scoped create or update and verify it by task ID.
Compatibility and dependencies
Compatibility means the runtime can load a local Skill and expose equivalent WeeklyPlanner logical operations. It does not mean every AI product or chat client is automatically supported.
Codex environments
The Skill can run where Codex exposes local Skills and the current session can discover the registered WeeklyPlanner connector operations it needs.
Claude environments
The same workflow directory can be used in Claude environments that support local Skills and expose an equivalent connector at runtime.
Other agents
Treat support as unverified until the runtime can load SKILL.md, preserve its referenced files, and map the required logical operations. A generic prompt import is not equivalent.
Controls that remain in force
The Skill orchestrates the subset of task, group, settings, review, and planning operations required by a workflow. It does not promise to call every MCP tool, and it does not expand connector permissions.
Read the requested range
A request for a specified day, week, or filter authorizes that read. The agent should not query unrelated account data merely to test the connection.
Authorize writes at object level
Create, update, complete, delete, and batch actions require a current instruction that identifies the intended operation. Writes are followed by a task-level read-back.
Preview multi-task scheduling
The agent previews proposed dates or time blocks, waits for explicit confirmation, uses conflict-aware batch patches, and does not batch-move recurring children.
Keep setup actions separate
Connector registration, credentials, push-channel login, test messages, and scheduled jobs each require separate authorization. None happens merely because the Skill was installed.
Continue with the right layer
Task Planner Skill FAQ
- What is the difference between the Task Planner Skill and MCP?
- The Skill contains reusable workflow instructions and safety rules. MCP is one connection layer that exposes structured planner tools. The Skill can orchestrate those tools, but it does not replace or bypass the connector.
- Does installing the Skill connect my account automatically?
- No. Skill installation, connector registration, authentication, and the first real call are separate steps. The Skill discovers capabilities in the current session and reports when the required operations are not exposed.
- Can the Skill change tasks without asking?
- It may perform a write only when the current request authorizes that operation and object. Multi-task scheduling requires a preview and explicit confirmation, and affected tasks are read back after a write.
- Will it send daily notifications after installation?
- No. Conversation summaries work without an external channel. Feishu/Lark or Telegram configuration, test messages, recipients, and scheduled jobs are separate actions that require explicit authorization.