← Back to Skills Marketplace
byungkyu

microsoft-to-do

by byungkyu · GitHub ↗ · v1.2.5 · MIT-0
cross-platform ✓ Security Clean
6863
Downloads
8
Stars
0
Active Installs
11
Versions
Install in OpenClaw
/install microsoft-to-do
Description
Microsoft To Do API integration with managed OAuth. Manage task lists, tasks, checklist items, and linked resources. Use this skill when users want to create, read, update, or delete tasks and task lists in Microsoft To Do. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Requires network access and valid Maton API key. Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Microsoft To Do connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Microsoft To Do action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Microsoft To Do examples; they add no Microsoft To Do capability - Microsoft To Do is not an event source, a trigger cannot read Microsoft To Do data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
Usage Guidance
Before installing, understand that this skill can read and change Microsoft To Do data through your authorized Maton connection. Only approve writes, deletions, function deployments, triggers, or destinations after checking the exact account, target resource, payload, and any ongoing data flow.
Capability Assessment
ℹ Credentials
Network access, OAuth, and Maton API credentials are expected for this integration; raw HTTP/API-key use is limited to environments where the CLI cannot be installed and includes handling cautions.
✓ Install Mechanism
Installation is documented through pinned Maton CLI and SDK package versions, and the artifact contains only Markdown files with no executable bundled scripts.
✓ Instruction Scope
The instructions repeatedly require explicit user approval for connection creation, writes, deletes, function deployment or invocation, trigger destinations, and local event execution; no prompt-hijacking or hidden override language was found.
ℹ Persistence & Privilege
The skill can create persistent OAuth connections, hosted functions, triggers, and trigger destinations, but these behaviors are disclosed, scoped, and require user approval; no unbounded or hidden persistence was identified.
ℹ Purpose & Capability
The stated purpose is to create, read, update, and delete Microsoft To Do task lists, tasks, checklist items, and linked resources; the documented API calls match that purpose, with optional Maton functions and triggers explained as automation paths.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install microsoft-to-do
  3. After installation, invoke the skill by name or use /microsoft-to-do
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.5
Simplify the login instructions to the code flow (maton login prints a link; finish with maton login --code <CODE>), drop the API Key subsection, and pin the Maton CLI install to 0.4.0.
v1.2.4
Switch the login instructions to the device flow (maton login prints a link and a user code; the --oauth flag is gone) and pin the Maton CLI install to 0.3.5.
v1.2.3
Pin the Maton CLI install to 0.3.4, the current release.
v1.2.2
Add this skill's own trigger policy to the shared Triggers section: the only destination it sets up is its own hosted function inside the platform, it does not forward events to third-party hosts, and it does not use event watch --exec; each trigger reference now also says this skill configures no trigger from that source on its own.
v1.2.1
Bring the skill to the current api-gateway baseline and tell the connection-to-function-to-trigger story: the shared Functions and Triggers sections open with an example for this app (a hosted function that performs one action for it through the Maton SDK, and the trigger that runs it - its own event source where it has one, otherwise a time schedule), the description says these constructs turn the connection into automation and add no capability of their own, the passthrough is described by its enforced boundary, CLI and SDK installs are pinned to 0.3.1, absolute API URLs are placeholders, and multipart uploads use mktemp.
v1.2.0
CLI-first rewrite with the Maton SDK examples; clarify that the CLI and SDKs keep separate credential stores, and reword webhook egress warnings
v1.1.0
CLI-first rewrite: the maton CLI with OAuth login is the documented path, every example is a maton command, SDK examples added, and the raw HTTP fallback feeds the key on stdin instead of reading it from the environment
v1.0.3
- Changed API and connection management base URLs from gateway.maton.ai/ctrl.maton.ai to api.maton.ai for all user and OAuth operations. - Improved documentation to clarify connection management steps and strengthened recommendations on specifying the `Maton-Connection` header when multiple accounts are in use. - Added a new section outlining security and user approval requirements for write operations. - Removed the LICENSE.txt file from the skill package.
v1.0.2
- Added new metadata fields under the skill's metadata section, including `clawdbot` requirements and emoji. - Declared `MATON_API_KEY` as a required environment variable within the metadata. - No other documentation or functionality changes detected.
v1.0.1
Version 1.0.1 of microsoft-to-do - No file or documentation changes detected in this release. - No new features, bug fixes, or updates introduced.
v1.0.0
Initial release of Microsoft To Do API integration. - Provides full CRUD operations for task lists, tasks, and checklist items via the Maton API gateway. - Managed OAuth authentication with easy connection management at ctrl.maton.ai. - Supports use of multiple connections with the Maton-Connection header. - Includes detailed usage instructions and example code for all core operations. - Requires a Maton API key for authorization. - Proxies requests to Microsoft Graph API with automatic OAuth handling.
Metadata
Slug microsoft-to-do
Version 1.2.5
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 11
Frequently Asked Questions

What is microsoft-to-do?

Microsoft To Do API integration with managed OAuth. Manage task lists, tasks, checklist items, and linked resources. Use this skill when users want to create, read, update, or delete tasks and task lists in Microsoft To Do. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Requires network access and valid Maton API key. Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Microsoft To Do connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Microsoft To Do action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Microsoft To Do examples; they add no Microsoft To Do capability - Microsoft To Do is not an event source, a trigger cannot read Microsoft To Do data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe). It is an AI Agent Skill for Claude Code / OpenClaw, with 6863 downloads so far.

How do I install microsoft-to-do?

Run "/install microsoft-to-do" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is microsoft-to-do free?

Yes, microsoft-to-do is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does microsoft-to-do support?

microsoft-to-do is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created microsoft-to-do?

It is built and maintained by byungkyu (@byungkyu); the current version is v1.2.5.

💬 Comments