[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADSEN2YJPQ93S1GEA8CJ9C":3,"skill-same:01M6ADSEN2YJPQ93S1GEA8CJ9C":79},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6ADSEN2YJPQ93S1GEA8CJ9C","linkedin-post-formatter",null,"Format and draft compelling LinkedIn posts using Unicode bold\u002Fitalic styling, visual separators, structured sections, and engagement-optimized patterns. USE FOR: draft LinkedIn post, format text for LinkedIn, create social media post, write thought leadership post, convert content to LinkedIn format, LinkedIn carousel text, Unicode bold italic formatting.","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41162,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flinkedin-post-formatter\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"linkedin post formatter","formatter","linkedin","linkedin post","post","social","bold","for","carousel","posts","Unicode","formatting","leadership","create","patterns","styling","write","social media","text","Media","content","2026-11-10 10:12:30",false,"---\nname: linkedin-post-formatter\ndescription: 'Format and draft compelling LinkedIn posts using Unicode bold\u002Fitalic styling, visual separators, structured sections, and engagement-optimized patterns. USE FOR: draft LinkedIn post, format text for LinkedIn, create social media post, write thought leadership post, convert content to LinkedIn format, LinkedIn carousel text, Unicode bold italic formatting.'\n---\n\n# LinkedIn Post Formatter\n\nTransform raw content, ideas, or technical material into polished, engagement-optimized LinkedIn posts using Unicode typography and proven structural patterns.\n\n## Overview\n\nLinkedIn only supports plain text — no Markdown rendering, no rich formatting. This skill uses Unicode Mathematical Alphanumeric Symbols to simulate bold, italic, and bold-italic text that renders natively in the LinkedIn editor without any external tools.\n\n## Unicode Typography Reference\n\nWhen converting plain text into Unicode-styled LinkedIn text, first load and use `references\u002Funicode-charmap.md` as the authoritative character mapping reference.\n\nApply these character mappings to create visual emphasis in plain text:\n\n### Bold (Mathematical Sans-Serif Bold)\n\nUse bold for key phrases, section headers, and emphasis words.\n\n| Plain | Unicode Bold |\n|-------|-------------|\n| A-Z   | ?-?         |\n| a-z   | ?-?         |\n| 0-9   | ?-?         |\n\n### Italic (Mathematical Sans-Serif Italic)\n\nUse italic for subtle emphasis, technical terms, or quotes.\n\n| Plain | Unicode Italic |\n|-------|---------------|\n| A-Z   | ?-?           |\n| a-z   | ?-?           |\n\n### Bold-Italic (Mathematical Sans-Serif Bold Italic)\n\nUse sparingly for maximum emphasis.\n\n| Plain | Unicode Bold-Italic |\n|-------|-------------------|\n| A-Z   | ?-?               |\n| a-z   | ?-?               |\n\n## Visual Separators\n\nUse these characters to create visual structure:\n\n- **Section divider**: `━━━━━━━━━━━━━━━━━━━━━━` (box-drawing heavy horizontal)\n- **Bullet points**: `◈` (diamond with dot) or `◎` (bullseye)\n- **Arrow flow**: `↓` for vertical flow, `→` for horizontal continuation\n- **Sub-points**: `↳` for indented sub-items\n- **Numbered items**: Use bold Unicode digits `?. ?. ?.` etc.\n\n## Post Structure Patterns\n\n### Pattern 1: Hook → Content → CTA (General Purpose)\n\n```\n[Bold hook line — provocative statement or question]\n\n[1-2 lines of context setting the stage]\n\n━━━━━━━━━━━━━━━━━━━━━━\n\n[Main content with bold section headers]\n[Bullet points using ◈ or numbered with bold digits]\n\n━━━━━━━━━━━━━━━━━━━━━━\n\n[Bold takeaway or summary]\n\n[Call to action — repost, comment, or grab resource]\n\n#Hashtags\n```\n\n### Pattern 2: Listicle (Numbered Insights)\n\n```\n[Bold opening line with a strong claim]\n\n[Setup line explaining what follows]\n\n?. [Bold item title]\n   [Supporting detail]\n\n?. [Bold item title]\n   [Supporting detail]\n\n...\n\n??? ??? ????????: [Summary in italic]\n\n#Hashtags\n```\n\n### Pattern 3: Story → Lesson (Thought Leadership)\n\n```\n[Italic opening with a personal or observed moment]\n\n[2-3 short paragraphs telling the story]\n\n━━━━━━━━━━━━━━━━━━━━━━\n\n??? ??????:\n\n[Bold lesson or principle extracted from the story]\n\n[CTA]\n\n#Hashtags\n```\n\n### Pattern 4: Resource Share (Cheatsheet\u002FGuide\u002FTool)\n\n```\n[Hook: \"If you do X, you cannot miss this...\"]\n\n[Brief description of what the resource covers]\n\n━━━━━━━━━━━━━━━━━━━━━━\n\n[Bold section count]. [Bold section titles as numbered list]\n\n━━━━━━━━━━━━━━━━━━━━━━\n\n??? ???? ????????:\n\n[Why this resource matters — bold key phrase]\n\n[Grab it \u002F Share it CTA]\n\n♻️ ?????? if this is useful to your network.\n\n#Hashtags\n```\n\n## Formatting Rules\n\n1. **Line breaks matter**: LinkedIn collapses multiple blank lines. Use single blank lines between paragraphs.\n2. **Hook above the fold**: The first 2-3 lines must compel the reader to click \"see more.\" Front-load value.\n3. **Short paragraphs**: 1-3 sentences max per paragraph. Wall of text kills engagement.\n4. **Bold sparingly**: Bold key phrases and headers, not entire paragraphs.\n5. **Italic for nuance**: Use italic for technical terms, internal thoughts, or subtle emphasis.\n6. **Hashtags at the end**: 5-8 relevant hashtags on the last line. No mid-post hashtags.\n7. **No emojis in body** unless the user explicitly requests them. Exception: one strategic emoji in CTA (♻️ for repost).\n8. **Character limit**: LinkedIn posts can be up to 3000 characters. Aim for 1500-2500 for optimal engagement.\n9. **No URLs in body**: LinkedIn suppresses reach for posts with links. Add links in comments instead. Mention \"link in comments\" or \"grab it below\" as CTA.\n\n## Engagement Optimization\n\n- **Opening hooks that work**: Questions, bold claims, \"If you do X...\", contrarian takes, surprising stats.\n- **Closing CTAs that work**: \"♻️ ?????? if...\", \"Save this for later\", \"Tag someone who needs this\", \"What's your take? ?\"\n- **Whitespace is your friend**: Dense text gets scrolled past. Airy, scannable layout wins.\n- **The \"see more\" hook**: LinkedIn truncates posts after ~210 characters on desktop. Make sure the first 2 lines create enough curiosity to click.\n\n## Process\n\n1. Analyze the source content (text, HTML, image, or idea).\n2. Identify the best post structure pattern (Hook→Content→CTA, Listicle, Story→Lesson, Resource Share).\n3. Extract the core message and 3-5 key points.\n4. Apply Unicode bold\u002Fitalic formatting to headers and emphasis words using `references\u002Funicode-charmap.md`.\n5. Add visual separators between sections.\n6. Write a compelling hook for the opening.\n7. Add a CTA and hashtags at the end.\n8. Verify the post is copy-paste ready for LinkedIn.\n","# LinkedIn Post Formatter\n\nTransform raw content, ideas, or technical material into polished, engagement-optimized LinkedIn posts using Unicode typography and proven structural patterns.\n\n## Overview\n\nLinkedIn only supports plain text — no Markdown rendering, no rich formatting. This skill uses Unicode Mathematical Alphanumeric Symbols to simulate bold, italic, and bold-italic text that renders natively in the LinkedIn editor without any external tools.\n\n## Unicode Typography Reference\n\nWhen converting plain text into Unicode-styled LinkedIn text, first load and use `references\u002Funicode-charmap.md` as the authoritative character mapping reference.\n\nApply these character mappings to create visual emphasis in plain text:\n\n### Bold (Mathematical Sans-Serif Bold)\n\nUse bold for key phrases, section headers, and emphasis words.\n\n| Plain | Unicode Bold |\n|-------|-------------|\n| A-Z   | ?-?         |\n| a-z   | ?-?         |\n| 0-9   | ?-?         |\n\n### Italic (Mathematical Sans-Serif Italic)\n\nUse italic for subtle emphasis, technical terms, or quotes.\n\n| Plain | Unicode Italic |\n|-------|---------------|\n| A-Z   | ?-?           |\n| a-z   | ?-?           |\n\n### Bold-Italic (Mathematical Sans-Serif Bold Italic)\n\nUse sparingly for maximum emphasis.\n\n| Plain | Unicode Bold-Italic |\n|-------|-------------------|\n| A-Z   | ?-?               |\n| a-z   | ?-?               |\n\n## Visual Separators\n\nUse these characters to create visual structure:\n\n- **Section divider**: `━━━━━━━━━━━━━━━━━━━━━━` (box-drawing heavy horizontal)\n- **Bullet points**: `◈` (diamond with dot) or `◎` (bullseye)\n- **Arrow flow**: `↓` for vertical flow, `→` for horizontal continuation\n- **Sub-points**: `↳` for indented sub-items\n- **Numbered items**: Use bold Unicode digits `?. ?. ?.` etc.\n\n## Post Structure Patterns\n\n### Pattern 1: Hook → Content → CTA (General Purpose)\n\n```\n[Bold hook line — provocative statement or question]\n\n[1-2 lines of context setting the stage]\n\n━━━━━━━━━━━━━━━━━━━━━━\n\n[Main content with bold section headers]\n[Bullet points using ◈ or numbered with bold digits]\n\n━━━━━━━━━━━━━━━━━━━━━━\n\n[Bold takeaway or summary]\n\n[Call to action — repost, comment, or grab resource]\n\n#Hashtags\n```\n\n### Pattern 2: Listicle (Numbered Insights)\n\n```\n[Bold opening line with a strong claim]\n\n[Setup line explaining what follows]\n\n?. [Bold item title]\n   [Supporting detail]\n\n?. [Bold item title]\n   [Supporting detail]\n\n...\n\n??? ??? ????????: [Summary in italic]\n\n#Hashtags\n```\n\n### Pattern 3: Story → Lesson (Thought Leadership)\n\n```\n[Italic opening with a personal or observed moment]\n\n[2-3 short paragraphs telling the story]\n\n━━━━━━━━━━━━━━━━━━━━━━\n\n??? ??????:\n\n[Bold lesson or principle extracted from the story]\n\n[CTA]\n\n#Hashtags\n```\n\n### Pattern 4: Resource Share (Cheatsheet\u002FGuide\u002FTool)\n\n```\n[Hook: \"If you do X, you cannot miss this...\"]\n\n[Brief description of what the resource covers]\n\n━━━━━━━━━━━━━━━━━━━━━━\n\n[Bold section count]. [Bold section titles as numbered list]\n\n━━━━━━━━━━━━━━━━━━━━━━\n\n??? ???? ????????:\n\n[Why this resource matters — bold key phrase]\n\n[Grab it \u002F Share it CTA]\n\n♻️ ?????? if this is useful to your network.\n\n#Hashtags\n```\n\n## Formatting Rules\n\n1. **Line breaks matter**: LinkedIn collapses multiple blank lines. Use single blank lines between paragraphs.\n2. **Hook above the fold**: The first 2-3 lines must compel the reader to click \"see more.\" Front-load value.\n3. **Short paragraphs**: 1-3 sentences max per paragraph. Wall of text kills engagement.\n4. **Bold sparingly**: Bold key phrases and headers, not entire paragraphs.\n5. **Italic for nuance**: Use italic for technical terms, internal thoughts, or subtle emphasis.\n6. **Hashtags at the end**: 5-8 relevant hashtags on the last line. No mid-post hashtags.\n7. **No emojis in body** unless the user explicitly requests them. Exception: one strategic emoji in CTA (♻️ for repost).\n8. **Character limit**: LinkedIn posts can be up to 3000 characters. Aim for 1500-2500 for optimal engagement.\n9. **No URLs in body**: LinkedIn suppresses reach for posts with links. Add links in comments instead. Mention \"link in comments\" or \"grab it below\" as CTA.\n\n## Engagement Optimization\n\n- **Opening hooks that work**: Questions, bold claims, \"If you do X...\", contrarian takes, surprising stats.\n- **Closing CTAs that work**: \"♻️ ?????? if...\", \"Save this for later\", \"Tag someone who needs this\", \"What's your take? ?\"\n- **Whitespace is your friend**: Dense text gets scrolled past. Airy, scannable layout wins.\n- **The \"see more\" hook**: LinkedIn truncates posts after ~210 characters on desktop. Make sure the first 2 lines create enough curiosity to click.\n\n## Process\n\n1. Analyze the source content (text, HTML, image, or idea).\n2. Identify the best post structure pattern (Hook→Content→CTA, Listicle, Story→Lesson, Resource Share).\n3. Extract the core message and 3-5 key points.\n4. Apply Unicode bold\u002Fitalic formatting to headers and emphasis words using `references\u002Funicode-charmap.md`.\n5. Add visual separators between sections.\n6. Write a compelling hook for the opening.\n7. Add a CTA and hashtags at the end.\n8. Verify the post is copy-paste ready for LinkedIn.\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Flinkedin-post-formatter",5360,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot","https:\u002F\u002Fawesome-copilot.github.com\u002F","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-15 04:42:30",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add github\u002Fawesome-copilot --skill linkedin-post-formatter",{"tool":61,"command":62},"bunx","bunx skills add github\u002Fawesome-copilot --skill linkedin-post-formatter",{"tool":64,"command":65},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill linkedin-post-formatter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flinkedin-post-formatter\u002FSKILL.md",true,[69,75],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"package.json","REFERENCE","参考文档",874,"https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002Fpackages\u002Fsandbox-packs\u002Fsandbox-rrule\u002Fpackage.json",{"path":76,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Funicode-charmap.md",2583,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flinkedin-post-formatter\u002Freferences\u002Funicode-charmap.md",[80,114,141,171,205,222],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":94,"publishedAt":40},"01M70KXZNX9ES38N2A8M58ZZMZ","supabase-rls-policies","Write, review, and test Supabase Row Level Security (RLS) policies so that one user cannot read or change another user's rows. Use when creating or changing tables, policies, views, or security definer functions in a Supabase project, when reviewing a migration that touches RLS, or when asked to prove user isolation with pgTAP tests that sign in as two users.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsupabase-rls-policies\u002FSKILL.md",[86,91],{"categoryNo":87,"categoryName":88,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":92,"categoryName":93,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000023","Skill与智能体开发",[95,96,97,98,99,100,101,102,103,35,104,105,106,107,108,109,110,111,112,113],"supabase","rls","supabase rls","supabase rls policies","project","when","review","change","read","security","isolation","tables","as","tests","prove","use","users","functions","with",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":121,"publishedAt":40},"01M70KWA5YWXDV6V8DZ19E3T2Y","skill-distribution-audit","Audit a skill collection before release or investigate installer omissions, archived\u002Ftemplate leakage, duplicate identities, and manifest drift. Reconcile the intended public source set, distribution manifest, and actual discovery output for a specified consumer version. Includes a deterministic set-comparison helper.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fskill-distribution-audit\u002FSKILL.md",[120],{"categoryNo":92,"categoryName":93,"taxonomyType":89,"taxonomyTypeDesc":90},[122,123,124,125,126,127,26,128,129,130,131,132,133,134,135,136,137,138,139,140],"distribution","skill distribution audit","audit","SET","deterministic","installer","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":145,"sourceHtmlUrl":146,"categories":147,"keywords":153,"publishedAt":40},"01M70KCJPFVW7PPQ49CC5R8JGK","logicapps-custom-code-net10-migration","Migrate Azure Logic Apps Standard local-function custom-code projects from .NET 8 to .NET 10. Use for legacy Logic Apps custom-code workspace upgrades, project\u002Fpackage configuration, custom-worker settings, publication, and integrated VS Code debugging. Not for ordinary .NET applications, standalone Azure Functions, Consumption workflows, or cloud deployment.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FSKILL.md",[148],{"categoryNo":149,"categoryName":150,"taxonomyType":151,"taxonomyTypeDesc":152},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[154,155,156,157,158,159,26,99,160,161,162,163,164,165,166,110,167,168,169,170],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":175,"sourceHtmlUrl":176,"categories":177,"keywords":182,"publishedAt":40},"01M6AEBN37RQMXJ3298PEY7PG1","winmd-api-search","Find and explore Windows desktop APIs. Use when building features that need platform capabilities — camera, file access, notifications, UI controls, AI\u002FML, sensors, networking, etc. Discovers the right API for a task and retrieves full type details (methods, properties, events, enumeration values).","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FSKILL.md",[178,181],{"categoryNo":179,"categoryName":180,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":149,"categoryName":150,"taxonomyType":151,"taxonomyTypeDesc":152},[183,184,185,186,187,188,189,190,191,192,193,194,195,196,197,100,198,199,200,201,202,26,203,204],"winmd api search","search","api","windows","desktop","file access","enumeration","ui","ml","file","networking","capabilities","notifications","explore","access","features","full","camera","events","platform","methods","controls",{"skillNo":206,"name":207,"nameZh":6,"description":208,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":209,"licenseFileUrl":210,"sourceHtmlUrl":211,"categories":212,"keywords":218,"publishedAt":40},"01M6AE571R3SC1ZGE202B3NB5S","resemble-detect","Deepfake detection and media safety — detect AI-generated audio, images, video, and text, trace synthesis sources, apply watermarks, verify speaker identity, and analyze media intelligence using Resemble AI","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FSKILL.md",[213,214,217],{"categoryNo":179,"categoryName":180,"taxonomyType":89,"taxonomyTypeDesc":90},{"categoryNo":215,"categoryName":216,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":92,"categoryName":93,"taxonomyType":89,"taxonomyTypeDesc":90},[219,125,192,220,221],"resemble detect","https","identity",{"skillNo":223,"name":224,"nameZh":6,"description":225,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":209,"licenseFileUrl":226,"sourceHtmlUrl":227,"categories":228,"keywords":233,"publishedAt":40},"01M6AE30BSK2HCY4TQQ22Z8JRD","quality-playbook","Run a complete quality engineering audit on any codebase. Derives behavioral requirements from the code, generates spec-traced functional tests, runs a three-pass code review with regression tests, executes a multi-model spec audit (Council of Three), and produces a consolidated bug report with TDD-verified patches. Finds the 35% of real defects that structural code review alone cannot catch. Works with any language. Trigger on 'quality playbook', 'spec audit', 'Council of Three', 'fitness-to-purpose', or 'coverage theater'.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FSKILL.md",[229,232],{"categoryNo":230,"categoryName":231,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":92,"categoryName":93,"taxonomyType":89,"taxonomyTypeDesc":90},[234,235,236,237,155,101,9,124,238,239,220,240,241,242,243,244,245,246,247,248,249,250,108,251,252,253,254],"playbook","quality playbook","quality","code review","tdd","run","report","spec","bug report","council","engineering","functional","spec audit","bug","verified","multi-model","three","coverage","model","regression","structural"]