[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72TY994GF01D0MW8SMHC57E":3,"skill-same:01M72TY994GF01D0MW8SMHC57E":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M72TY994GF01D0MW8SMHC57E","meeting-mom",null,"Use when the user wants to create Minutes of Meeting","srafis\u002Fskills","srafis","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235246308?v=4","01M72TXNT2C698T34G2E0NXYZK","01M72TXNV3B1A02Y78K83806PJ",2,"MIT","https:\u002F\u002Fgithub.com\u002Fsrafis\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmeeting-mom\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: meeting-mom\ndescription: Use when the user wants to create Minutes of Meeting\n---\n\n# Meeting Transcript To MoM\n\nRead the supplied transcript, draft and review the MoM, and return only the final Markdown.\n\n## Writing and Accuracy\n\n- Use concise business language focused on requested changes, operational impact, decisions, responsibilities, blockers, and next steps. Explain technical terms only when essential.\n- Attribute statements to speakers where possible. Preserve important numbers, percentages, dates, statuses, feature names, and business terminology.\n- Use the meeting date supplied by the user or transcript; otherwise default to today's date.\n- Include every speaker as an attendee.\n- Record only decisions supported by the transcript. Do not turn suggestions into agreed decisions or invent owners, deadlines, blockers, or completed follow-up work.\n- Use stated timelines; otherwise use \"TBD\". Use \"TBD\" for unassigned action owners as well.\n- Mark unclear passages as \"(unclear)\" or \"(inaudible)\" and use direct quotes sparingly.\n- Before returning the MoM, check it against the transcript for completeness, attribution, and factual accuracy.\n\n## Output Structure\n\nUse the following layout in order, with no preamble or closing remarks. Include the tracker section only when applicable.\n\n### Opening Details\n\nStart directly with a quote block containing date and attendees on separate lines. Format the date as day with ordinal suffix, full month, and year (e.g., 6th August 2026). Do not add a meeting-details heading or duration.\n\n> **Date:** [supplied meeting date or today's date]\n> **Attendees:** [comma-separated speaker names]\n\n### **Agenda Items Covered**\n\nList every distinct business topic as a numbered list with concise topic names.\n\n### **[N]. [Topic Name]**\n\nCreate one numbered topic section per agenda item. Group related points under bold subtopic labels ending in a colon, such as **Issue Identified:** or **Decision:**, when helpful. Use bullets covering the discussion, requested changes, concerns, business impact, and outcomes; retain enough detail to explain behavior and restrictions. Use numbered lists for issue summaries or sequential steps when clearer.\n\n### **Key Decisions Made**\n\nList supported decisions as bullets, each beginning with a bold declarative sentence stating the agreed outcome or direction.\n\nIf none: \"No formal decisions were recorded in this meeting.\"\n\n### **Open Questions \u002F Pending Clarifications**\n\nUse a numbered list, starting each entry with a bold topic label followed by a colon. State what remains unresolved, who needs to clarify when known, and the business impact when relevant.\n\nIf none: \"No open questions or pending clarifications.\"\n\n### **Action Items Summary**\n\nWrite each action as a self-contained action description focused on the intended outcome.\n\n| **#** | **Action Item** | **Owner** | **ETA** |\n| --- | --- | --- | --- |\n\nIf none, replace the table with: \"No action items were identified.\"\n\n### **Blockers \u002F Dependencies**\n\nInclude only explicitly mentioned blockers or dependencies, their operational impact, and any stated mitigation or next step.\n\n| **Blocker** | **Impact** | **Mitigation \u002F Next Step** |\n| --- | --- | --- |\n\nIf none, replace the table with: \"No blockers were identified.\"\n\n### **Clarification Tracker Reference**\n\nIf pending clarifications need follow-up, include a short bullet recommending they be tracked in the shared clarification tracker. Claim entries were added only if the transcript confirms that. Otherwise omit this section.\n\n### **Next Meeting**\n\nState the date, time, or recurrence only if explicitly mentioned.\n\nIf absent: \"Next meeting details were not discussed.\"\n\n## Formatting\n\n- Use `### **Heading**` for section headings and `---` after the opening quote block and between sections, with blank lines around headings, lists, tables, and separators.\n- Use `-` for bullets and numbered lists where specified above.\n- Use bold for decision sentences, subtopic labels, table headers, and key facts where it aids scanning. Italicize titles of movies or other works when relevant.\n- Use valid Markdown table separators.\n","# Meeting Transcript To MoM\n\nRead the supplied transcript, draft and review the MoM, and return only the final Markdown.\n\n## Writing and Accuracy\n\n- Use concise business language focused on requested changes, operational impact, decisions, responsibilities, blockers, and next steps. Explain technical terms only when essential.\n- Attribute statements to speakers where possible. Preserve important numbers, percentages, dates, statuses, feature names, and business terminology.\n- Use the meeting date supplied by the user or transcript; otherwise default to today's date.\n- Include every speaker as an attendee.\n- Record only decisions supported by the transcript. Do not turn suggestions into agreed decisions or invent owners, deadlines, blockers, or completed follow-up work.\n- Use stated timelines; otherwise use \"TBD\". Use \"TBD\" for unassigned action owners as well.\n- Mark unclear passages as \"(unclear)\" or \"(inaudible)\" and use direct quotes sparingly.\n- Before returning the MoM, check it against the transcript for completeness, attribution, and factual accuracy.\n\n## Output Structure\n\nUse the following layout in order, with no preamble or closing remarks. Include the tracker section only when applicable.\n\n### Opening Details\n\nStart directly with a quote block containing date and attendees on separate lines. Format the date as day with ordinal suffix, full month, and year (e.g., 6th August 2026). Do not add a meeting-details heading or duration.\n\n> **Date:** [supplied meeting date or today's date]\n> **Attendees:** [comma-separated speaker names]\n\n### **Agenda Items Covered**\n\nList every distinct business topic as a numbered list with concise topic names.\n\n### **[N]. [Topic Name]**\n\nCreate one numbered topic section per agenda item. Group related points under bold subtopic labels ending in a colon, such as **Issue Identified:** or **Decision:**, when helpful. Use bullets covering the discussion, requested changes, concerns, business impact, and outcomes; retain enough detail to explain behavior and restrictions. Use numbered lists for issue summaries or sequential steps when clearer.\n\n### **Key Decisions Made**\n\nList supported decisions as bullets, each beginning with a bold declarative sentence stating the agreed outcome or direction.\n\nIf none: \"No formal decisions were recorded in this meeting.\"\n\n### **Open Questions \u002F Pending Clarifications**\n\nUse a numbered list, starting each entry with a bold topic label followed by a colon. State what remains unresolved, who needs to clarify when known, and the business impact when relevant.\n\nIf none: \"No open questions or pending clarifications.\"\n\n### **Action Items Summary**\n\nWrite each action as a self-contained action description focused on the intended outcome.\n\n| **#** | **Action Item** | **Owner** | **ETA** |\n| --- | --- | --- | --- |\n\nIf none, replace the table with: \"No action items were identified.\"\n\n### **Blockers \u002F Dependencies**\n\nInclude only explicitly mentioned blockers or dependencies, their operational impact, and any stated mitigation or next step.\n\n| **Blocker** | **Impact** | **Mitigation \u002F Next Step** |\n| --- | --- | --- |\n\nIf none, replace the table with: \"No blockers were identified.\"\n\n### **Clarification Tracker Reference**\n\nIf pending clarifications need follow-up, include a short bullet recommending they be tracked in the shared clarification tracker. Claim entries were added only if the transcript confirms that. Otherwise omit this section.\n\n### **Next Meeting**\n\nState the date, time, or recurrence only if explicitly mentioned.\n\nIf absent: \"Next meeting details were not discussed.\"\n\n## Formatting\n\n- Use `### **Heading**` for section headings and `---` after the opening quote block and between sections, with blank lines around headings, lists, tables, and separators.\n- Use `-` for bullets and numbered lists where specified above.\n- Use bold for decision sentences, subtopic labels, table headers, and key facts where it aids scanning. Italicize titles of movies or other works when relevant.\n- Use valid Markdown table separators.\n",{"name":5,"description":7},"main","e490e83f217c4749df8a2f4a1786d766bbce3f9a","skills\u002Fmeeting-mom",0,"https:\u002F\u002Fgithub.com\u002Fsrafis\u002Fskills","https:\u002F\u002Fgithub.com\u002Fsrafis","2026-10-16 03:12:32",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add srafis\u002Fskills --skill meeting-mom",{"tool":36,"command":37},"bunx","bunx skills add srafis\u002Fskills --skill meeting-mom",{"tool":39,"command":40},"pnpm","pnpm dlx skills add srafis\u002Fskills --skill meeting-mom","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsrafis\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmeeting-mom\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M72TYT9M9FB8S66E8WY3MQP1","work","Runs an Azure ticket delivery loop: fetch tickets, plan against design docs, implement via sub-agents, record before\u002Fafter videos, run quality gates and CodeRabbit, then post ticket comments and commit only when asked. Use when the user says \u002Fwork, names an Azure ticket or user story, or asks for a before\u002Fafter video or ticket comment.","https:\u002F\u002Fgithub.com\u002Fsrafis\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwork\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M72TYR7JTYQ2XS24DWSDB0RV","video-to-transcript","Use when the user wants to convert a local video or meeting recording into a text transcript, especially MP4\u002FMOV recordings. Covers extracting audio with ffmpeg and transcribing locally with faster-whisper.","https:\u002F\u002Fgithub.com\u002Fsrafis\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fvideo-to-transcript\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M72TYJ2E334HJHXTTG368G5Y","ui-ux-pro-max","UI\u002FUX design intelligence for web and mobile. Searchable local database with 84 styles, 192 color palettes, 74 font pairings, 192 product types, 98 UX guidelines, 104 icon entries, 16 GSAP motion presets, and 25 chart types across 22 stacks (React, Next.js, Vue, Nuxt, Svelte, Astro, SwiftUI, React Native, Flutter, Tailwind, shadcn\u002Fui, Jetpack Compose, Angular, Laravel, JavaFX, WPF, WinUI, Avalonia, Uno Platform, UWP, Three.js, and HTML\u002FCSS). Use when designing, building, or reviewing UI: pages, components, color schemes, typography, layout, accessibility, animation, or data visualization.","https:\u002F\u002Fgithub.com\u002Fsrafis\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fui-ux-pro-max\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M72TYF24YHZG4NMTR71CBFQM","ship-work","Use when shipping a software task end to end, with scope control and verified completion.","https:\u002F\u002Fgithub.com\u002Fsrafis\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fship\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M72TYCQDYR3XGP2J6EFD00V8","quick","Delegate task to fast model","https:\u002F\u002Fgithub.com\u002Fsrafis\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fquick\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M72TY3A28XQSPEJXWNMCC9P7","humanizer","Rewrite AI-sounding text so it reads like the writer without changing what it says.\nUse when editing or reviewing prose for AI tells: not-X-but-Y contrasts, one-line\nclosers, staged openers, forced triads, dashes everywhere, inflated claims, sales\nlanguage, stock AI words, bold labels, or filler. Based on Wikipedia's \"Signs of AI writing.\"","https:\u002F\u002Fgithub.com\u002Fsrafis\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fhumanizer\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fsrafis\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fhumanizer\u002FSKILL.md",[],[]]