[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79G487F66R7KCE92GAC2RH9":3,"skill-same:01M79G487F66R7KCE92GAC2RH9":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M79G487F66R7KCE92GAC2RH9","teams-reply-drafting",null,"Draft Microsoft Teams replies from available context. Use when the user wants help finding messages that likely need a response and preparing reply drafts.","zfifteen\u002Fskills-catalog","zfifteen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F221906715?v=4","01M79CQFXDZM5J5CJTCECPFA66","Dionisio Alberto Lopez III","01M79CQFY4C62PN8A2T5KDAHGA",1,"MIT","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fteams-reply-drafting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: teams-reply-drafting\ndescription: Draft Microsoft Teams replies from available context. Use when the user wants help finding messages that likely need a response and preparing reply drafts.\n---\n\n# Teams Reply Drafting\n\nUse this skill to identify Teams messages that likely need a reply and produce draft responses grounded in the available conversation context.\n\n## Related Skills\n\n| Workflow | Skill |\n| --- | --- |\n| Refine or send the final Teams text | [..\u002Fteams-messages\u002FSKILL.md](..\u002Fteams-messages\u002FSKILL.md) |\n| Create Microsoft Planner tasks instead of replying in Teams | [..\u002Fteams-planner-task-management\u002FSKILL.md](..\u002Fteams-planner-task-management\u002FSKILL.md) |\n\n## Start Here\n\n- If the user provided channels, threads, chats, people, or a time window, use that scope instead of the default fallback.\n- If no source scope was provided, treat this as best-effort reply drafting from available Teams signals rather than an exact \"messages needing reply\" detector.\n- Use draft replies when the user asked for drafting or review, and send when the requested action is to post or reply now.\n\n## Workflow\n\n1. If the user gave explicit scope, use the cheapest matching path first:\n   - specific message or thread path: `fetch`, then `reply_to_message` only if the user wants to send\n   - named channel: `resolve_team`, `resolve_channel`, then `list_channel_messages`\n   - named chat or DM: `resolve_chat`, then `list_chat_messages`\n2. If no explicit scope was provided, start with:\n   - `list_chats(unread_only=True)` for unread direct conversations and group chats\n   - `list_recent_threads` for recent channel or chat activity\n3. Expand only the conversations needed to answer accurately:\n   - unread chats first\n   - then recent messages containing direct questions or clear asks\n   - then recent mentions detected from message-history reads\n4. To detect recent mentions, get the caller profile and match `TeamsMessageResult.mentions` against the caller's user ID from direct message-history reads. Do not rely on Teams search hits for mention detection.\n5. If the context is incomplete, write the smallest useful clarifying reply instead of guessing.\n6. If a message contains a follow-up but no reply is needed, say that directly. If the user wants it tracked, route the follow-up to the Planner skill instead of drafting a performative Teams reply.\n\n## Drafting Rules\n\n- Answer the question first, then add clarification or next steps only when the context supports it.\n- Keep in-thread replies short unless the thread clearly requires a longer answer.\n- Preserve thread-specific facts, dates, links, and owners.\n- If there are multiple plausible reply targets, stop and ask which conversation the user means before drafting anything send-ready.\n\n## Formatting\n\nFormat multiple drafts as:\n\n```md\n*Teams Reply Drafts — \u003Cscope>*\n\n*\u003Cchat \u002F channel \u002F thread info>*\nDraft:\n\u003Cdraft text>\n\n*\u003Cchat \u002F channel \u002F thread info>*\nDraft:\n\u003Cdraft text>\n```\n\n- Keep each item minimal: a short header plus the draft text.\n- If the user asked for a single reply, return only that item.\n- If nothing likely needing a reply is found, say so directly and explain the scope checked.\n","# Teams Reply Drafting\n\nUse this skill to identify Teams messages that likely need a reply and produce draft responses grounded in the available conversation context.\n\n## Related Skills\n\n| Workflow | Skill |\n| --- | --- |\n| Refine or send the final Teams text | [..\u002Fteams-messages\u002FSKILL.md](..\u002Fteams-messages\u002FSKILL.md) |\n| Create Microsoft Planner tasks instead of replying in Teams | [..\u002Fteams-planner-task-management\u002FSKILL.md](..\u002Fteams-planner-task-management\u002FSKILL.md) |\n\n## Start Here\n\n- If the user provided channels, threads, chats, people, or a time window, use that scope instead of the default fallback.\n- If no source scope was provided, treat this as best-effort reply drafting from available Teams signals rather than an exact \"messages needing reply\" detector.\n- Use draft replies when the user asked for drafting or review, and send when the requested action is to post or reply now.\n\n## Workflow\n\n1. If the user gave explicit scope, use the cheapest matching path first:\n   - specific message or thread path: `fetch`, then `reply_to_message` only if the user wants to send\n   - named channel: `resolve_team`, `resolve_channel`, then `list_channel_messages`\n   - named chat or DM: `resolve_chat`, then `list_chat_messages`\n2. If no explicit scope was provided, start with:\n   - `list_chats(unread_only=True)` for unread direct conversations and group chats\n   - `list_recent_threads` for recent channel or chat activity\n3. Expand only the conversations needed to answer accurately:\n   - unread chats first\n   - then recent messages containing direct questions or clear asks\n   - then recent mentions detected from message-history reads\n4. To detect recent mentions, get the caller profile and match `TeamsMessageResult.mentions` against the caller's user ID from direct message-history reads. Do not rely on Teams search hits for mention detection.\n5. If the context is incomplete, write the smallest useful clarifying reply instead of guessing.\n6. If a message contains a follow-up but no reply is needed, say that directly. If the user wants it tracked, route the follow-up to the Planner skill instead of drafting a performative Teams reply.\n\n## Drafting Rules\n\n- Answer the question first, then add clarification or next steps only when the context supports it.\n- Keep in-thread replies short unless the thread clearly requires a longer answer.\n- Preserve thread-specific facts, dates, links, and owners.\n- If there are multiple plausible reply targets, stop and ask which conversation the user means before drafting anything send-ready.\n\n## Formatting\n\nFormat multiple drafts as:\n\n```md\n*Teams Reply Drafts — \u003Cscope>*\n\n*\u003Cchat \u002F channel \u002F thread info>*\nDraft:\n\u003Cdraft text>\n\n*\u003Cchat \u002F channel \u002F thread info>*\nDraft:\n\u003Cdraft text>\n```\n\n- Keep each item minimal: a short header plus the draft text.\n- If the user asked for a single reply, return only that item.\n- If nothing likely needing a reply is found, say so directly and explain the scope checked.\n",{"name":5,"description":7},"main","d9535210da9af28aa76bca80de80355197e1b6d6","skills\u002Fteams-reply-drafting","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog","https:\u002F\u002Fgithub.com\u002Fzfifteen","I like to measure things.","2026-07-19 23:41:54",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add zfifteen\u002Fskills-catalog --skill teams-reply-drafting",{"tool":37,"command":38},"bunx","bunx skills add zfifteen\u002Fskills-catalog --skill teams-reply-drafting",{"tool":40,"command":41},"pnpm","pnpm dlx skills add zfifteen\u002Fskills-catalog --skill teams-reply-drafting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fteams-reply-drafting\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",375,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fteams-reply-drafting\u002Fagents\u002Fopenai.yaml",[52,59,66,73,82,89],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M79GXQ2PWPT2E4CJYHXVJ0YE","Zotero","Use Zotero Desktop from Codex to enable\u002Fprobe the local API, search a local Zotero library, list items\u002Fcollections\u002Ftags, export BibTeX, insert citation keys into LaTeX or Markdown drafts, read indexed full text when requested, and import BibTeX\u002FRIS records into Zotero through the connector server. Use when the user mentions Zotero, citations, references.bib, BibTeX export, local Zotero API, localhost:23119, or adding citations from a Zotero library.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fzotero\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M79GXN85NETKBE06865CWK6Z","zoom-apps-sdk","Use when using Apps SDK.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M79GXCYD7FGYS932J9N9RFFY","youtube","Obtain accurate, timestamped YouTube video transcripts (preferring manual captions over auto-generated) as the primary deliverable, then derive summaries, key claims, or notes from that transcript.  Use when the user provides a YouTube URL (or video ID) and wants the transcript, a faithful summary, key claims with attribution, timestamped notes, or \"what does this video actually say\".  The skill is transcript-first: never substitute metadata, title, description, or search snippets for the spoken content.  Triggers: \"youtube transcript\", \"get the transcript of this video\", \"summarize this youtube video\", \"what did they say in https:\u002F\u002Fyoutube.com\u002F...\", \"key claims from this talk\".","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79GX8EXHHYM566BKR7MS778","yeet","Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M79GX2HFJPX84NMRE5VBTYX9","x-post-creator","Create X-ready post threads and co-located story packages from the active conversation or referenced project material. Use when the user says turn this into an X-post, \u002Fx-post, make this into an X thread, or wants plain-language social posts with supporting images saved to docs\u002Fx-posts\u002F[story-name]\u002F.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fx-post-creator\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M79GWXQT4HBT6QME6QSBZJFA","x-api","Search, read, and write X posts through the local X API MCP server (the same backend used by the Codex x-api skill). Use for searching X\u002Fx.com, reading threads and replies, creating lists, staging\u002Fpublishing posts for @alltheputs, finding high-visibility reply targets for research outreach, ingesting public context, or any request that mentions \u002Fx-api or \"search X\".","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]