Openclaw Skill M365 Task Manager
Manage lightweight Microsoft 365 task workflows with Microsoft To Do and Planner. Use when a user needs to quickly create, assign, track, and follow up opera...
MIT-0 · Free to use, modify, and redistribute. No attribution required.
⭐ 1 · 327 · 1 current installs · 1 all-time installs
byAbdelkrim from Brussels@Abdelkrim
MIT-0
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description claim Microsoft 365 To Do/Planner task management and the code implements Microsoft Graph CRUD calls. Required env vars (M365_TENANT_ID, M365_CLIENT_ID) map directly to creating an Entra app and using device-code/OAuth; no unrelated credentials or binaries are requested.
Instruction Scope
SKILL.md instructs creating an Entra app, granting delegated Graph permissions, setting env vars, running npm install, and running the provided Node script. The runtime instructions and the script operate only on Microsoft identity endpoints and graph.microsoft.com and do not reference unrelated files or external endpoints. The script does read/write a local token cache (expected for offline_access).
Install Mechanism
There is no automated install spec in the registry metadata (instruction-only), but the README asks the user to run `npm install` in the repo root before using the script. This is reasonable for a Node-based script, but the user should inspect package.json (not included here) and the dependencies before running `npm install`.
Credentials
Only M365_TENANT_ID and M365_CLIENT_ID are required (plus an optional M365_TOKEN_CACHE_PATH). These are proportional to performing delegated Graph operations. No unrelated SECRET/TOKEN/PASSWORD environment variables are requested.
Persistence & Privilege
The skill does not request permanent platform-wide privileges (always is false). It caches OAuth tokens to a local file in the user's home directory by default — appropriate for device-code flow and offline_access scope. It does not modify other skills or global agent config.
Assessment
This skill appears to do exactly what it says: call Microsoft Graph to manage To Do tasks. Before installing or running it: 1) create a proper Entra app with only the delegated Graph scopes you intend to grant; 2) review the repository (especially package.json and dependencies) before running `npm install`; 3) be aware the script uses Device Code flow and will cache tokens locally (default: ~/.cache/openclaw/m365-task-manager-token.json) — store that file securely or set M365_TOKEN_CACHE_PATH to a safe location; 4) confirm the M365_CLIENT_ID you supply is a public client you control/trust (no client secret is used); and 5) if you need enterprise-level auditing/consent, prefer an admin-consented service/app registration or consult your tenant admin. Overall the package is internally coherent and consistent with its stated purpose.Like a lobster shell, security has layers — review code before you run it.
Current versionv0.1.2
Download ziplatest
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
✅ Clawdis
EnvM365_TENANT_ID, M365_CLIENT_ID
Primary envM365_TENANT_ID
SKILL.md
M365 Task Manager
Use this skill to perform real Microsoft Graph CRUD operations for Microsoft To Do tasks.
Setup
- Create an Entra app registration for delegated sign-in.
- Add Microsoft Graph delegated permissions:
Tasks.ReadWriteUser.Readoffline_access
- Configure environment variables:
M365_TENANT_ID=your-tenant-id-or-common
M365_CLIENT_ID=your-public-client-app-id
# optional
M365_TOKEN_CACHE_PATH=/home/user/.cache/openclaw/m365-task-manager-token.json
- Install dependencies at repo root:
npm install
On first run, the script uses Device Code login and caches tokens for reuse.
Commands
# profile connection
node skills/m365-task-manager/scripts/m365-todo.mjs info
# list Microsoft To Do lists
node skills/m365-task-manager/scripts/m365-todo.mjs lists
# list tasks
node skills/m365-task-manager/scripts/m365-todo.mjs tasks:list --list-name "Tasks"
# create task
node skills/m365-task-manager/scripts/m365-todo.mjs tasks:create --list-name "Tasks" --title "2026-03-01-submit-weekly-status-report" --due 2026-03-01
# update task
node skills/m365-task-manager/scripts/m365-todo.mjs tasks:update --list-name "Tasks" --task-id <TASK_ID> --status inProgress
# delete task
node skills/m365-task-manager/scripts/m365-todo.mjs tasks:delete --list-name "Tasks" --task-id <TASK_ID>
Operating standard
- Task title pattern:
YYYY-MM-DD-short-action-owner - Required fields: title, owner, due date, status
- Status values:
Open,In Progress,Blocked,Done
References
references/playbook.mdfor operating guidance.
Scripts
scripts/m365-todo.mjsfor Graph CRUD on Microsoft To Do.scripts/format-task-name.shfor deterministic task naming.
Author
Abdelkrim BOUJRAF - ALT-F1 SRL - https://www.alt-f1.be
License
MIT
Files
4 totalSelect a file
Select a file to preview.
Comments
Loading comments…
