[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71873D2KYYJDX6ZWZFN05E6":3,"skill-same:01M71873D2KYYJDX6ZWZFN05E6":60},{"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":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M71873D2KYYJDX6ZWZFN05E6","teams",null,"Write, sign and post Teams chat and channel messages for the human. Use \u002Fteams before you draft, post or edit a Teams message.","microsoft\u002Fagentic-loops","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M7187043GF7ZMW7DWF6Y0TQW",5,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagentic-loops\u002Fblob\u002Fmaster\u002Fskills\u002Fteams\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31],"draft","chat","post","message","human","for","sign","messages","write","edit","use","channel","you","2026-11-10 10:12:30",false,"---\nname: teams\ndescription: Write, sign and post Teams chat and channel messages for the human. Use \u002Fteams before you draft, post or edit a Teams message.\n---\n\n# \u002Fteams\n\nObey these rules for the remainder of this session. The Writing rules of `\u002Fyagni` also apply.\n\n## Write\n\n- Put the main point or the request in the first line.\n- Pay attention to formatting:\n  - Ensure the message is not one flat blob of ugly text.\n  - Write about one topic in each message. For details, link to a document.\n  - Use lists. Do not use headings or tables.\n- Use a diagram only if it is 60 columns wide or less. If it is wider, link to it.\n- @mention a person only if that person must do an action, or if the human tells you to cc that person.\n\n## Sign\n\nEnd each message with this block. Use the persona name, for example `JARVIS (on behalf of Mr. Das)`. Do not write other signature or attribution text.\n\n```text\nThanks!\n\u003Cpersona> (on behalf of Mr. Das)\n\ncc \u003C@mentions>\n```\n\nIf there is no cc, do not write the cc line.\n\n## Post\n\n1. Show the human the exact final text of each message, with the signature, the destination and the people. Post only after the human approves.\n2. Post each message one time. To change a posted message, edit it. Do not post it again.\n3. Do not put `:` in a chat title. Teams rejects it.\n4. After you post or edit, read the message again and confirm the content. Give the human a link to each message.\n","# \u002Fteams\n\nObey these rules for the remainder of this session. The Writing rules of `\u002Fyagni` also apply.\n\n## Write\n\n- Put the main point or the request in the first line.\n- Pay attention to formatting:\n  - Ensure the message is not one flat blob of ugly text.\n  - Write about one topic in each message. For details, link to a document.\n  - Use lists. Do not use headings or tables.\n- Use a diagram only if it is 60 columns wide or less. If it is wider, link to it.\n- @mention a person only if that person must do an action, or if the human tells you to cc that person.\n\n## Sign\n\nEnd each message with this block. Use the persona name, for example `JARVIS (on behalf of Mr. Das)`. Do not write other signature or attribution text.\n\n```text\nThanks!\n\u003Cpersona> (on behalf of Mr. Das)\n\ncc \u003C@mentions>\n```\n\nIf there is no cc, do not write the cc line.\n\n## Post\n\n1. Show the human the exact final text of each message, with the signature, the destination and the people. Post only after the human approves.\n2. Post each message one time. To change a posted message, edit it. Do not post it again.\n3. Do not put `:` in a chat title. Teams rejects it.\n4. After you post or edit, read the message again and confirm the content. Give the human a link to each message.\n",{"name":5,"description":7},"master","90d2da5ee908f1bfbeeb2d40e84b4c885cd286ce","skills\u002Fteams",1,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagentic-loops","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-10 05:12:29",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add microsoft\u002Fagentic-loops --skill teams",{"tool":52,"command":53},"bunx","bunx skills add microsoft\u002Fagentic-loops --skill teams",{"tool":55,"command":56},"pnpm","pnpm dlx skills add microsoft\u002Fagentic-loops --skill teams","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagentic-loops\u002Fblob\u002Fmaster\u002Fskills\u002Fteams\u002FSKILL.md",true,[],[61,82],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":72,"publishedAt":32},"01M71874N3GHWHNQ8TSD2V16YM","yagni","Keep design and code simple, and communicate clearly in documents, comments, messages and diagrams.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagentic-loops\u002Fblob\u002Fmaster\u002Fskills\u002Fyagni\u002FSKILL.md",[67],{"categoryNo":68,"categoryName":69,"taxonomyType":70,"taxonomyTypeDesc":71},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",[63,73,74,75,76,77,78,26,79,80,81],"code","comments","keep","documents","communicate","design","communicate clearly","simple","diagrams",{"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":32},"01M71871RTFJBKFVJ7RH30WMCH","bro","Re-explain the previous assistant message in a much simpler way, for when the reply made you go 'bro what'. Use \u002Fbro to get a simpler version of the last answer in Plain Language + Chicago Manual of Style, with diagrams where they help.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagentic-loops\u002Fblob\u002Fmaster\u002Fskills\u002Fbro\u002FSKILL.md",[],[84,89,90,91,92,93,22,94,95,96,97,31,98,29,99,100,101,24,102,81],"style","plain","assistant","go","help","with","last","explain","version","when","manual","re","answer","get"]