teams-intelligence

name	teams-intelligence
description	Use when the founder wants to configure Microsoft Teams channels/chats, extract actionable Teams intelligence, create a daily Teams digest, review Teams decisions and handoffs, or turn selected Teams context into task candidates for the daily operating workflow.
user-invocable	true

Teams Intelligence — Selected Channel Operating Digest

Purpose

Make Microsoft Teams useful inside the founder operating system without turning it into a noisy transcript dump.

The skill should read only the Teams teams, channels, chats, meeting recaps, exports, or pasted snippets the founder chooses. It extracts operational intelligence that should affect the day: decisions, asks, customer/account mentions, blockers, handoffs, risks, product feedback, competitor mentions, useful links, and task candidates.

Setup

Use /teams-setup when Teams is first connected or when the founder wants to change which Teams areas matter.

Capture:

• Teams connector status: connected / export-only / not connected
• selected teams, channels, chats, or meeting recap sources to review
• sources to ignore
• what each source is for
• review cadence
• priority keywords, accounts, competitors, products, and people
• escalation rules for urgent asks or customer risk
• posting boundary: no Teams posting or meeting changes without explicit approval

Write:

• data/teams/channel-map.md
• update Teams fields in data/setup-status.md
• append one line to data/ops.log

Required Paths

Read:

• data/setup-status.md
• data/connectors.md
• data/teams/channel-map.md
• data/tasks.md
• views/daily-briefing.md
• views/priority-plan.md
• data/ops.log

Write:

• data/teams/channel-map.md
• views/teams-digest.md
• data/teams/digests/{{DATE}}.md
• data/setup-status.md during setup
• append one line to data/ops.log

Tool Requirements

• Teams connector is preferred for selected team/channel/chat/recap reads.
• If the Teams connector is unavailable, use pasted threads, selected exports, or meeting recap notes.
• Read only selected sources from data/teams/channel-map.md.
• Posting to Teams or modifying meetings requires explicit approval.
• Do not use private chats or broad history unless explicitly included.

Daily Digest

Use /teams-digest daily, or let the morning briefing include it when Teams is configured.

Read:

• data/teams/channel-map.md
• accessible selected Teams messages, channels, chats, and meeting recaps since the last digest, if a Teams connector is available
• pasted Teams threads, exported channel snippets, or meeting recaps if no connector is available
• data/tasks.md
• views/daily-briefing.md
• views/priority-plan.md
• recent data/ops.log

Extract:

• decisions made
• direct asks of the founder or team
• task candidates
• blockers and risks
• customer, prospect, account, or partner mentions
• competitor or market mentions
• product feedback or repeated complaints
• meeting recap action items or unanswered follow-ups
• useful files or links to review
• threads that need a response

Write:

• views/teams-digest.md
• data/teams/digests/{{DATE}}.md
• append one line to data/ops.log

Output Standard

Keep the digest short enough to use in a morning briefing. Do not summarize every message.

Every item should answer:

• what happened
• why it matters
• who owns the next step, if known
• whether it should become a task
• source team/channel/chat/meeting reference

Boundaries

• Do not post to Teams without explicit approval.
• Do not modify meetings, chats, files, or tasks without explicit approval.
• Do not read private chats, DMs, or broad history unless the founder explicitly includes them.
• Do not store raw Teams transcripts unless the user asks.
• Do not silently add tasks from Teams; list task candidates and ask before mutating data/tasks.md.
• Do not create hidden passive memory or full Teams indexes.
• Prefer selected-channel intelligence over broad workspace surveillance.