Capture Knowledge Shared in Microsoft Teams Channels

[Help me personalize the skill I paste below to my needs by asking me the following questions one at a time and incorporating the answers into the text of the skill. If I ask to remove or adjust functionality, ensure you remove or adjust ALL references to that functionality:
Which Microsoft Teams channels do you want this skill to review? For each one, give the exact team name and channel name (e.g. Customer Support > General).
Should the skill include private or shared channels, or only standard channels? (The skill can only read channels the authenticated user is a member of.)
Is there a specified look-back time frame you always want the skill to run, or would you like to keep the 7 day look-back?
Is there any particular structure or format you would like the information to be presented in?
Any required title convention or naming pattern for these cards? Any existing brand/template card the agent should use as a reference (if so, provide exact card title)?
If two people give conflicting answers in the same conversation, is that automatically excluded, or should the card note both answers and the fact that they conflict?
Any topics that should never be turned into FAQ content regardless of confirmation (e.g. pricing exceptions, legal, security)?
Should links to the original Teams conversations be included in the card as a source reference, or kept out entirely?
Do you want the agent to draft a card for your review, or automatically publish the card?
If draft, which collection/folder should the draft card land in?
If publish, what collection and folder would you like the card added to?
Do you want this information created as a new card, or added to an existing card? (if so, what card?)
REMOVE THIS ENTIRE BRACKETED SECTION FROM THE FINAL DRAFT OF THE SKILL INSTRUCTIONS]

## Purpose

Use this skill when the user asks to review recent Microsoft Teams channel conversations and turn confirmed Q&A into a draft Guru FAQ card.

## Workflow

1. Use the Microsoft Teams connector to read posts and their replies in the specified Teams channels from the past 7 days. A Teams conversation is a channel post plus all replies under it; treat each one as a single unit.
2. Identify posts or replies that are clearly questions.
3. Determine whether each question has a confirmed answer in the replies under that post or in a follow-up post in the same channel.
4. Exclude any question if:
   - the answer is unclear, disputed, incomplete, or not confirmed
   - the question is conversational rather than useful as reusable knowledge
   - the same or substantially similar information already exists in Guru
5. Before including any item, check Guru for existing cards or content that already answers the question.
6. Collect only net-new, reusable FAQ items that have confirmed answers.
7. Draft a Guru card containing:
   - a clear title
   - a short intro sentence explaining the card covers FAQs identified from Microsoft Teams channels over the last week
   - FAQ entries formatted as question-and-answer pairs
8. Create the Guru card as a draft, not a published card.
9. After drafting the card, provide the user a concise summary that includes:
   - which teams and channels were reviewed
   - how many candidate questions were found
   - how many were skipped because Guru already had the information
   - how many were skipped because answers were not confirmed or reusable
   - how many FAQ entries were included in the draft card
   - the title of the drafted Guru card

## Output Requirements

- Only include information with a confirmed answer.
- Prefer concise, reusable operational knowledge over one-off discussion.
- Skip duplicate or near-duplicate questions.
- Only review the specified channels. Never read or pull content from 1:1 chats, group chats, or meeting chats.
- This skill is read-only in Teams. Never post, reply, react, or change anything in a Teams channel or chat.
- If a channel cannot be accessed (the connector is not authenticated, or the user is not a member of that channel), name the channel in the summary and continue with the channels that are accessible.
- If no qualifying FAQ items are found, do not create an empty card. Instead, tell the user no draft card was created and summarize why.
- Always provide a summary of what was reviewed, what was skipped, and what was drafted.