[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71871RTFJBKFVJ7RH30WMCH":3,"skill-same:01M71871RTFJBKFVJ7RH30WMCH":66},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M71871RTFJBKFVJ7RH30WMCH","bro",null,"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.","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\u002Fbro\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"version","plain","assistant","go","help","style","message","with","last","explain","you","when","use","manual","re","answer","for","get","diagrams","2026-11-10 10:12:30",false,"---\nname: bro\ndescription: \"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.\"\nlicense: MIT\n---\n\n# \u002Fbro: say it simpler\n\nThe user typed `\u002Fbro`. Your last message was not clear to the user. It was too dense, had too much jargon, or was too formal.\n\n**Your task:** explain YOUR most recent assistant message again in a much simpler way.\n\n## Rules\n\n1. **Explain again. Do not answer again.** Never answer a new question. Never add new information. Never use tools. Exception: you can read the diagram rules in rule 5. Only say again what you already said, in a different way.\n2. **Simpler, not necessarily shorter.** If the idea needs space to be clear, use the space. The goal is \"impossible to misunderstand\", not \"fewer words\". Remove preamble, hedging and consultant-speak. Keep the length that real clarity needs.\n3. **Keep the facts exactly.** Each path, command, filename, number, URL, name and decision stays EXACTLY the same. Make the explanation around the facts simpler. Never change the facts.\n4. **Use Plain Language + Chicago Manual of Style.** Do not use em-dashes.\n5. **Add diagrams where they help.** If the idea is a data flow or a control flow, add a diagram. Follow the [diagram rules](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagentic-loops\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fdiagram.md).\n6. **Same language.** If your original message was not in English, write the simpler version in that language, with the same short, simple sentences.\n7. **Flatten the structure.** Remove headers and ceremony. Change tables into plain sentences or a diagram. Keep a short list only if the original really had more than one part.\n8. **Edge case:** if this conversation has no previous assistant message, say that there is nothing to simplify yet.\n","# \u002Fbro: say it simpler\n\nThe user typed `\u002Fbro`. Your last message was not clear to the user. It was too dense, had too much jargon, or was too formal.\n\n**Your task:** explain YOUR most recent assistant message again in a much simpler way.\n\n## Rules\n\n1. **Explain again. Do not answer again.** Never answer a new question. Never add new information. Never use tools. Exception: you can read the diagram rules in rule 5. Only say again what you already said, in a different way.\n2. **Simpler, not necessarily shorter.** If the idea needs space to be clear, use the space. The goal is \"impossible to misunderstand\", not \"fewer words\". Remove preamble, hedging and consultant-speak. Keep the length that real clarity needs.\n3. **Keep the facts exactly.** Each path, command, filename, number, URL, name and decision stays EXACTLY the same. Make the explanation around the facts simpler. Never change the facts.\n4. **Use Plain Language + Chicago Manual of Style.** Do not use em-dashes.\n5. **Add diagrams where they help.** If the idea is a data flow or a control flow, add a diagram. Follow the [diagram rules](https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagentic-loops\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fdiagram.md).\n6. **Same language.** If your original message was not in English, write the simpler version in that language, with the same short, simple sentences.\n7. **Flatten the structure.** Remove headers and ceremony. Change tables into plain sentences or a diagram. Keep a short list only if the original really had more than one part.\n8. **Edge case:** if this conversation has no previous assistant message, say that there is nothing to simplify yet.\n",{"name":5,"license":15,"description":7},"master","90d2da5ee908f1bfbeeb2d40e84b4c885cd286ce","skills\u002Fbro",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":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add microsoft\u002Fagentic-loops --skill bro",{"tool":58,"command":59},"bunx","bunx skills add microsoft\u002Fagentic-loops --skill bro",{"tool":61,"command":62},"pnpm","pnpm dlx skills add microsoft\u002Fagentic-loops --skill bro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagentic-loops\u002Fblob\u002Fmaster\u002Fskills\u002Fbro\u002FSKILL.md",true,[],[67,88],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":78,"publishedAt":38},"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",[73],{"categoryNo":74,"categoryName":75,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",[69,79,80,81,82,83,84,85,86,87,37],"code","comments","keep","documents","communicate","design","messages","communicate clearly","simple",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":38},"01M71873D2KYYJDX6ZWZFN05E6","teams","Write, sign and post Teams chat and channel messages for the human. Use \u002Fteams before you draft, post or edit a Teams message.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fagentic-loops\u002Fblob\u002Fmaster\u002Fskills\u002Fteams\u002FSKILL.md",[],[90,95,29,31,96,97,85,98,35,99,25,100,101,102],"channel","edit","write","sign","human","post","chat","draft"]