m365-task-manager-by-altf1be_skill

This skill helps you manage Microsoft 365 tasks with To Do and Planner, creating, assigning, tracking, and reminding with clear ownership and due dates.
  • Python

2.6k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill m365-task-manager-by-altf1be

  • _meta.json311 B
  • SKILL.md2.3 KB

Overview

This skill manages lightweight Microsoft 365 task workflows using Microsoft To Do and Planner via Microsoft Graph. It enables quick creation, assignment, tracking, and follow-up of operational tasks with clear owners, due dates, status and daily reminders. The skill is designed for fast, repeatable CRUD of To Do tasks and enforces a deterministic naming and status convention.

How this skill works

The skill authenticates using an Entra app registration and delegated Microsoft Graph permissions, typically via device-code flow with cached tokens. It exposes CLI scripts to list To Do lists, list tasks, and perform create, update and delete operations against Microsoft To Do. Tasks follow a required structure (title, owner, due date, status) and a naming pattern that supports automation and human scanning.

When to use it

  • You need to create and assign operational tasks quickly inside M365 with clear owners and due dates.
  • You want scripted CRUD access to Microsoft To Do for automation or batch updates.
  • You need a lightweight alternative to full project tools for daily operational follow-ups.
  • You require deterministic task naming to integrate with reports or other automation.
  • You want daily reminders and simple status tracking for short-lived work items.

Best practices

  • Register an Entra app with delegated Tasks.ReadWrite, User.Read and offline_access and use a persistent token cache path.
  • Follow the title pattern <project>-<date>-<person>-<action> to keep task names consistent and machine-readable.
  • Always set required fields: title, owner, due date and status to avoid orphaned or ambiguous tasks.
  • Use status values Open, In Progress, Blocked, Done to keep triage and reporting simple.
  • Script repetitive operations via the provided CLI to reduce manual errors and keep auditability.

Example use cases

  • Create daily operational tasks for on-call teams with owner and due date using the CLI.
  • Batch-update status for a set of tasks after a sprint demo or shift handover.
  • Automate creation of checklist tasks for a recurring maintenance window and link them to owners.
  • Delete or archive completed tasks programmatically as part of a housekeeping workflow.
  • Generate consistent task names for ingestion into monitoring or reporting tools.

FAQ

Delegated Microsoft Graph permissions: Tasks.ReadWrite, User.Read and offline_access.

How does authentication work on first run?

The script uses device-code login on first run and caches tokens to the configured M365_TOKEN_CACHE_PATH for reuse.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational