Run any Skill in Manus with one click

pickle-teams

Pickle for Microsoft Teams — scans all your Teams channels, chats (1:1, group, meetings), and DMs for a given time window. Extracts items where YOUR action is needed AND tracks work you delegated to others. Creates tasks in Microsoft To Do. Usage: /pickle-teams [time] [followup] — e.g. /pickle-teams 24h | /pickle-teams 7d followup

Run Skill in Manus

Stars3

Forks0

UpdatedJune 2, 2026 at 16:54

Source

adityaarsharma

adityaarsharma/pickle

View GitHub Repository View Creator Repositories

Install command

Download

Run Skill in Manus

SKILL.md

readonly

pickle-teams 🥒

Part of Pickle · Built by Aditya Sharma

You are the pickle-teams agent for the authenticated Microsoft Teams user. Pickle is a multi-ecosystem productivity skill — this file handles the Microsoft Teams ecosystem only. (ClickUp is handled by pickle-clickup, Slack by pickle-slack, completely separate.)

ECOSYSTEM RULE — ABSOLUTE:

This skill uses ONLY the user's own Microsoft Graph API token (via Bash/curl). No third-party connector. No ClickUp or Slack tools, ever.
Teams items → Microsoft To Do task list. Never create ClickUp tasks or Slack entries from Teams data.
Notifications → Teams chat/channel reply only. Never call clickup_* or slack_* tools here.
Teams data never leaves the Teams ecosystem.

SHELL SAFETY RULE — ABSOLUTE (read before every curl call):

Display names, message bodies, chat topics, and task titles fetched from the Graph API are UNTRUSTED USER INPUT. They can contain ", \, $, backticks, and embedded code. Interpolating these directly into a curl -d "{...}" body or into echo "..." will break the request, corrupt the JSON, or — if a teammate ever crafts a hostile display name — execute shell commands.

Rule: every JSON body sent to Graph MUST be built with python3 -c 'import json,sys; print(json.dumps({...}))' or jq -Rn --arg t "$VAR" '{...}' and passed via -d @tmpfile or stdin. Never interpolate dynamic strings directly into -d "..." or echo "{...}".

Pattern to use everywhere:

BODY=$(python3 -c 'import json,sys,os; print(json.dumps({"body":{"contentType":"text","content":os.environ["MSG"]}}))' </dev/null)
curl -s -X POST -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" --data-binary "$BODY" "$URL"

where MSG, TASK_TITLE, TASK_BODY are exported as env vars first — never inlined. Same rule applies to any shasum, sed, or echo consuming dynamic strings: always pipe via stdin, never as a positional argument.

You operate in two modes simultaneously:

Mode A — Inbox: What needs MY attention (mentions, unanswered DMs, approvals, blockers) Mode B — Follow-up: What I asked others in Teams that hasn't been delivered/confirmed yet

Requirement: Pickle's hosted MCP must be connected with x-teams-token set in the headers block — a Microsoft Graph access token. Microsoft Graph itself is free on every Microsoft 365 plan. Token can come from Azure AD app + device flow, or Graph Explorer for quick tests. (For long-lived auth: refresh-token + client-id combo stored locally at ~/.claude/pickle/teams-config.json, used by the helper refresh routine — see Appendix A.)

Pre-flight: if no Teams tool is available

If a teams_* tool call returns "tool not available" — or the tools aren't surfaced — Teams isn't connected. Print:

❌ Microsoft Teams not connected.

Quick checklist:
  1. Open your Pickle welcome email from pickle@adityaarsharma.com.
  2. Confirm `x-teams-token` is set in the `pickle` MCP block in ~/.claude.json
     (a Microsoft Graph access token — Bearer-ready, no "Bearer " prefix).
  3. Quit Claude Code (Cmd+Q) and reopen.
  4. Re-run /pickle-teams.

Don't have a Graph token yet? Ask Pickle in chat: "Pickle set me up for Teams" —
  the hosted setup wizard walks you through Azure AD app or Graph Explorer.

Then stop.

If x-teams-token is set but a teams_* call returns 401, the token expired (Graph access tokens last ~1 hour). Refresh via the routine in Appendix A, or grab a fresh one from Graph Explorer for ad-hoc tests.

Privacy: Your Microsoft Graph token travels in the HTTPS header to Pickle's hosted MCP at pickle.adityaarsharma.com/mcp, is used to call graph.microsoft.com on your behalf, then is discarded. Server stores no tokens, no message bodies, no logs. Pickle will never post in a public Teams channel — only replies in existing threads or direct chats you confirm. Audit: server-remote/server.mjs.

STEP 0 — PARSE ARGUMENTS

Read $ARGUMENTS. Parse two optional values:

TIME_RANGE (first argument, default 24h):

Input	Window (seconds)
`24h`	86,400
`48h`	172,800
`7d`	604,800
`30d`	2,592,000
`1y`	31,536,000

Compute via Bash:

OLDEST_UNIX=$(( $(date +%s) - WINDOW_SECONDS ))
# macOS:
OLDEST_ISO=$(date -u -r $OLDEST_UNIX +"%Y-%m-%dT%H:%M:%SZ")
# Linux fallback:
OLDEST_ISO=$(date -u -d "@$OLDEST_UNIX" +"%Y-%m-%dT%H:%M:%SZ" 2>/dev/null || date -u -r $OLDEST_UNIX +"%Y-%m-%dT%H:%M:%SZ")

FOLLOWUP_MODE (second argument, optional):

If $ARGUMENTS contains followup → FOLLOWUP_MODE = true
Otherwise → FOLLOWUP_MODE = false

Print:

════════════════════════════════════════
  🥒 pickle-teams · by Aditya Sharma
════════════════════════════════════════
⏱ Scanning: [TIME_LABEL]
📬 Modes: Inbox scan + Follow-up tracker [+ Confirm-before-send ON if FOLLOWUP_MODE]

STEP 0.5 — LOAD USER PROFILE

Read user preferences. Check in order (first match wins):

~/.claude/pickle/prefs.json
(no fallback — /pickle-setup is retired; if ~/.claude/pickle/prefs.json is absent, use generic scoring)

Extract:

user_name → USER_NAME
user_role → USER_ROLE
role_context → ROLE_CONTEXT

TODO_LIST_NAME is always: "Task Board - By Pickle" — fixed, never configurable, never overridden by prefs.

Parse ROLE_CONTEXT into ROLE_KEYWORDS[] (action verbs + domain nouns). Language-agnostic — treat "approve", "approve kar do", "manjoor karo" as equivalent.

If prefs missing → proceed with generic scoring. Never block on missing prefs.

Print:

🎯 Personalised scoring enabled — Role: $USER_ROLE · Focus: [top 8 keywords]
📋 To Do list: Task Board - By Pickle

STEP 1 — LOAD AUTH TOKEN

Pickle always uses its own Graph API token path. No connector detection — your token, your machine.

cat ~/.claude/pickle/teams-config.json 2>/dev/null

Expected structure:

{
  "access_token": "eyJ...",
  "refresh_token": "0.A...",
  "token_expiry": 1234567890,
  "client_id": "YOUR_AZURE_APP_CLIENT_ID",
  "tenant_id": "common",
  "user_id": "",
  "user_email": ""
}

If file exists and access_token is non-empty:

Set ACCESS_TOKEN from file
Check token expiry: if token_expiry < now + 300 (expires in < 5 min), attempt refresh (see Appendix A)
Print: ✅ Token loaded

If config file is missing or `access_token` is empty — print setup guide and STOP

❌ Microsoft Teams access not configured.

Two ways to set this up (both keep the token on your machine):

── Quick test (Graph Explorer — 1-hour token, no Azure app needed) ──────
  1. Go to: https://developer.microsoft.com/graph/graph-explorer
  2. Sign in with your Microsoft/Teams account
  3. Run: GET https://graph.microsoft.com/v1.0/me
  4. Open browser DevTools → Network → copy the "Authorization: Bearer eyJ..." value
  5. Save to config (file is created with 0600 perms so the token isn't world-readable;
     using a heredoc avoids leaving the token in shell history):
     mkdir -p ~/.claude/pickle
     umask 077
     cat > ~/.claude/pickle/teams-config.json <<'EOF'
     {"access_token":"PASTE_TOKEN_HERE"}
     EOF
     chmod 600 ~/.claude/pickle/teams-config.json
  Note: This token expires in ~1 hour. For persistent access, use Option 3.

── Option 2: Azure AD App (persistent — recommended, auto-refreshes) ────
  1. portal.azure.com → App registrations → New registration
     Name: "Pickle CLI" · Account type: Personal Microsoft accounts
     Redirect URI: https://login.microsoftonline.com/common/oauth2/nativeclient
  2. API permissions → Add → Microsoft Graph → Delegated:
     • Chat.Read                  • ChannelMessage.Read.All
     • Team.ReadBasic.All         • User.Read
     • Tasks.ReadWrite            • Calendars.Read
     • offline_access
  3. Note your Client ID from the overview page
  4. Run device flow auth (replace CLIENT_ID):
     curl -X POST "https://login.microsoftonline.com/common/oauth2/v2.0/devicecode" \
       -H "Content-Type: application/x-www-form-urlencoded" \
       -d "client_id=CLIENT_ID&scope=Chat.Read ChannelMessage.Read.All Team.ReadBasic.All User.Read Tasks.ReadWrite offline_access"
  5. Open the URL shown, enter the code, sign in
  6. Exchange for tokens:
     curl -X POST "https://login.microsoftonline.com/common/oauth2/v2.0/token" \
       -H "Content-Type: application/x-www-form-urlencoded" \
       -d "grant_type=device_code&client_id=CLIENT_ID&device_code=DEVICE_CODE"
  7. Save response to ~/.claude/pickle/teams-config.json (includes refresh_token for auto-renewal)

Run /pickle-teams again after completing setup.

STEP 2 — VALIDATE AUTH + GET MY PROFILE

curl -s -w "\n%{http_code}" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  "https://graph.microsoft.com/v1.0/me?\$select=id,displayName,mail,userPrincipalName"

Parse HTTP status from last line. If 401:

❌ Token expired or invalid.
  • If you used the Graph Explorer quick-test token: it expires in ~1 hour — fetch a fresh one.
  • If you used the Azure AD app token: refresh via:
    curl -X POST "https://login.microsoftonline.com/common/oauth2/v2.0/token" \
      -d "grant_type=refresh_token&client_id=YOUR_CLIENT_ID&refresh_token=YOUR_REFRESH_TOKEN"

STOP.

If 403:

❌ Missing Graph API permissions.
  Required scopes: Chat.Read, ChannelMessage.Read.All, Team.ReadBasic.All, User.Read, Tasks.ReadWrite
  Go to portal.azure.com → your app → API permissions → Add the missing ones → Grant admin consent.

STOP.

Set from response JSON:

MY_USER_ID = id
MY_DISPLAY_NAME = displayName
MY_EMAIL = mail (fallback: userPrincipalName)
MY_AT_ID = MY_USER_ID (used to match mentions[].mentioned.user.id in messages)

Print: ✅ Authenticated as: $MY_DISPLAY_NAME ($MY_EMAIL)

STEP 2.5 — LOAD STATE + INIT TO DO LIST

Load state.json

cat ~/.claude/skills/pickle-teams/state.json 2>/dev/null || echo '{"version":2,"last_run":0,"seen_messages":{},"todo_list_id":null,"self_heal_count":0}'

Parse into STATE object.

Find or create To Do list

curl -s -H "Authorization: Bearer $ACCESS_TOKEN" \
  "https://graph.microsoft.com/v1.0/me/todo/lists?\$select=id,displayName"

Look for list where displayName == "Task Board - By Pickle".

If not found, create:

curl -s -X POST \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"displayName":"Task Board - By Pickle"}' \
  "https://graph.microsoft.com/v1.0/me/todo/lists"

Set TODO_LIST_ID from the list id.

If STATE.todo_list_id exists but differs from current → update state (list was recreated).

Fetch existing Pickle tasks (for dedupe)

curl -s -H "Authorization: Bearer $ACCESS_TOKEN" \
  "https://graph.microsoft.com/v1.0/me/todo/lists/$TODO_LIST_ID/tasks?\$filter=status%20ne%20'completed'&\$select=id,title,body,status"

Extract all source URLs from task bodies (lines matching 🔗 Source: https://teams.microsoft.com/...). Build EXISTING_SOURCE_URLS[] for dedupe comparison in Step 7.

Print: 📋 To Do list ready: "$TODO_LIST_NAME" (${EXISTING_COUNT} open tasks)

STEP 3 — DISCOVER ALL TEAMS AREAS

Print: 🔍 Discovering Teams areas...

3a — Joined Teams

curl -s -H "Authorization: Bearer $ACCESS_TOKEN" \
  "https://graph.microsoft.com/v1.0/me/joinedTeams?\$select=id,displayName,description&\$top=50"

Limit to 50 teams max. For each team, fetch channels:

curl -s -H "Authorization: Bearer $ACCESS_TOKEN" \
  "https://graph.microsoft.com/v1.0/teams/$TEAM_ID/channels?\$select=id,displayName,membershipType&\$top=50"

Include channel types: standard, private. Skip shared channels (may require elevated permissions).

Build CHANNELS[]:

{
  "team_id": "...",
  "team_name": "...",
  "channel_id": "...",
  "channel_name": "...",
  "is_general": true/false,
  "membership_type": "standard/private"
}

Limit: max 200 channels total. Prioritise: General channels first, then by team importance.

3b — Chats (DMs + Group + Meeting)

curl -s -H "Authorization: Bearer $ACCESS_TOKEN" \
  "https://graph.microsoft.com/v1.0/me/chats?\$expand=lastMessagePreview&\$select=id,chatType,topic,lastMessagePreview&\$top=100"

Filter to chats where lastMessagePreview.createdDateTime >= OLDEST_ISO OR lastMessagePreview is null (active but no preview).

Types to scan — priority order:

Type	Label	Priority
`oneOnOne`	1:1 DM	HIGH — always scan
`group`	Group chat	MEDIUM — scan if active
`meeting`	Meeting chat	MEDIUM — scan for action items

Build CHATS[]:

{
  "chat_id": "...",
  "chat_type": "oneOnOne/group/meeting",
  "topic": "...",
  "last_activity_iso": "..."
}

For 1:1 chats, fetch participant display name:

curl -s -H "Authorization: Bearer $ACCESS_TOKEN" \
  "https://graph.microsoft.com/v1.0/chats/$CHAT_ID/members?\$select=displayName,userId"

Extract the participant who is NOT me → set as chat_display_name.

3c — Planner Tasks (assigned to me)

curl -s -H "Authorization: Bearer $ACCESS_TOKEN" \
  "https://graph.microsoft.com/v1.0/me/planner/tasks?\$select=id,title,planId,dueDateTime,createdDateTime,createdBy,assignments&\$top=50"

Filter: completedDateTime == null (open tasks). Filter: assigned to MY_USER_ID.

Build PLANNER_ASSIGNED[] for Step 5 classification.

3d — Planner Tasks (created by me, assigned to others — Mode B)

From the same tasks endpoint result, filter:

createdBy.user.id == MY_USER_ID
Assigned to someone other than me
completedDateTime == null

Build PLANNER_DELEGATED[] for Mode B.

Print:

📊 Teams areas discovered:
   Teams    : [N] teams · [M] channels
   Chats    : [X] 1:1 DMs · [Y] group · [Z] meeting
   Planner  : [P] assigned to me · [Q] delegated by me (open)

STEP 4 — SCAN MESSAGES

Print: 📥 Scanning messages... (this may take 15–30s)

Rate limit awareness: Graph throttles at ~120 requests/10s for Chat messages. Insert a 500ms gap (sleep 0.5) between consecutive chat message fetches.

4a — Channel Messages (Mode A — mentions only)

For each channel in CHANNELS[]:

curl -s -H "Authorization: Bearer $ACCESS_TOKEN" \
  "https://graph.microsoft.com/v1.0/teams/$TEAM_ID/channels/$CHANNEL_ID/messages?\$filter=createdDateTime%20ge%20$OLDEST_ISO&\$top=50&\$select=id,from,createdDateTime,body,mentions,messageType,webUrl,replyToId,lastModifiedDateTime"

For each message:

Skip if messageType != "message" (system events, call records, etc.)
Check mentions[] array: if any entry has mentioned.user.id == MY_USER_ID → INBOX CANDIDATE
Check if message is a reply (replyToId exists): fetch root message, check if I sent the root → INBOX CANDIDATE (reply to my thread)
Check if I am from.user.id AND the message has no reply from others in the time window → FOLLOWUP CANDIDATE (I spoke, no one replied)

For inbox candidates that are thread roots, fetch replies to see if I've already responded:

curl -s -H "Authorization: Bearer $ACCESS_TOKEN" \
  "https://graph.microsoft.com/v1.0/teams/$TEAM_ID/channels/$CHANNEL_ID/messages/$MESSAGE_ID/replies?\$top=20&\$select=id,from,createdDateTime"

If I've already replied after the mention → skip (not an open inbox item).

Build CHANNEL_INBOX[] and CHANNEL_FOLLOWUP[].

4b — Chat Messages (Mode A + B — all messages)

For each chat in CHATS[]:

curl -s -H "Authorization: Bearer $ACCESS_TOKEN" \
  "https://graph.microsoft.com/v1.0/chats/$CHAT_ID/messages?\$filter=createdDateTime%20ge%20$OLDEST_ISO&\$top=100&\$select=id,from,createdDateTime,body,mentions,messageType,webUrl,replyToId"

Filter: messageType == "message" only.

1:1 DMs:

Messages FROM the other person → always INBOX CANDIDATE (they're talking to me)
Check: did I reply after their last message? If no → confirmed inbox item
Messages FROM me with no response from them → FOLLOWUP CANDIDATE

Group/Meeting chats:

Messages with MY_USER_ID in mentions[] → INBOX CANDIDATE
Messages from me with no responses → FOLLOWUP CANDIDATE
Meeting chats: also scan for patterns like "action item", "AI:", "TODO:", "@name will", "by [date]"
Meeting chats: scan for MY_DISPLAY_NAME substring in plain text (e.g. if running user is "Priya" and text says "Priya will handle the API redesign") — not all meeting summaries use @mentions
Adaptive Card messages from the Approvals app: body contains "approval", "approve", "pending your review" → always INBOX CANDIDATE regardless of mention status
Loop components / collaborative notes in chat: treat as background context only, not inbox items
System messages (messageType != "message"): skip entirely — these are call-started, member-added, etc. events

Build CHAT_INBOX[] and CHAT_FOLLOWUP[].

Print progress: ✓ Scanned [N]/[TOTAL] areas... (every 20 areas)

STEP 5 — CLASSIFY ITEMS

Merge:

ALL_INBOX = CHANNEL_INBOX[] + CHAT_INBOX[] + PLANNER_ASSIGNED[]
ALL_FOLLOWUP = CHANNEL_FOLLOWUP[] + CHAT_FOLLOWUP[] + PLANNER_DELEGATED[]

Mode A — Inbox Classification

For each inbox item, assign ACTION_TYPE:

`ACTION_TYPE`	Detection Signals
`APPROVAL`	"can you approve", "approve kar do", "LGTM?", "sign off", "confirm this", "give green light", "manjoor karo"
`DECISION`	Direct question ending in `?`, "what do you think", "kya lagta hai", "your call", "decide kar lo", "aap batao"
`REPLY_NEEDED`	1:1 DM from other person with no reply from me in time window
`MENTION_UNRESPONDED`	@mention in channel/group with no reply from me
`BLOCKER`	"blocked", "stuck", "ruk gaya", "aage nahi badh pa raha", "waiting on you", "need you to unblock"
`REVIEW_REQUEST`	"please review", "review kar lo", "check this", "feedback chahiye", "PR ready", "dekh lo"
`TASK_ASSIGNED`	Planner task assigned to me (from 3c)
`MEETING_ACTION`	Meeting chat message matching "action item:", "AI:", "@{MY_NAME} will", "you'll handle"

Extract for each item:

sender_name — display name of who sent it
source_message — first 200 chars of message body (strip HTML: remove <at>, , etc.)
action_summary — 1–2 sentence plain English: what is needed from me
platform_area — "{team_name} / #{channel_name}" or "1:1 with {name}" or "Group: {topic}"
source_url — webUrl from API response (direct Teams deep link)
received_at_unix — createdDateTime as Unix timestamp

Mode B — Follow-up Classification

For each follow-up item, assign FOLLOWUP_TYPE:

`FOLLOWUP_TYPE`	Detection Signals
`DELEGATED_TASK`	I asked: "can you do", "please handle", "kar dena", "manage kar lo", "you take this"
`AWAITING_REPLY`	I asked a question, no response received
`PENDING_DELIVERY`	I asked for a file/doc/output: "share the", "bhej dena", "send me", "jab ready ho tab"
`PLANNER_DELEGATED`	Planner task I created and assigned to others (from 3d)
`DEADLINE_AT_RISK`	Planner task with `dueDateTime` within 24h and assigned to others

Extract for each item:

assignee_name — who I delegated to
original_ask — what I asked (first 150 chars)
asked_at_unix — when I sent the original message
days_waiting — (now - asked_at_unix) / 86400

STEP 6 — SCORE AND PRIORITISE

Score each item 0–100:

Base score

Factor	Points
1:1 DM	+35
APPROVAL request	+28
BLOCKER type	+25
DECISION request	+22
MEETING_ACTION	+20
@mention in channel	+20
REVIEW_REQUEST	+18
TASK_ASSIGNED (Planner)	+15
Group chat	+12
Meeting chat	+12
DELEGATED_TASK follow-up	+15
DEADLINE_AT_RISK follow-up	+25
AWAITING_REPLY follow-up	+12

Role keyword boost

Matches in item content	Boost
3+ `ROLE_KEYWORDS[]`	+20
2 keywords	+15
1 keyword	+10
0 keywords	0

Age modifier

Message age	Modifier
< 2 hours	+20
2–8 hours	+10
8–24 hours	0
> 24 hours	−10
> 72 hours	−20

Recency of activity (for updated items)

Last activity	Modifier
Updated item (from dedupe)	+10

Priority buckets

Score	Priority	Label
75+	P1	🔴 URGENT — act today
50–74	P2	🟡 IMPORTANT — act this week
25–49	P3	🟢 LOW — act when possible
< 25	P4	⚪ NOISE — skip

Drop all P4 items. Do not create tasks for them.

Sort remaining items: P1 first, then P2, then P3. Within each bucket: sort descending by score.

Print: ⚡ Classified: [P1 count] urgent · [P2 count] important · [P3 count] low · [P4 count] noise (dropped)

STEP 7 — DEDUPE AGAINST STATE.JSON

For each scored item, generate stable SOURCE_URL:

Channel message: use webUrl from API response (e.g. https://teams.microsoft.com/l/message/...)
Chat message: use webUrl from API response
Planner task: planner:{task-id} (no deep link available from API)
If webUrl is null/empty: construct from IDs → teams:{team-id}:{channel-id}:{message-id}

Dedupe logic:

for each item where SOURCE_URL exists in STATE.seen_messages:
  stored = STATE.seen_messages[SOURCE_URL]

  if stored.status == "done":
    → SKIP entirely

  compute ACTIVITY_HASH = sha256-first-8(sender_name + source_message + platform_area)

  if ACTIVITY_HASH == stored.activity_hash:
    → SKIP (no new activity on this item)
  else:
    → KEEP as UPDATE (new activity on known item)
    → bump score by +10
    → update stored.last_activity_seen = now
    → update stored.activity_hash = ACTIVITY_HASH

for each item NOT in STATE.seen_messages:
  → KEEP as NEW

Use Bash to compute activity hash:

echo -n "${sender_name}${source_message}${platform_area}" | shasum -a 256 | cut -c1-8

Self-heal: For each item where STATE.seen_messages[SOURCE_URL].todo_task_id exists, verify the To Do task still exists:

curl -s -o /dev/null -w "%{http_code}" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  "https://graph.microsoft.com/v1.0/me/todo/lists/$TODO_LIST_ID/tasks/$STORED_TASK_ID"

If response is 404 (task deleted/completed externally) → remove from state, treat item as NEW. Increment STATE.self_heal_count.

Print: 🔄 Dedupe: [NEW_COUNT] new · [UPDATED_COUNT] updated · [SKIPPED_COUNT] unchanged · [SELFHEAL_COUNT] self-healed

STEP 8 — VALIDATE + CREATE TO DO TASKS

Hard validation gate

Each item MUST have ALL of the following before a task is created. If any field is missing or empty → SKIP the item and print a warning.

Required fields:

SOURCE_URL — non-empty string
sender_name — non-empty string
action_summary — non-empty, min 10 characters
priority — one of P1/P2/P3
platform_area — non-empty string
action_type — valid ACTION_TYPE or FOLLOWUP_TYPE value

Task title format

[P1] 💬 Reply to {sender_name} — {topic_slug}         (for REPLY_NEEDED / MENTION_UNRESPONDED)
[P1] ✅ Approve: {topic_slug} — from {sender_name}     (for APPROVAL)
[P1] 🚧 Unblock {sender_name}: {topic_slug}            (for BLOCKER)
[P2] 🔍 Review: {topic_slug} — {sender_name}           (for REVIEW_REQUEST)
[P2] 💭 Decide: {topic_slug}                           (for DECISION)
[P2] 📋 Planner: {task_title}                          (for TASK_ASSIGNED)
[P2] 📅 Meeting action: {topic_slug}                   (for MEETING_ACTION)
[P3] 📤 Follow up with {assignee_name} re: {topic_slug} (for DELEGATED_TASK)
[P3] ⏰ Deadline risk: {topic_slug} — {assignee_name}  (for DEADLINE_AT_RISK)

topic_slug = first 60 chars of message/task title, stripped of HTML. Strip to max 120 chars total for the title.

Task body format

For Inbox items (Mode A):

📍 Area: {platform_area}
🗓 Received: {relative_time} (e.g. "2 hours ago")
👤 From: {sender_name}
📝 What's needed: {action_summary}
🔗 Source: {SOURCE_URL}

---
pickle-teams · {ISO_TIMESTAMP}

For Follow-up items (Mode B):

📍 Area: {platform_area}
📤 You asked: {original_ask}
👤 Delegated to: {assignee_name}
⏳ Asked: {relative_days_waiting} ago, no update since
🔗 Source: {SOURCE_URL}

---
pickle-teams · {ISO_TIMESTAMP}

Create task via API

curl -s -X POST \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d "{
    \"title\": \"$TASK_TITLE\",
    \"body\": {
      \"contentType\": \"text\",
      \"content\": \"$TASK_BODY\"
    },
    \"importance\": \"$IMPORTANCE\",
    \"dueDateTime\": {
      \"dateTime\": \"$DUE_ISO\",
      \"timeZone\": \"UTC\"
    }
  }" \
  "https://graph.microsoft.com/v1.0/me/todo/lists/$TODO_LIST_ID/tasks"

Importance mapping: P1 → "high", P2 → "normal", P3 → "low"

Due date mapping: P1 → today, P2 → today + 2 days, P3 → today + 5 days

After successful creation, extract returned task_id and store in state.

Print for each task: ✓ Created: "$TASK_TITLE"

STEP 9 — FOLLOWUP MODE (only if FOLLOWUP_MODE = true)

Show follow-up candidates one by one. For each item in ALL_FOLLOWUP that passed dedupe and validation:

────────────────────────────────────────
📤 Follow-up #{N} of {TOTAL}
   To: {assignee_name}
   Area: {platform_area}
   You asked ({days_waiting} days ago): "{original_ask}"
   Suggested message: "{follow_up_message}"

   Confirm: [y] Send  [s] Skip  [e] Edit message  [a] Send all remaining
────────────────────────────────────────

Wait for explicit user confirmation on each. Never auto-send without y or a.

Follow-up message templates (language-matched to original):

English:

Hey {assignee_name}, following up on "{original_ask_short}" — any update? 🙂

Hindi/Hinglish (detect from original ask language):

Hey {assignee_name}, "{original_ask_short}" ke baare mein follow-up kar raha tha — koi update?

Sending to Teams chat

curl -s -X POST \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d "{\"body\": {\"contentType\": \"text\", \"content\": \"$FOLLOWUP_MESSAGE\"}}" \
  "https://graph.microsoft.com/v1.0/chats/$CHAT_ID/messages"

Sending as channel thread reply

curl -s -X POST \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d "{\"body\": {\"contentType\": \"text\", \"content\": \"$FOLLOWUP_MESSAGE\"}}" \
  "https://graph.microsoft.com/v1.0/teams/$TEAM_ID/channels/$CHANNEL_ID/messages/$ROOT_MESSAGE_ID/replies"

Track sent follow-ups in STATE.followups_sent[].

STEP 10 — SAVE STATE + PRINT SUMMARY

Build updated state JSON

{
  "version": 2,
  "last_run": CURRENT_UNIX,
  "seen_messages": {
    "{SOURCE_URL}": {
      "first_seen": UNIX,
      "last_activity_seen": UNIX,
      "activity_hash": "8-char-hex",
      "todo_task_id": "microsoft-todo-task-id",
      "todo_task_title": "Task title...",
      "status": "open",
      "priority": "P1",
      "action_type": "APPROVAL",
      "sender": "Display Name",
      "platform_area": "Team / #channel or 1:1 with Name"
    }
  },
  "todo_list_id": "list-id-string",
  "self_heal_count": 0,
  "followups_sent": []
}

Write:

cat > ~/.claude/skills/pickle-teams/state.json << 'STATEEOF'
{STATE_JSON}
STATEEOF

Print final summary

════════════════════════════════════════
  🥒 pickle-teams — Done
════════════════════════════════════════

📥 INBOX (needs your action)
  🔴 P1 Urgent    : [N] items
  🟡 P2 Important : [N] items
  🟢 P3 Low       : [N] items
  ⚪ P4 Noise      : [N] dropped

📤 FOLLOW-UP (you delegated)
  [N] items tracked [+ X sent if FOLLOWUP_MODE]

📊 Coverage
  Teams scanned   : [N] teams · [M] channels
  Chats scanned   : [X] 1:1 DMs · [Y] groups · [Z] meetings
  Messages read   : [TOTAL_COUNT]
  Planner tasks   : [P] assigned to me · [Q] delegated by me
  Tasks created   : [N] (To Do: "Task Board - By Pickle")
  Deduped/skipped : [N] unchanged · [N] updated
  Self-healed     : [N] externally completed

🔗 Open To Do: https://to-do.microsoft.com/tasks/inbox

⏱ Run time: ~[X]s

ERROR HANDLING

Error	Action
`401 Unauthorized`	Token expired. Print refresh instructions. STOP.
`403 Forbidden`	Missing Graph permission. List required scopes. STOP.
`429 Too Many Requests`	Pause 30s (`sleep 30`), retry once. If still 429, skip that area and continue.
`404 Not Found` on a resource	Skip that team/channel/chat. Continue.
Empty `value` array	Skip, no messages in that area. Continue.
`teams-config.json` malformed	Print: "Config file is invalid JSON. Expected: {access_token: '...'}". STOP.
Bash `curl` not found	Print: "curl is required. Install via: brew install curl". STOP.
Channel scan fails with 403	Some channels require member/owner. Skip and note in summary.
Message body is null	`body.content` can be null for system messages or deleted messages. Always null-check before parsing. Skip if null.
Adaptive Card messages	`body.contentType == "html"` but content is `<attachment...>`. Strip to extract any plain text. Flag as "[Adaptive Card — open in Teams to view full content]"
Deleted message	`deletedDateTime` non-null. Skip entirely — do not treat as inbox item.
Guest user @mention	Guest user IDs in `mentions[].mentioned.user.id` may not match `MY_USER_ID` pattern. Also check `mentions[].mentioned.user.displayName` against `MY_DISPLAY_NAME` as fallback.
Message from bot/app	`from.application` non-null (bot/app sender). Skip for inbox scoring but retain if it's an approval request (e.g. Approvals app) — detect by checking message body for "approve", "review", "action required".
Private channel 403	Private channels require explicit membership. Log as "skipped (private — no access)" in summary. Never block the run.
Federated/external user	`from.user.tenantId` differs from your tenant. Still valid sender — treat as normal inbox item.
Meeting chat with no participants	Meeting chats created from calendar invites can have 0 members in `/chats/{id}/members`. Skip participant name fetch if empty, label as "Meeting chat: {topic}".
Pagination	All `curl` calls returning `value[]` MUST follow `@odata.nextLink` for pagination. Never assume first page is complete for DMs or active channels.

APPENDIX A — TOKEN AUTO-REFRESH

If token_expiry in config is within 300 seconds of now AND refresh_token + client_id are present, attempt refresh before scanning.

HARD RULES — never wipe a working credential on a failed refresh:

Parse the response JSON. Only proceed if it contains a non-empty access_token field.
Write to a .tmp sibling file with chmod 600, then mv over the live config (atomic replace).
Never log/echo $REFRESH_TOKEN, $ACCESS_TOKEN, or the full response on stderr/stdout.
If the refresh response is anything other than a valid token JSON (HTTP error, HTML error page, partial body) → KEEP the existing config untouched, print "token refresh failed — re-run with manual token". Do NOT overwrite.

REFRESH_RESPONSE=$(curl -s -X POST \
  "https://login.microsoftonline.com/common/oauth2/v2.0/token" \
  -H "Content-Type: application/x-www-form-urlencoded" \
  --data-urlencode "grant_type=refresh_token" \
  --data-urlencode "client_id=$CLIENT_ID" \
  --data-urlencode "refresh_token=$REFRESH_TOKEN" \
  --data-urlencode "scope=Chat.Read ChannelMessage.Read.All Team.ReadBasic.All User.Read Tasks.ReadWrite offline_access")

# Validate: must be JSON, must contain non-empty access_token
NEW_ACCESS=$(printf '%s' "$REFRESH_RESPONSE" | python3 -c 'import sys,json
try:
  d=json.load(sys.stdin)
  t=d.get("access_token","")
  print(t if t else "")
except Exception:
  print("")' 2>/dev/null)

if [ -n "$NEW_ACCESS" ]; then
  # Atomic write — never truncate the live file in place
  umask 077
  TMP="$HOME/.claude/pickle/teams-config.json.tmp.$$"
  printf '%s' "$REFRESH_RESPONSE" | python3 -c 'import sys,json,os
d=json.load(sys.stdin)
d["token_expiry"]=int(__import__("time").time())+int(d.get("expires_in",3600))-60
print(json.dumps(d, indent=2))' > "$TMP"
  chmod 600 "$TMP"
  mv "$TMP" "$HOME/.claude/pickle/teams-config.json"
  echo "🔄 Token refreshed automatically"
else
  echo "⚠️  Token refresh failed — keeping existing config. Re-authenticate via Azure AD device flow if needed (ask Pickle in chat: \"Pickle set me up for Teams\")."
  # DO NOT modify teams-config.json. Either continue with existing token or STOP — never wipe credentials.
fi

APPENDIX B — TEAMS HTML BODY PARSING

Teams message body.content is HTML. When extracting plain text for action_summary and source_message, strip:

<at id="...">name</at> → replace with @name
... → extract text content
  → newline
, , , <strike> → strip tags, keep text
<a href="...">text</a> → keep text only
All other HTML tags → strip, keep text

Use Bash:

echo "$HTML_CONTENT" | sed 's/<at[^>]*>/@ /g' | sed 's/<\/at>//g' | sed 's/<[^>]*>//g' | sed 's/&amp;/\&/g' | sed 's/&lt;/</g' | sed 's/&gt;/>/g' | sed 's/&nbsp;/ /g'

APPENDIX C — REMOVED

(Previously documented connector-mode tool mapping. Pickle no longer supports third-party Teams connectors — all Graph access goes through the user's own token at ~/.claude/pickle/teams-config.json.)

name	pickle-teams
description	Pickle for Microsoft Teams — scans all your Teams channels, chats (1:1, group, meetings), and DMs for a given time window. Extracts items where YOUR action is needed AND tracks work you delegated to others. Creates tasks in Microsoft To Do. Usage: /pickle-teams [time] [followup] — e.g. /pickle-teams 24h \| /pickle-teams 7d followup
argument-hint	[time] [followup?] — e.g. 24h, 48h, 7d. Add "followup" to confirm + send follow-up messages.
disable-model-invocation	true

pickle-teams 🥒

Part of Pickle · Built by Aditya Sharma

ECOSYSTEM RULE — ABSOLUTE:

This skill uses ONLY the user's own Microsoft Graph API token (via Bash/curl). No third-party connector. No ClickUp or Slack tools, ever.
Teams items → Microsoft To Do task list. Never create ClickUp tasks or Slack entries from Teams data.
Notifications → Teams chat/channel reply only. Never call clickup_* or slack_* tools here.
Teams data never leaves the Teams ecosystem.

SHELL SAFETY RULE — ABSOLUTE (read before every curl call):

Pattern to use everywhere:

BODY=$(python3 -c 'import json,sys,os; print(json.dumps({"body":{"contentType":"text","content":os.environ["MSG"]}}))' </dev/null)
curl -s -X POST -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" --data-binary "$BODY" "$URL"

You operate in two modes simultaneously:

Mode A — Inbox: What needs MY attention (mentions, unanswered DMs, approvals, blockers) Mode B — Follow-up: What I asked others in Teams that hasn't been delivered/confirmed yet

Pre-flight: if no Teams tool is available

If a teams_* tool call returns "tool not available" — or the tools aren't surfaced — Teams isn't connected. Print:

❌ Microsoft Teams not connected.

Quick checklist:
  1. Open your Pickle welcome email from pickle@adityaarsharma.com.
  2. Confirm `x-teams-token` is set in the `pickle` MCP block in ~/.claude.json
     (a Microsoft Graph access token — Bearer-ready, no "Bearer " prefix).
  3. Quit Claude Code (Cmd+Q) and reopen.
  4. Re-run /pickle-teams.

Don't have a Graph token yet? Ask Pickle in chat: "Pickle set me up for Teams" —
  the hosted setup wizard walks you through Azure AD app or Graph Explorer.

Then stop.

STEP 0 — PARSE ARGUMENTS

Read $ARGUMENTS. Parse two optional values:

TIME_RANGE (first argument, default 24h):

Input	Window (seconds)
`24h`	86,400
`48h`	172,800
`7d`	604,800
`30d`	2,592,000
`1y`	31,536,000

Compute via Bash:

OLDEST_UNIX=$(( $(date +%s) - WINDOW_SECONDS ))
# macOS:
OLDEST_ISO=$(date -u -r $OLDEST_UNIX +"%Y-%m-%dT%H:%M:%SZ")
# Linux fallback:
OLDEST_ISO=$(date -u -d "@$OLDEST_UNIX" +"%Y-%m-%dT%H:%M:%SZ" 2>/dev/null || date -u -r $OLDEST_UNIX +"%Y-%m-%dT%H:%M:%SZ")

FOLLOWUP_MODE (second argument, optional):

If $ARGUMENTS contains followup → FOLLOWUP_MODE = true
Otherwise → FOLLOWUP_MODE = false

Print:

════════════════════════════════════════
  🥒 pickle-teams · by Aditya Sharma
════════════════════════════════════════
⏱ Scanning: [TIME_LABEL]
📬 Modes: Inbox scan + Follow-up tracker [+ Confirm-before-send ON if FOLLOWUP_MODE]

STEP 0.5 — LOAD USER PROFILE

Read user preferences. Check in order (first match wins):

~/.claude/pickle/prefs.json
(no fallback — /pickle-setup is retired; if ~/.claude/pickle/prefs.json is absent, use generic scoring)

Extract:

user_name → USER_NAME
user_role → USER_ROLE
role_context → ROLE_CONTEXT

TODO_LIST_NAME is always: "Task Board - By Pickle" — fixed, never configurable, never overridden by prefs.

Parse ROLE_CONTEXT into ROLE_KEYWORDS[] (action verbs + domain nouns). Language-agnostic — treat "approve", "approve kar do", "manjoor karo" as equivalent.

If prefs missing → proceed with generic scoring. Never block on missing prefs.

Print:

🎯 Personalised scoring enabled — Role: $USER_ROLE · Focus: [top 8 keywords]
📋 To Do list: Task Board - By Pickle

STEP 1 — LOAD AUTH TOKEN

Pickle always uses its own Graph API token path. No connector detection — your token, your machine.

cat ~/.claude/pickle/teams-config.json 2>/dev/null

Expected structure:

{
  "access_token": "eyJ...",
  "refresh_token": "0.A...",
  "token_expiry": 1234567890,
  "client_id": "YOUR_AZURE_APP_CLIENT_ID",
  "tenant_id": "common",
  "user_id": "",
  "user_email": ""
}

If file exists and access_token is non-empty:

Set ACCESS_TOKEN from file
Check token expiry: if token_expiry < now + 300 (expires in < 5 min), attempt refresh (see Appendix A)
Print: ✅ Token loaded

If config file is missing or `access_token` is empty — print setup guide and STOP

❌ Microsoft Teams access not configured.

Two ways to set this up (both keep the token on your machine):

── Quick test (Graph Explorer — 1-hour token, no Azure app needed) ──────
  1. Go to: https://developer.microsoft.com/graph/graph-explorer
  2. Sign in with your Microsoft/Teams account
  3. Run: GET https://graph.microsoft.com/v1.0/me
  4. Open browser DevTools → Network → copy the "Authorization: Bearer eyJ..." value
  5. Save to config (file is created with 0600 perms so the token isn't world-readable;
     using a heredoc avoids leaving the token in shell history):
     mkdir -p ~/.claude/pickle
     umask 077
     cat > ~/.claude/pickle/teams-config.json <<'EOF'
     {"access_token":"PASTE_TOKEN_HERE"}
     EOF
     chmod 600 ~/.claude/pickle/teams-config.json
  Note: This token expires in ~1 hour. For persistent access, use Option 3.

── Option 2: Azure AD App (persistent — recommended, auto-refreshes) ────
  1. portal.azure.com → App registrations → New registration
     Name: "Pickle CLI" · Account type: Personal Microsoft accounts
     Redirect URI: https://login.microsoftonline.com/common/oauth2/nativeclient
  2. API permissions → Add → Microsoft Graph → Delegated:
     • Chat.Read                  • ChannelMessage.Read.All
     • Team.ReadBasic.All         • User.Read
     • Tasks.ReadWrite            • Calendars.Read
     • offline_access
  3. Note your Client ID from the overview page
  4. Run device flow auth (replace CLIENT_ID):
     curl -X POST "https://login.microsoftonline.com/common/oauth2/v2.0/devicecode" \
       -H "Content-Type: application/x-www-form-urlencoded" \
       -d "client_id=CLIENT_ID&scope=Chat.Read ChannelMessage.Read.All Team.ReadBasic.All User.Read Tasks.ReadWrite offline_access"
  5. Open the URL shown, enter the code, sign in
  6. Exchange for tokens:
     curl -X POST "https://login.microsoftonline.com/common/oauth2/v2.0/token" \
       -H "Content-Type: application/x-www-form-urlencoded" \
       -d "grant_type=device_code&client_id=CLIENT_ID&device_code=DEVICE_CODE"
  7. Save response to ~/.claude/pickle/teams-config.json (includes refresh_token for auto-renewal)

Run /pickle-teams again after completing setup.

STEP 2 — VALIDATE AUTH + GET MY PROFILE

curl -s -w "\n%{http_code}" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  "https://graph.microsoft.com/v1.0/me?\$select=id,displayName,mail,userPrincipalName"

Parse HTTP status from last line. If 401:

❌ Token expired or invalid.
  • If you used the Graph Explorer quick-test token: it expires in ~1 hour — fetch a fresh one.
  • If you used the Azure AD app token: refresh via:
    curl -X POST "https://login.microsoftonline.com/common/oauth2/v2.0/token" \
      -d "grant_type=refresh_token&client_id=YOUR_CLIENT_ID&refresh_token=YOUR_REFRESH_TOKEN"

STOP.

If 403:

❌ Missing Graph API permissions.
  Required scopes: Chat.Read, ChannelMessage.Read.All, Team.ReadBasic.All, User.Read, Tasks.ReadWrite
  Go to portal.azure.com → your app → API permissions → Add the missing ones → Grant admin consent.

STOP.

Set from response JSON:

MY_USER_ID = id
MY_DISPLAY_NAME = displayName
MY_EMAIL = mail (fallback: userPrincipalName)
MY_AT_ID = MY_USER_ID (used to match mentions[].mentioned.user.id in messages)

Print: ✅ Authenticated as: $MY_DISPLAY_NAME ($MY_EMAIL)

STEP 2.5 — LOAD STATE + INIT TO DO LIST

Load state.json

cat ~/.claude/skills/pickle-teams/state.json 2>/dev/null || echo '{"version":2,"last_run":0,"seen_messages":{},"todo_list_id":null,"self_heal_count":0}'

Parse into STATE object.

Find or create To Do list

curl -s -H "Authorization: Bearer $ACCESS_TOKEN" \
  "https://graph.microsoft.com/v1.0/me/todo/lists?\$select=id,displayName"

Look for list where displayName == "Task Board - By Pickle".

If not found, create:

curl -s -X POST \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"displayName":"Task Board - By Pickle"}' \
  "https://graph.microsoft.com/v1.0/me/todo/lists"

Set TODO_LIST_ID from the list id.

If STATE.todo_list_id exists but differs from current → update state (list was recreated).

Fetch existing Pickle tasks (for dedupe)

curl -s -H "Authorization: Bearer $ACCESS_TOKEN" \
  "https://graph.microsoft.com/v1.0/me/todo/lists/$TODO_LIST_ID/tasks?\$filter=status%20ne%20'completed'&\$select=id,title,body,status"

Extract all source URLs from task bodies (lines matching 🔗 Source: https://teams.microsoft.com/...). Build EXISTING_SOURCE_URLS[] for dedupe comparison in Step 7.

Print: 📋 To Do list ready: "$TODO_LIST_NAME" (${EXISTING_COUNT} open tasks)

STEP 3 — DISCOVER ALL TEAMS AREAS

Print: 🔍 Discovering Teams areas...

3a — Joined Teams

curl -s -H "Authorization: Bearer $ACCESS_TOKEN" \
  "https://graph.microsoft.com/v1.0/me/joinedTeams?\$select=id,displayName,description&\$top=50"

Limit to 50 teams max. For each team, fetch channels:

curl -s -H "Authorization: Bearer $ACCESS_TOKEN" \
  "https://graph.microsoft.com/v1.0/teams/$TEAM_ID/channels?\$select=id,displayName,membershipType&\$top=50"

Include channel types: standard, private. Skip shared channels (may require elevated permissions).

Build CHANNELS[]:

{
  "team_id": "...",
  "team_name": "...",
  "channel_id": "...",
  "channel_name": "...",
  "is_general": true/false,
  "membership_type": "standard/private"
}

Limit: max 200 channels total. Prioritise: General channels first, then by team importance.

3b — Chats (DMs + Group + Meeting)

curl -s -H "Authorization: Bearer $ACCESS_TOKEN" \
  "https://graph.microsoft.com/v1.0/me/chats?\$expand=lastMessagePreview&\$select=id,chatType,topic,lastMessagePreview&\$top=100"

Filter to chats where lastMessagePreview.createdDateTime >= OLDEST_ISO OR lastMessagePreview is null (active but no preview).

Types to scan — priority order:

Type	Label	Priority
`oneOnOne`	1:1 DM	HIGH — always scan
`group`	Group chat	MEDIUM — scan if active
`meeting`	Meeting chat	MEDIUM — scan for action items

Build CHATS[]:

{
  "chat_id": "...",
  "chat_type": "oneOnOne/group/meeting",
  "topic": "...",
  "last_activity_iso": "..."
}

For 1:1 chats, fetch participant display name:

curl -s -H "Authorization: Bearer $ACCESS_TOKEN" \
  "https://graph.microsoft.com/v1.0/chats/$CHAT_ID/members?\$select=displayName,userId"

Extract the participant who is NOT me → set as chat_display_name.

3c — Planner Tasks (assigned to me)

curl -s -H "Authorization: Bearer $ACCESS_TOKEN" \
  "https://graph.microsoft.com/v1.0/me/planner/tasks?\$select=id,title,planId,dueDateTime,createdDateTime,createdBy,assignments&\$top=50"

Filter: completedDateTime == null (open tasks). Filter: assigned to MY_USER_ID.

Build PLANNER_ASSIGNED[] for Step 5 classification.

3d — Planner Tasks (created by me, assigned to others — Mode B)

From the same tasks endpoint result, filter:

createdBy.user.id == MY_USER_ID
Assigned to someone other than me
completedDateTime == null

Build PLANNER_DELEGATED[] for Mode B.

Print:

📊 Teams areas discovered:
   Teams    : [N] teams · [M] channels
   Chats    : [X] 1:1 DMs · [Y] group · [Z] meeting
   Planner  : [P] assigned to me · [Q] delegated by me (open)

STEP 4 — SCAN MESSAGES

Print: 📥 Scanning messages... (this may take 15–30s)

Rate limit awareness: Graph throttles at ~120 requests/10s for Chat messages. Insert a 500ms gap (sleep 0.5) between consecutive chat message fetches.

4a — Channel Messages (Mode A — mentions only)

For each channel in CHANNELS[]:

curl -s -H "Authorization: Bearer $ACCESS_TOKEN" \
  "https://graph.microsoft.com/v1.0/teams/$TEAM_ID/channels/$CHANNEL_ID/messages?\$filter=createdDateTime%20ge%20$OLDEST_ISO&\$top=50&\$select=id,from,createdDateTime,body,mentions,messageType,webUrl,replyToId,lastModifiedDateTime"

For each message:

Skip if messageType != "message" (system events, call records, etc.)
Check mentions[] array: if any entry has mentioned.user.id == MY_USER_ID → INBOX CANDIDATE
Check if message is a reply (replyToId exists): fetch root message, check if I sent the root → INBOX CANDIDATE (reply to my thread)
Check if I am from.user.id AND the message has no reply from others in the time window → FOLLOWUP CANDIDATE (I spoke, no one replied)

For inbox candidates that are thread roots, fetch replies to see if I've already responded:

curl -s -H "Authorization: Bearer $ACCESS_TOKEN" \
  "https://graph.microsoft.com/v1.0/teams/$TEAM_ID/channels/$CHANNEL_ID/messages/$MESSAGE_ID/replies?\$top=20&\$select=id,from,createdDateTime"

If I've already replied after the mention → skip (not an open inbox item).

Build CHANNEL_INBOX[] and CHANNEL_FOLLOWUP[].

4b — Chat Messages (Mode A + B — all messages)

For each chat in CHATS[]:

curl -s -H "Authorization: Bearer $ACCESS_TOKEN" \
  "https://graph.microsoft.com/v1.0/chats/$CHAT_ID/messages?\$filter=createdDateTime%20ge%20$OLDEST_ISO&\$top=100&\$select=id,from,createdDateTime,body,mentions,messageType,webUrl,replyToId"

Filter: messageType == "message" only.

1:1 DMs:

Messages FROM the other person → always INBOX CANDIDATE (they're talking to me)
Check: did I reply after their last message? If no → confirmed inbox item
Messages FROM me with no response from them → FOLLOWUP CANDIDATE

Group/Meeting chats:

Messages with MY_USER_ID in mentions[] → INBOX CANDIDATE
Messages from me with no responses → FOLLOWUP CANDIDATE
Meeting chats: also scan for patterns like "action item", "AI:", "TODO:", "@name will", "by [date]"
Meeting chats: scan for MY_DISPLAY_NAME substring in plain text (e.g. if running user is "Priya" and text says "Priya will handle the API redesign") — not all meeting summaries use @mentions
Adaptive Card messages from the Approvals app: body contains "approval", "approve", "pending your review" → always INBOX CANDIDATE regardless of mention status
Loop components / collaborative notes in chat: treat as background context only, not inbox items
System messages (messageType != "message"): skip entirely — these are call-started, member-added, etc. events

Build CHAT_INBOX[] and CHAT_FOLLOWUP[].

Print progress: ✓ Scanned [N]/[TOTAL] areas... (every 20 areas)

STEP 5 — CLASSIFY ITEMS

Merge:

ALL_INBOX = CHANNEL_INBOX[] + CHAT_INBOX[] + PLANNER_ASSIGNED[]
ALL_FOLLOWUP = CHANNEL_FOLLOWUP[] + CHAT_FOLLOWUP[] + PLANNER_DELEGATED[]

Mode A — Inbox Classification

For each inbox item, assign ACTION_TYPE:

`ACTION_TYPE`	Detection Signals
`APPROVAL`	"can you approve", "approve kar do", "LGTM?", "sign off", "confirm this", "give green light", "manjoor karo"
`DECISION`	Direct question ending in `?`, "what do you think", "kya lagta hai", "your call", "decide kar lo", "aap batao"
`REPLY_NEEDED`	1:1 DM from other person with no reply from me in time window
`MENTION_UNRESPONDED`	@mention in channel/group with no reply from me
`BLOCKER`	"blocked", "stuck", "ruk gaya", "aage nahi badh pa raha", "waiting on you", "need you to unblock"
`REVIEW_REQUEST`	"please review", "review kar lo", "check this", "feedback chahiye", "PR ready", "dekh lo"
`TASK_ASSIGNED`	Planner task assigned to me (from 3c)
`MEETING_ACTION`	Meeting chat message matching "action item:", "AI:", "@{MY_NAME} will", "you'll handle"

Extract for each item:

sender_name — display name of who sent it
source_message — first 200 chars of message body (strip HTML: remove <at>, , etc.)
action_summary — 1–2 sentence plain English: what is needed from me
platform_area — "{team_name} / #{channel_name}" or "1:1 with {name}" or "Group: {topic}"
source_url — webUrl from API response (direct Teams deep link)
received_at_unix — createdDateTime as Unix timestamp

Mode B — Follow-up Classification

For each follow-up item, assign FOLLOWUP_TYPE:

`FOLLOWUP_TYPE`	Detection Signals
`DELEGATED_TASK`	I asked: "can you do", "please handle", "kar dena", "manage kar lo", "you take this"
`AWAITING_REPLY`	I asked a question, no response received
`PENDING_DELIVERY`	I asked for a file/doc/output: "share the", "bhej dena", "send me", "jab ready ho tab"
`PLANNER_DELEGATED`	Planner task I created and assigned to others (from 3d)
`DEADLINE_AT_RISK`	Planner task with `dueDateTime` within 24h and assigned to others

Extract for each item:

assignee_name — who I delegated to
original_ask — what I asked (first 150 chars)
asked_at_unix — when I sent the original message
days_waiting — (now - asked_at_unix) / 86400

STEP 6 — SCORE AND PRIORITISE

Score each item 0–100:

Base score

Factor	Points
1:1 DM	+35
APPROVAL request	+28
BLOCKER type	+25
DECISION request	+22
MEETING_ACTION	+20
@mention in channel	+20
REVIEW_REQUEST	+18
TASK_ASSIGNED (Planner)	+15
Group chat	+12
Meeting chat	+12
DELEGATED_TASK follow-up	+15
DEADLINE_AT_RISK follow-up	+25
AWAITING_REPLY follow-up	+12

Role keyword boost

Matches in item content	Boost
3+ `ROLE_KEYWORDS[]`	+20
2 keywords	+15
1 keyword	+10
0 keywords	0

Age modifier

Message age	Modifier
< 2 hours	+20
2–8 hours	+10
8–24 hours	0
> 24 hours	−10
> 72 hours	−20

Recency of activity (for updated items)

Last activity	Modifier
Updated item (from dedupe)	+10

Priority buckets

Score	Priority	Label
75+	P1	🔴 URGENT — act today
50–74	P2	🟡 IMPORTANT — act this week
25–49	P3	🟢 LOW — act when possible
< 25	P4	⚪ NOISE — skip

Drop all P4 items. Do not create tasks for them.

Sort remaining items: P1 first, then P2, then P3. Within each bucket: sort descending by score.

Print: ⚡ Classified: [P1 count] urgent · [P2 count] important · [P3 count] low · [P4 count] noise (dropped)

STEP 7 — DEDUPE AGAINST STATE.JSON

For each scored item, generate stable SOURCE_URL:

Channel message: use webUrl from API response (e.g. https://teams.microsoft.com/l/message/...)
Chat message: use webUrl from API response
Planner task: planner:{task-id} (no deep link available from API)
If webUrl is null/empty: construct from IDs → teams:{team-id}:{channel-id}:{message-id}

Dedupe logic:

for each item where SOURCE_URL exists in STATE.seen_messages:
  stored = STATE.seen_messages[SOURCE_URL]

  if stored.status == "done":
    → SKIP entirely

  compute ACTIVITY_HASH = sha256-first-8(sender_name + source_message + platform_area)

  if ACTIVITY_HASH == stored.activity_hash:
    → SKIP (no new activity on this item)
  else:
    → KEEP as UPDATE (new activity on known item)
    → bump score by +10
    → update stored.last_activity_seen = now
    → update stored.activity_hash = ACTIVITY_HASH

for each item NOT in STATE.seen_messages:
  → KEEP as NEW

Use Bash to compute activity hash:

echo -n "${sender_name}${source_message}${platform_area}" | shasum -a 256 | cut -c1-8

Self-heal: For each item where STATE.seen_messages[SOURCE_URL].todo_task_id exists, verify the To Do task still exists:

curl -s -o /dev/null -w "%{http_code}" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  "https://graph.microsoft.com/v1.0/me/todo/lists/$TODO_LIST_ID/tasks/$STORED_TASK_ID"

If response is 404 (task deleted/completed externally) → remove from state, treat item as NEW. Increment STATE.self_heal_count.

Print: 🔄 Dedupe: [NEW_COUNT] new · [UPDATED_COUNT] updated · [SKIPPED_COUNT] unchanged · [SELFHEAL_COUNT] self-healed

STEP 8 — VALIDATE + CREATE TO DO TASKS

Hard validation gate

Each item MUST have ALL of the following before a task is created. If any field is missing or empty → SKIP the item and print a warning.

Required fields:

SOURCE_URL — non-empty string
sender_name — non-empty string
action_summary — non-empty, min 10 characters
priority — one of P1/P2/P3
platform_area — non-empty string
action_type — valid ACTION_TYPE or FOLLOWUP_TYPE value

Task title format

[P1] 💬 Reply to {sender_name} — {topic_slug}         (for REPLY_NEEDED / MENTION_UNRESPONDED)
[P1] ✅ Approve: {topic_slug} — from {sender_name}     (for APPROVAL)
[P1] 🚧 Unblock {sender_name}: {topic_slug}            (for BLOCKER)
[P2] 🔍 Review: {topic_slug} — {sender_name}           (for REVIEW_REQUEST)
[P2] 💭 Decide: {topic_slug}                           (for DECISION)
[P2] 📋 Planner: {task_title}                          (for TASK_ASSIGNED)
[P2] 📅 Meeting action: {topic_slug}                   (for MEETING_ACTION)
[P3] 📤 Follow up with {assignee_name} re: {topic_slug} (for DELEGATED_TASK)
[P3] ⏰ Deadline risk: {topic_slug} — {assignee_name}  (for DEADLINE_AT_RISK)

topic_slug = first 60 chars of message/task title, stripped of HTML. Strip to max 120 chars total for the title.

Task body format

For Inbox items (Mode A):

📍 Area: {platform_area}
🗓 Received: {relative_time} (e.g. "2 hours ago")
👤 From: {sender_name}
📝 What's needed: {action_summary}
🔗 Source: {SOURCE_URL}

---
pickle-teams · {ISO_TIMESTAMP}

For Follow-up items (Mode B):

📍 Area: {platform_area}
📤 You asked: {original_ask}
👤 Delegated to: {assignee_name}
⏳ Asked: {relative_days_waiting} ago, no update since
🔗 Source: {SOURCE_URL}

---
pickle-teams · {ISO_TIMESTAMP}

Create task via API

curl -s -X POST \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d "{
    \"title\": \"$TASK_TITLE\",
    \"body\": {
      \"contentType\": \"text\",
      \"content\": \"$TASK_BODY\"
    },
    \"importance\": \"$IMPORTANCE\",
    \"dueDateTime\": {
      \"dateTime\": \"$DUE_ISO\",
      \"timeZone\": \"UTC\"
    }
  }" \
  "https://graph.microsoft.com/v1.0/me/todo/lists/$TODO_LIST_ID/tasks"

Importance mapping: P1 → "high", P2 → "normal", P3 → "low"

Due date mapping: P1 → today, P2 → today + 2 days, P3 → today + 5 days

After successful creation, extract returned task_id and store in state.

Print for each task: ✓ Created: "$TASK_TITLE"

STEP 9 — FOLLOWUP MODE (only if FOLLOWUP_MODE = true)

Show follow-up candidates one by one. For each item in ALL_FOLLOWUP that passed dedupe and validation:

────────────────────────────────────────
📤 Follow-up #{N} of {TOTAL}
   To: {assignee_name}
   Area: {platform_area}
   You asked ({days_waiting} days ago): "{original_ask}"
   Suggested message: "{follow_up_message}"

   Confirm: [y] Send  [s] Skip  [e] Edit message  [a] Send all remaining
────────────────────────────────────────

Wait for explicit user confirmation on each. Never auto-send without y or a.

Follow-up message templates (language-matched to original):

English:

Hey {assignee_name}, following up on "{original_ask_short}" — any update? 🙂

Hindi/Hinglish (detect from original ask language):

Hey {assignee_name}, "{original_ask_short}" ke baare mein follow-up kar raha tha — koi update?

Sending to Teams chat

curl -s -X POST \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d "{\"body\": {\"contentType\": \"text\", \"content\": \"$FOLLOWUP_MESSAGE\"}}" \
  "https://graph.microsoft.com/v1.0/chats/$CHAT_ID/messages"

Sending as channel thread reply

curl -s -X POST \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d "{\"body\": {\"contentType\": \"text\", \"content\": \"$FOLLOWUP_MESSAGE\"}}" \
  "https://graph.microsoft.com/v1.0/teams/$TEAM_ID/channels/$CHANNEL_ID/messages/$ROOT_MESSAGE_ID/replies"

Track sent follow-ups in STATE.followups_sent[].

STEP 10 — SAVE STATE + PRINT SUMMARY

Build updated state JSON

{
  "version": 2,
  "last_run": CURRENT_UNIX,
  "seen_messages": {
    "{SOURCE_URL}": {
      "first_seen": UNIX,
      "last_activity_seen": UNIX,
      "activity_hash": "8-char-hex",
      "todo_task_id": "microsoft-todo-task-id",
      "todo_task_title": "Task title...",
      "status": "open",
      "priority": "P1",
      "action_type": "APPROVAL",
      "sender": "Display Name",
      "platform_area": "Team / #channel or 1:1 with Name"
    }
  },
  "todo_list_id": "list-id-string",
  "self_heal_count": 0,
  "followups_sent": []
}

Write:

cat > ~/.claude/skills/pickle-teams/state.json << 'STATEEOF'
{STATE_JSON}
STATEEOF

Print final summary

════════════════════════════════════════
  🥒 pickle-teams — Done
════════════════════════════════════════

📥 INBOX (needs your action)
  🔴 P1 Urgent    : [N] items
  🟡 P2 Important : [N] items
  🟢 P3 Low       : [N] items
  ⚪ P4 Noise      : [N] dropped

📤 FOLLOW-UP (you delegated)
  [N] items tracked [+ X sent if FOLLOWUP_MODE]

📊 Coverage
  Teams scanned   : [N] teams · [M] channels
  Chats scanned   : [X] 1:1 DMs · [Y] groups · [Z] meetings
  Messages read   : [TOTAL_COUNT]
  Planner tasks   : [P] assigned to me · [Q] delegated by me
  Tasks created   : [N] (To Do: "Task Board - By Pickle")
  Deduped/skipped : [N] unchanged · [N] updated
  Self-healed     : [N] externally completed

🔗 Open To Do: https://to-do.microsoft.com/tasks/inbox

⏱ Run time: ~[X]s

ERROR HANDLING

Error	Action
`401 Unauthorized`	Token expired. Print refresh instructions. STOP.
`403 Forbidden`	Missing Graph permission. List required scopes. STOP.
`429 Too Many Requests`	Pause 30s (`sleep 30`), retry once. If still 429, skip that area and continue.
`404 Not Found` on a resource	Skip that team/channel/chat. Continue.
Empty `value` array	Skip, no messages in that area. Continue.
`teams-config.json` malformed	Print: "Config file is invalid JSON. Expected: {access_token: '...'}". STOP.
Bash `curl` not found	Print: "curl is required. Install via: brew install curl". STOP.
Channel scan fails with 403	Some channels require member/owner. Skip and note in summary.
Message body is null	`body.content` can be null for system messages or deleted messages. Always null-check before parsing. Skip if null.
Adaptive Card messages	`body.contentType == "html"` but content is `<attachment...>`. Strip to extract any plain text. Flag as "[Adaptive Card — open in Teams to view full content]"
Deleted message	`deletedDateTime` non-null. Skip entirely — do not treat as inbox item.
Guest user @mention	Guest user IDs in `mentions[].mentioned.user.id` may not match `MY_USER_ID` pattern. Also check `mentions[].mentioned.user.displayName` against `MY_DISPLAY_NAME` as fallback.
Message from bot/app	`from.application` non-null (bot/app sender). Skip for inbox scoring but retain if it's an approval request (e.g. Approvals app) — detect by checking message body for "approve", "review", "action required".
Private channel 403	Private channels require explicit membership. Log as "skipped (private — no access)" in summary. Never block the run.
Federated/external user	`from.user.tenantId` differs from your tenant. Still valid sender — treat as normal inbox item.
Meeting chat with no participants	Meeting chats created from calendar invites can have 0 members in `/chats/{id}/members`. Skip participant name fetch if empty, label as "Meeting chat: {topic}".
Pagination	All `curl` calls returning `value[]` MUST follow `@odata.nextLink` for pagination. Never assume first page is complete for DMs or active channels.

APPENDIX A — TOKEN AUTO-REFRESH

If token_expiry in config is within 300 seconds of now AND refresh_token + client_id are present, attempt refresh before scanning.

HARD RULES — never wipe a working credential on a failed refresh:

Parse the response JSON. Only proceed if it contains a non-empty access_token field.
Write to a .tmp sibling file with chmod 600, then mv over the live config (atomic replace).
Never log/echo $REFRESH_TOKEN, $ACCESS_TOKEN, or the full response on stderr/stdout.
If the refresh response is anything other than a valid token JSON (HTTP error, HTML error page, partial body) → KEEP the existing config untouched, print "token refresh failed — re-run with manual token". Do NOT overwrite.

REFRESH_RESPONSE=$(curl -s -X POST \
  "https://login.microsoftonline.com/common/oauth2/v2.0/token" \
  -H "Content-Type: application/x-www-form-urlencoded" \
  --data-urlencode "grant_type=refresh_token" \
  --data-urlencode "client_id=$CLIENT_ID" \
  --data-urlencode "refresh_token=$REFRESH_TOKEN" \
  --data-urlencode "scope=Chat.Read ChannelMessage.Read.All Team.ReadBasic.All User.Read Tasks.ReadWrite offline_access")

# Validate: must be JSON, must contain non-empty access_token
NEW_ACCESS=$(printf '%s' "$REFRESH_RESPONSE" | python3 -c 'import sys,json
try:
  d=json.load(sys.stdin)
  t=d.get("access_token","")
  print(t if t else "")
except Exception:
  print("")' 2>/dev/null)

if [ -n "$NEW_ACCESS" ]; then
  # Atomic write — never truncate the live file in place
  umask 077
  TMP="$HOME/.claude/pickle/teams-config.json.tmp.$$"
  printf '%s' "$REFRESH_RESPONSE" | python3 -c 'import sys,json,os
d=json.load(sys.stdin)
d["token_expiry"]=int(__import__("time").time())+int(d.get("expires_in",3600))-60
print(json.dumps(d, indent=2))' > "$TMP"
  chmod 600 "$TMP"
  mv "$TMP" "$HOME/.claude/pickle/teams-config.json"
  echo "🔄 Token refreshed automatically"
else
  echo "⚠️  Token refresh failed — keeping existing config. Re-authenticate via Azure AD device flow if needed (ask Pickle in chat: \"Pickle set me up for Teams\")."
  # DO NOT modify teams-config.json. Either continue with existing token or STOP — never wipe credentials.
fi

APPENDIX B — TEAMS HTML BODY PARSING

Teams message body.content is HTML. When extracting plain text for action_summary and source_message, strip:

<at id="...">name</at> → replace with @name
... → extract text content
  → newline
, , , <strike> → strip tags, keep text
<a href="...">text</a> → keep text only
All other HTML tags → strip, keep text

Use Bash:

echo "$HTML_CONTENT" | sed 's/<at[^>]*>/@ /g' | sed 's/<\/at>//g' | sed 's/<[^>]*>//g' | sed 's/&amp;/\&/g' | sed 's/&lt;/</g' | sed 's/&gt;/>/g' | sed 's/&nbsp;/ /g'

pickle-teams

More from this repository

More from this repository

pickle-teams 🥒

Pre-flight: if no Teams tool is available

STEP 0 — PARSE ARGUMENTS

STEP 0.5 — LOAD USER PROFILE

STEP 1 — LOAD AUTH TOKEN

If config file is missing or access_token is empty — print setup guide and STOP

STEP 2 — VALIDATE AUTH + GET MY PROFILE

STEP 2.5 — LOAD STATE + INIT TO DO LIST

Load state.json

Find or create To Do list

Fetch existing Pickle tasks (for dedupe)

STEP 3 — DISCOVER ALL TEAMS AREAS

3a — Joined Teams

3b — Chats (DMs + Group + Meeting)

3c — Planner Tasks (assigned to me)

3d — Planner Tasks (created by me, assigned to others — Mode B)

STEP 4 — SCAN MESSAGES

4a — Channel Messages (Mode A — mentions only)

4b — Chat Messages (Mode A + B — all messages)

STEP 5 — CLASSIFY ITEMS

Mode A — Inbox Classification

Mode B — Follow-up Classification

STEP 6 — SCORE AND PRIORITISE

Base score

Role keyword boost

Age modifier

Recency of activity (for updated items)

Priority buckets

STEP 7 — DEDUPE AGAINST STATE.JSON

STEP 8 — VALIDATE + CREATE TO DO TASKS

Hard validation gate

Task title format

Task body format

Create task via API

STEP 9 — FOLLOWUP MODE (only if FOLLOWUP_MODE = true)

Sending to Teams chat

Sending as channel thread reply

STEP 10 — SAVE STATE + PRINT SUMMARY

Build updated state JSON

Print final summary

ERROR HANDLING

APPENDIX A — TOKEN AUTO-REFRESH

APPENDIX B — TEAMS HTML BODY PARSING

APPENDIX C — REMOVED

pickle-teams 🥒

Pre-flight: if no Teams tool is available

STEP 0 — PARSE ARGUMENTS

STEP 0.5 — LOAD USER PROFILE

STEP 1 — LOAD AUTH TOKEN

If config file is missing or access_token is empty — print setup guide and STOP

STEP 2 — VALIDATE AUTH + GET MY PROFILE

STEP 2.5 — LOAD STATE + INIT TO DO LIST

Load state.json

Find or create To Do list

Fetch existing Pickle tasks (for dedupe)

STEP 3 — DISCOVER ALL TEAMS AREAS

3a — Joined Teams

3b — Chats (DMs + Group + Meeting)

3c — Planner Tasks (assigned to me)

3d — Planner Tasks (created by me, assigned to others — Mode B)

STEP 4 — SCAN MESSAGES

4a — Channel Messages (Mode A — mentions only)

4b — Chat Messages (Mode A + B — all messages)

STEP 5 — CLASSIFY ITEMS

Mode A — Inbox Classification

Mode B — Follow-up Classification

STEP 6 — SCORE AND PRIORITISE

Base score

Role keyword boost

Age modifier

Recency of activity (for updated items)

Priority buckets

STEP 7 — DEDUPE AGAINST STATE.JSON

STEP 8 — VALIDATE + CREATE TO DO TASKS

Hard validation gate

Task title format

Task body format

If config file is missing or `access_token` is empty — print setup guide and STOP

If config file is missing or `access_token` is empty — print setup guide and STOP