action-items-todo
Use this skill whenever the user asks to monitor, capture, or track action items directed at them across Microsoft Teams chats, meeting transcripts, and Outlook mail, and record them as Microsoft To Do tasks — e.g. "set up action item tracking", "monitor my action items", "capture asks into To Do", "scan for action items now", "what did people ask me to do". Run the SETUP wizard first when no config exists; it asks for the To Do list, scan frequency, and schedule, then creates the recurring automation. Also handles the follow-up commands "scan now", "status", "pause", "resume", and "reconfigure".
microsoft · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add microsoft/cat-agent-skills --skill action-items-todo技能说明
name: action-items-todo description: >- Use this skill whenever the user asks to monitor, capture, or track action items directed at them across Microsoft Teams chats, meeting transcripts, and Outlook mail, and record them as Microsoft To Do tasks — e.g. "set up action item tracking", "monitor my action items", "capture asks into To Do", "scan for action items now", "what did people ask me to do". Run the SETUP wizard first when no config exists; it asks for the To Do list, scan frequency, and schedule, then creates the recurring automation. Also handles the follow-up commands "scan now", "status", "pause", "resume", and "reconfigure".
:: ACTION ITEMS TO MICROSOFT TO DO :: Monitors Teams chats, meeting transcripts, and Outlook mail for action items EXPLICITLY directed at the user, and captures each one as a Microsoft To Do task with a due date, importance, and owner tagging. Microsoft To Do is the only task store this skill writes to.
Nothing about the user (name, email, list name, schedule, customer and workstream names) is hardcoded. Everything lives in the config file written by SETUP.
== FILES == Both live in the user's home directory, so write them with the platform's own separator and never hardcode a Windows path:
- CONFIG: /.scout/action-items-todo/config.json
- STATE (dedupe + last scan): /.scout/action-items-todo/state.json Resolve at runtime (Node os.homedir(), $HOME, or %USERPROFILE% on Windows). Create the directory if missing. Write both files as UTF-8 JSON, atomically (temp file then rename). Always preserve unknown fields.
== CONFIG SCHEMA == { "version": 1, "identity": { "displayName": str, "mail": str, "upn": str, "aadId": str }, "listName": str, // the Microsoft To Do list tasks are written to "frequency": str, // natural-language interval, e.g. "every 30 minutes" "schedule": "24/7" | "weekdays-allhours" | "workhours" | str, "timeZone": str, // IANA zone name, e.g. "Europe/Berlin" "language": "en", // task titles are always written in this language "owners": { "customers": [str], "workstreams": [str] }, // optional, may be empty "excludedChats": [str], // chat/channel names to always ignore "notifyTeams": bool, // send a Teams self-message when items are captured "automationId": str|null, "setupCompleted": ISO8601|null }
== STATE SCHEMA == { "last_scan": ISO8601, "seen": [ { "key": str, "title": str, "created": ISO8601, "source": "teams"|"transcript"|"email", "url": str|null } ] } "key" is a stable hash of source + thread/message id. Keep the last 500 entries; drop older ones.
== SETUP (first run, or on demand) == Run SETUP automatically whenever CONFIG is missing or setupCompleted is null. Never run a scan before SETUP completes.
- Call workiq_get_my_profile and fill identity. If it fails, say so and stop; the skill cannot target asks without knowing who the user is.
- Read the machine time zone as an IANA name with a cross-platform runtime API: Intl.DateTimeFormat().resolvedOptions().timeZone, e.g.
node -p "Intl.DateTimeFormat().resolvedOptions().timeZone". Do NOT use PowerShell Get-TimeZone: on Windows it returns a Windows zone ID such as "W. Europe Standard Time", which is not an IANA name and will not match the format the rest of the skill expects. If the lookup fails, ask the user for their IANA zone rather than guessing. - Read the user's existing lists with workiq_list_task_lists, then ask QUESTION 1 with m_ask_user, free-text mode, inputHint "list name, e.g. Work": "Which Microsoft To Do list should captured action items go into?" Show the existing list names in the assistant message BEFORE the call so the user can pick one or name a new one. After the reply: if the list does not exist, confirm creation, then workiq_create_task_list.
- Ask QUESTION 2 with m_ask_user, multiple choice, recommended index 1: "How often should I scan for new action items?" Answers: "Every 15 minutes" / "Every 30 minutes" / "Every hour" / "Every 2 hours". Store the matching natural-language interval in frequency.
- Ask QUESTION 3 with m_ask_user, multiple choice, recommended index 0:
"When should the scan run?"
Answers:
- "Around the clock, every day" (desc: best when you work across time zones) -> schedule "24/7"
- "Around the clock, weekdays only" -> "weekdays-allhours"
- "Working hours only, weekdays" (desc: 8am-6pm in your local time zone) -> "workhours"
- "Let me describe it" -> free-text follow-up, stored verbatim.
- Ask nothing else. Default the remaining config: language "en", owners empty, excludedChats empty, notifyTeams true.
- Write CONFIG and an empty STATE with last_scan = now minus one frequency interval. Do NOT seed last_scan further back to "catch up". The first run would then backfill items that were already handled or already completed elsewhere, and create tasks for them. A short first window is correct.
- Create the automation with m_create_automation, then store its id in automationId:
- name: "Action Items to To Do" // avoid > and < in the name; they get HTML-escaped in the automation list
- schedule: derived from frequency + schedule (see SCHEDULE MAPPING)
- teamsNotify: "auto"
- prompt: "Load the action-items-todo skill with m_get_skill and run the SCAN procedure exactly as written. Output only the strict result format the skill defines."
- Confirm back in one short block: list name, frequency, schedule, automation id, and how to change any of them ("run /action-items-todo setup again").
== SCHEDULE MAPPING == The scheduler parses a fixed set of forms. A minute interval CANNOT be combined with an hour window in natural language, so the working-hours case must use cron.
- "24/7" -> "" e.g. "every 30 minutes"
- "weekdays-allhours" -> " on weekdays" e.g. "every