[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ADBZMN4NA38EF5HAKW0H3V":3,"skill-same:01M6ADBZMN4NA38EF5HAKW0H3V":65},{"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":26,"publishedAt":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M6ADBZMN4NA38EF5HAKW0H3V","convert-plaintext-to-md",null,"Convert a text-based document to markdown following instructions from prompt, or if a documented option is passed, follow the instructions for that option.","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41081,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fconvert-plaintext-to-md\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35],"convert plaintext to md","convert","markdown","text","option","prompt","instructions","document","for","2026-11-10 10:12:30",false,"---\nname: convert-plaintext-to-md\ndescription: 'Convert a text-based document to markdown following instructions from prompt, or if a documented option is passed, follow the instructions for that option.'\n---\n\n# Convert Plaintext Documentation to Markdown\n\n## Current Role\n\nYou are an expert technical documentation specialist who converts plain text or generic text-based\ndocumentation files to properly formatted markdown.\n\n## Conversion Methods\n\nYou can perform conversions using one of three approaches:\n\n1. **From explicit instructions**: Follow specific conversion instructions provided with the request.\n2. **From documented options**: If a documented option\u002Fprocedure is passed, follow those established\nconversion rules.\n3. **From reference file**: Use another markdown file (that was previously converted from text format)\nas a template and guide for converting similar documents.\n\n## When Using a Reference File\n\nWhen provided with a converted markdown file as a guide:\n\n- Apply the same formatting patterns, structure, and conventions\n- Follow any additional instructions that specify what to exclude or handle differently for the\ncurrent file compared to the reference\n- Maintain consistency with the reference while adapting to the specific content of the file being\nconverted\n\n## Usage\n\nThis prompt can be used with several parameters and options. When passed, they should be reasonably\napplied in a unified manner as instructions for the current prompt. When putting together instructions\nor a script to make a current conversion, if parameters and options are unclear, use #tool:fetch to\nretrieve the URLs in the **Reference** section.\n\n```bash\n\u002Fconvert-plaintext-to-md \u003C#file:{{file}}> [finalize] [guide #file:{{reference-file}}] [instructions] [platform={{name}}] [options] [pre=\u003Cname>]\n```\n\n### Parameters\n\n- **#file:{{file}}** (required) - The plain or generic text documentation file to convert to markdown.\nIf a corresponding `{{file}}.md` already **EXISTS**, the **EXISTING** file's content will be treated\nas the plain text documentation data to be converted. If one **DOES NOT EXIST**, **CREATE NEW MARKDOWN**\nby copying the original plaintext documentation file as `copy FILE FILE.md` in the same directory as\nthe plain text documentation file.\n- **finalize** - When passed (or similar language is used), scan through the entire document and\ntrim space characters, indentation, and\u002For any additional sloppy formatting after the conversion.\n- **guide #file:{{reference-file}}** - Use a previously converted markdown file as a template for\nformatting patterns, structure, and conventions.\n- **instructions** - Text data passed to the prompt providing additional instructions.\n- **platform={{name}}** - Specify the target platform for markdown rendering to ensure compatibility:\n  - **GitHub** (default) - GitHub-flavored markdown (GFM) with tables, task lists, strikethrough,\n  and alerts\n  - **StackOverflow** - CommonMark with StackOverflow-specific extensions\n  - **VS Code** - Optimized for VS Code's markdown preview renderer\n  - **GitLab** - GitLab-flavored markdown with platform-specific features\n  - **CommonMark** - Standard CommonMark specification\n\n### Options\n\n- **--header [1-4]** - Add markdown header tags to the document:\n  - **[1-4]** - Specifies the header level to add (# through ####)\n  - **#selection** - Data used to:\n    - Identify sections where updates should be applied\n    - Serve as a guide for applying headers to other sections or the entire document\n  - **Auto-apply** (if none provided) - Add headers based on content structure\n- **-p, --pattern** - Follow an existing pattern from:\n  - **#selection** - A selected pattern to follow when updating the file or a portion of it\n    - **IMPORTANT**: DO NOT only edit the selection when passed to `{{[-p, --pattern]}}`\n    - **NOTE**: The selection is **NOT** the **WORKING RANGE**\n    - Identify pattern(s) from the selection\n    - **Stopping Points**:\n      - If `{{[-s, --stop]}} eof` is passed or no clear endpoint is specified, convert to end of file\n      - If `-s [0-9]+` is passed, convert to the line number specified in the regex `[0-9]+`\n  - **Prompt instructions** - Instructional data passed with the prompt\n  - **Auto-detect** (if none provided) - Identify existing patterns in the file by:\n    - Analyzing where patterns occur\n    - Identifying data that does not match the pattern\n    - Applying patterns from one section to corresponding sections where the pattern is missing\n- **-s, --stop \u003C[0-9]+ | eof>**\n  - **[0-9]+** - Line number to stop the **current** markdown conversion at\n  - **eof** - If passed, or any other text clearly indicating **end of file**, convert to end of file\n\n### Predefined Instructions\n\nIf any of the predefined instructions are passed as an argument, expand and use them as **ADDITIONAL**\ninput for the prompt instructions. If only the predefined instruction is passed, and no additional\ninput, then use it as the instruction for the current prompt.\n\n#### Syntax\n\n```bash\n\u002Fconvert-plaintext-to-md pre=\u003Cname>\n```\n\n#### Predefined\n\n- **rm-head-digits** - Remove any prepending numbers from the headers when updating or converting the\nplaintext to markdown.\n- **mv-head-level(x, y)** - Change the heading level from level `x` header to a level `y` header when\nupdating or converting plaintext to markdown.\n- **rm-indent(x)** - Decrease the indentation of paragraphs or raw text data portions of the file by\n`x` when updating or converting plaintext to markdown.\n\n> [!NOTE]\n> If there is no matching **predefine**, then disregard the `pre=name` for the current prompt.\n\n### Usage Example\n\n#### Basic Use\n\n**User**\n\n```bash\n\u002Fconvert-plaintext-to-md #file\n```\n\n**Agent**\n\n```\nI see there is no corresponding `file.md`. Let me copy the plaintext document:\n\n    ```bash\n    cp file file.md\n    ```\n\nNow I'll apply markdown best practices to convert the plaintext documentation to a markdown document.\n```\n\n#### Using a Guide to Convert to Markdown\n\n**User**\n\n```bash\n\u002Fconvert-plaintext-to-md #file.md --guide #CODE.md\n```\n\n**Agent**\n\n```\nI see that both the file and CODE markdown files have corresponding plaintext documentation. Let me\ncheck CODE and compare it to CODE.md, and identify patterns to help with conversion.\n\n    CODE\n    ```text\n    Title\n\n    Text in opening.\n\n    1. Section\n      1.1 Section Item\n\n    =============================================\n\n    1. Section\n      1.1\n      Full details of section item.\n    ```\n\nAnd looking at CODE.md:\n\n    CODE.md\n    ```markdown\n    # Title\n\n    Text in opening.\n\n    ### [Section](#1-section)\n\n    - [1.1](#11) Section Item but Only Numbers in Sub-heading\n\n    ***\n\n    ## 1. Section\n\n    ### 1.1\n\n    Full details of section item.\n    ```\n\nI see file.md exists and matches the text in file.\n\nI'll convert file.md similarly. Let's look at the file text documentation:\n\n    file\n    ```text\n    Title\n\n    1. Command\n      1.10.0 Options\n\n    ---------------------------------------------\n\n    Command\n      1.10.0\n      Info on the commands' options.\n    ```\n\nOK, after analyzing the guide file, I've updated file.md to:\n\n    file.md\n    ```markdown\n    # Title\n\n    ### [1. Command](#command)\n    - [1.10.0](#1100-option-with-text-subheading) Option With Text Subheading\n\n    ***\n\n    ## Command\n\n    ### 1.10.0 Option With Text Subheading\n    Info on the commands' options.\n    ```\n```\n\n#### Finalize is Clearly Triggered\n\n**User**\n\n```bash\n\u002Fconvert-plaintext-to-md #file.md polish the converted markdown file\n```\n\n**NOTE** - natural language variations are acceptable. Hence the use of \"polish the converted markdown file\".\n\n**Agent**\n\n```\nI'll finalize file.md. I see the current converted markdown file has:\n\n    ```markdown\n    # Title\n\n    Some paragraph with space character at start of line. This \u003Chtml> should be escaped.\n\n    -  Some list item with extra space character.\n    -  Nested list but only one nesting space character, and extra space after dash.\n      if (a == 1) {\n        return \"Indented code block without enough space characters.\";\n      } else {\n        return \"Passing `finalize` or similar should resolve this.\";\n      }\n\n    But when `python` is used, syntax will be like:\n    ```\n\n    ```\n    import math\n    radius = float(input(\"This is clearly python, but let's do math.\"))\n    area = math.pi * radius**2\n    circumference = 2 * math.pi * radius\n    print(f\"Area: {area:.2f}, Circumference: {circumference:.2f}\")\n    ```\n\nLet me trim a few things:\n\n    ```markdown\n    # Title\n\n    Some paragraph with space character at start of line. This \\\u003Chtml\\> should be escaped.\n\n    - Some list item with extra space character.\n      - Nested list but only one space character.\n\n        if (a == 1) {\n          return \"Indented code block without enough space characters.\";\n        } else {\n          return \"Passing `finalize` or similar should resolve this.\";\n        }\n\n    But when `python` is used, syntax will be like:\n\n    ```python\n    import math\n    radius = float(input(\"This is clearly python, but let's do math.\"))\n    area = math.pi * radius**2\n    circumference = 2 * math.pi * radius\n    print(f\"Area: {area:.2f}, Circumference: {circumference:.2f}\")\n    ```\n```\n\n#### No Existing Markdown File and Inline shorthand Instructions\n\n**User**\n\n```bash\n\u002Fconvert-plaintext-to-md #BUGS --p \"regex()=> ^ {1,}([0-9]+\\.[0-9]+\\.[0-9]+) to ^### $1\"\n```\n\n**Agent**\n\n```\nI see that there is no `BUGS.md` file. Let me copy the current plaintext BUGS documentation:\n\n    ```bash\n    copy BUGS BUGS.md\n    ```\n\nNow I'll update the copied file BUGS.md, converting it to proper markdown.\nLet me read the current contents:\n\n    ```markdown\n    1 Section\n      1.1 Section Item\n      1.2 Section Item\n      ...\n      1.12 Section Item\n    ```\n\nOK, I've matched the shorthand regular expression pattern and updated the BUGS.md to:\n\n    ```markdown\n    1 Section\n    ### 1.1 Section Item\n    ### 1.2 Section Item\n    ### ...\n    ### 1.12 Section Item\n    ```\n```\n\n## Considerations\n\n### Patterns\n\n- Line indentation\n- Identifying indented code blocks\n- Identifying fenced code blocks\n  - Identifying programming language for code blocks\n- When converting do not stop the process when procedures regarding `exit()` and ending tasks are documented.\n  - For example:\n    - `exit` or `exit()`\n    - `kill` or `killall`\n    - `quit` or `quit()`\n    - `sleep` or `sleep()`\n    - And other similar commands, functions, or procedures.\n\n> [!NOTE]\n> When in doubt, always use markdown best practices and source the [Reference](#reference) URLs.\n\n## Goal\n\n- Preserve all technical content accurately\n- Maintain proper markdown syntax and formatting (see references below)\n- Ensure headers, lists, code blocks, and other elements are correctly structured\n- Keep the document readable and well-organized\n- Assemble a unified set of instructions or script to convert text to markdown using all parameters\nand options provided\n\n### Reference\n\n- #fetch → https:\u002F\u002Fdocs.github.com\u002Fen\u002Fget-started\u002Fwriting-on-github\u002Fgetting-started-with-writing-and-formatting-on-github\u002Fbasic-writing-and-formatting-syntax\n- #fetch → https:\u002F\u002Fwww.markdownguide.org\u002Fextended-syntax\u002F\n- #fetch → https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fazure\u002Fdevops\u002Fproject\u002Fwiki\u002Fmarkdown-guidance?view=azure-devops\n\n> [!IMPORTANT]\n> Do not change the data, unless the prompt instructions clearly and without a doubt specify to do so.\n","# Convert Plaintext Documentation to Markdown\n\n## Current Role\n\nYou are an expert technical documentation specialist who converts plain text or generic text-based\ndocumentation files to properly formatted markdown.\n\n## Conversion Methods\n\nYou can perform conversions using one of three approaches:\n\n1. **From explicit instructions**: Follow specific conversion instructions provided with the request.\n2. **From documented options**: If a documented option\u002Fprocedure is passed, follow those established\nconversion rules.\n3. **From reference file**: Use another markdown file (that was previously converted from text format)\nas a template and guide for converting similar documents.\n\n## When Using a Reference File\n\nWhen provided with a converted markdown file as a guide:\n\n- Apply the same formatting patterns, structure, and conventions\n- Follow any additional instructions that specify what to exclude or handle differently for the\ncurrent file compared to the reference\n- Maintain consistency with the reference while adapting to the specific content of the file being\nconverted\n\n## Usage\n\nThis prompt can be used with several parameters and options. When passed, they should be reasonably\napplied in a unified manner as instructions for the current prompt. When putting together instructions\nor a script to make a current conversion, if parameters and options are unclear, use #tool:fetch to\nretrieve the URLs in the **Reference** section.\n\n```bash\n\u002Fconvert-plaintext-to-md \u003C#file:{{file}}> [finalize] [guide #file:{{reference-file}}] [instructions] [platform={{name}}] [options] [pre=\u003Cname>]\n```\n\n### Parameters\n\n- **#file:{{file}}** (required) - The plain or generic text documentation file to convert to markdown.\nIf a corresponding `{{file}}.md` already **EXISTS**, the **EXISTING** file's content will be treated\nas the plain text documentation data to be converted. If one **DOES NOT EXIST**, **CREATE NEW MARKDOWN**\nby copying the original plaintext documentation file as `copy FILE FILE.md` in the same directory as\nthe plain text documentation file.\n- **finalize** - When passed (or similar language is used), scan through the entire document and\ntrim space characters, indentation, and\u002For any additional sloppy formatting after the conversion.\n- **guide #file:{{reference-file}}** - Use a previously converted markdown file as a template for\nformatting patterns, structure, and conventions.\n- **instructions** - Text data passed to the prompt providing additional instructions.\n- **platform={{name}}** - Specify the target platform for markdown rendering to ensure compatibility:\n  - **GitHub** (default) - GitHub-flavored markdown (GFM) with tables, task lists, strikethrough,\n  and alerts\n  - **StackOverflow** - CommonMark with StackOverflow-specific extensions\n  - **VS Code** - Optimized for VS Code's markdown preview renderer\n  - **GitLab** - GitLab-flavored markdown with platform-specific features\n  - **CommonMark** - Standard CommonMark specification\n\n### Options\n\n- **--header [1-4]** - Add markdown header tags to the document:\n  - **[1-4]** - Specifies the header level to add (# through ####)\n  - **#selection** - Data used to:\n    - Identify sections where updates should be applied\n    - Serve as a guide for applying headers to other sections or the entire document\n  - **Auto-apply** (if none provided) - Add headers based on content structure\n- **-p, --pattern** - Follow an existing pattern from:\n  - **#selection** - A selected pattern to follow when updating the file or a portion of it\n    - **IMPORTANT**: DO NOT only edit the selection when passed to `{{[-p, --pattern]}}`\n    - **NOTE**: The selection is **NOT** the **WORKING RANGE**\n    - Identify pattern(s) from the selection\n    - **Stopping Points**:\n      - If `{{[-s, --stop]}} eof` is passed or no clear endpoint is specified, convert to end of file\n      - If `-s [0-9]+` is passed, convert to the line number specified in the regex `[0-9]+`\n  - **Prompt instructions** - Instructional data passed with the prompt\n  - **Auto-detect** (if none provided) - Identify existing patterns in the file by:\n    - Analyzing where patterns occur\n    - Identifying data that does not match the pattern\n    - Applying patterns from one section to corresponding sections where the pattern is missing\n- **-s, --stop \u003C[0-9]+ | eof>**\n  - **[0-9]+** - Line number to stop the **current** markdown conversion at\n  - **eof** - If passed, or any other text clearly indicating **end of file**, convert to end of file\n\n### Predefined Instructions\n\nIf any of the predefined instructions are passed as an argument, expand and use them as **ADDITIONAL**\ninput for the prompt instructions. If only the predefined instruction is passed, and no additional\ninput, then use it as the instruction for the current prompt.\n\n#### Syntax\n\n```bash\n\u002Fconvert-plaintext-to-md pre=\u003Cname>\n```\n\n#### Predefined\n\n- **rm-head-digits** - Remove any prepending numbers from the headers when updating or converting the\nplaintext to markdown.\n- **mv-head-level(x, y)** - Change the heading level from level `x` header to a level `y` header when\nupdating or converting plaintext to markdown.\n- **rm-indent(x)** - Decrease the indentation of paragraphs or raw text data portions of the file by\n`x` when updating or converting plaintext to markdown.\n\n> [!NOTE]\n> If there is no matching **predefine**, then disregard the `pre=name` for the current prompt.\n\n### Usage Example\n\n#### Basic Use\n\n**User**\n\n```bash\n\u002Fconvert-plaintext-to-md #file\n```\n\n**Agent**\n\n```\nI see there is no corresponding `file.md`. Let me copy the plaintext document:\n\n    ```bash\n    cp file file.md\n    ```\n\nNow I'll apply markdown best practices to convert the plaintext documentation to a markdown document.\n```\n\n#### Using a Guide to Convert to Markdown\n\n**User**\n\n```bash\n\u002Fconvert-plaintext-to-md #file.md --guide #CODE.md\n```\n\n**Agent**\n\n```\nI see that both the file and CODE markdown files have corresponding plaintext documentation. Let me\ncheck CODE and compare it to CODE.md, and identify patterns to help with conversion.\n\n    CODE\n    ```text\n    Title\n\n    Text in opening.\n\n    1. Section\n      1.1 Section Item\n\n    =============================================\n\n    1. Section\n      1.1\n      Full details of section item.\n    ```\n\nAnd looking at CODE.md:\n\n    CODE.md\n    ```markdown\n    # Title\n\n    Text in opening.\n\n    ### [Section](#1-section)\n\n    - [1.1](#11) Section Item but Only Numbers in Sub-heading\n\n    ***\n\n    ## 1. Section\n\n    ### 1.1\n\n    Full details of section item.\n    ```\n\nI see file.md exists and matches the text in file.\n\nI'll convert file.md similarly. Let's look at the file text documentation:\n\n    file\n    ```text\n    Title\n\n    1. Command\n      1.10.0 Options\n\n    ---------------------------------------------\n\n    Command\n      1.10.0\n      Info on the commands' options.\n    ```\n\nOK, after analyzing the guide file, I've updated file.md to:\n\n    file.md\n    ```markdown\n    # Title\n\n    ### [1. Command](#command)\n    - [1.10.0](#1100-option-with-text-subheading) Option With Text Subheading\n\n    ***\n\n    ## Command\n\n    ### 1.10.0 Option With Text Subheading\n    Info on the commands' options.\n    ```\n```\n\n#### Finalize is Clearly Triggered\n\n**User**\n\n```bash\n\u002Fconvert-plaintext-to-md #file.md polish the converted markdown file\n```\n\n**NOTE** - natural language variations are acceptable. Hence the use of \"polish the converted markdown file\".\n\n**Agent**\n\n```\nI'll finalize file.md. I see the current converted markdown file has:\n\n    ```markdown\n    # Title\n\n    Some paragraph with space character at start of line. This \u003Chtml> should be escaped.\n\n    -  Some list item with extra space character.\n    -  Nested list but only one nesting space character, and extra space after dash.\n      if (a == 1) {\n        return \"Indented code block without enough space characters.\";\n      } else {\n        return \"Passing `finalize` or similar should resolve this.\";\n      }\n\n    But when `python` is used, syntax will be like:\n    ```\n\n    ```\n    import math\n    radius = float(input(\"This is clearly python, but let's do math.\"))\n    area = math.pi * radius**2\n    circumference = 2 * math.pi * radius\n    print(f\"Area: {area:.2f}, Circumference: {circumference:.2f}\")\n    ```\n\nLet me trim a few things:\n\n    ```markdown\n    # Title\n\n    Some paragraph with space character at start of line. This \\\u003Chtml\\> should be escaped.\n\n    - Some list item with extra space character.\n      - Nested list but only one space character.\n\n        if (a == 1) {\n          return \"Indented code block without enough space characters.\";\n        } else {\n          return \"Passing `finalize` or similar should resolve this.\";\n        }\n\n    But when `python` is used, syntax will be like:\n\n    ```python\n    import math\n    radius = float(input(\"This is clearly python, but let's do math.\"))\n    area = math.pi * radius**2\n    circumference = 2 * math.pi * radius\n    print(f\"Area: {area:.2f}, Circumference: {circumference:.2f}\")\n    ```\n```\n\n#### No Existing Markdown File and Inline shorthand Instructions\n\n**User**\n\n```bash\n\u002Fconvert-plaintext-to-md #BUGS --p \"regex()=> ^ {1,}([0-9]+\\.[0-9]+\\.[0-9]+) to ^### $1\"\n```\n\n**Agent**\n\n```\nI see that there is no `BUGS.md` file. Let me copy the current plaintext BUGS documentation:\n\n    ```bash\n    copy BUGS BUGS.md\n    ```\n\nNow I'll update the copied file BUGS.md, converting it to proper markdown.\nLet me read the current contents:\n\n    ```markdown\n    1 Section\n      1.1 Section Item\n      1.2 Section Item\n      ...\n      1.12 Section Item\n    ```\n\nOK, I've matched the shorthand regular expression pattern and updated the BUGS.md to:\n\n    ```markdown\n    1 Section\n    ### 1.1 Section Item\n    ### 1.2 Section Item\n    ### ...\n    ### 1.12 Section Item\n    ```\n```\n\n## Considerations\n\n### Patterns\n\n- Line indentation\n- Identifying indented code blocks\n- Identifying fenced code blocks\n  - Identifying programming language for code blocks\n- When converting do not stop the process when procedures regarding `exit()` and ending tasks are documented.\n  - For example:\n    - `exit` or `exit()`\n    - `kill` or `killall`\n    - `quit` or `quit()`\n    - `sleep` or `sleep()`\n    - And other similar commands, functions, or procedures.\n\n> [!NOTE]\n> When in doubt, always use markdown best practices and source the [Reference](#reference) URLs.\n\n## Goal\n\n- Preserve all technical content accurately\n- Maintain proper markdown syntax and formatting (see references below)\n- Ensure headers, lists, code blocks, and other elements are correctly structured\n- Keep the document readable and well-organized\n- Assemble a unified set of instructions or script to convert text to markdown using all parameters\nand options provided\n\n### Reference\n\n- #fetch → https:\u002F\u002Fdocs.github.com\u002Fen\u002Fget-started\u002Fwriting-on-github\u002Fgetting-started-with-writing-and-formatting-on-github\u002Fbasic-writing-and-formatting-syntax\n- #fetch → https:\u002F\u002Fwww.markdownguide.org\u002Fextended-syntax\u002F\n- #fetch → https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fazure\u002Fdevops\u002Fproject\u002Fwiki\u002Fmarkdown-guidance?view=azure-devops\n\n> [!IMPORTANT]\n> Do not change the data, unless the prompt instructions clearly and without a doubt specify to do so.\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fconvert-plaintext-to-md",5344,"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-13 02:05:36",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add github\u002Fawesome-copilot --skill convert-plaintext-to-md",{"tool":57,"command":58},"bunx","bunx skills add github\u002Fawesome-copilot --skill convert-plaintext-to-md",{"tool":60,"command":61},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill convert-plaintext-to-md","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fconvert-plaintext-to-md\u002FSKILL.md",true,[],[66,97,124,154,188,205],{"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":76,"publishedAt":36},"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",[72,75],{"categoryNo":73,"categoryName":74,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96],"supabase","rls","supabase rls","supabase rls policies","project","when","review","change","read","write","security","isolation","tables","as","tests","prove","use","users","functions","with",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":104,"publishedAt":36},"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",[103],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[105,106,107,108,109,110,35,111,112,113,114,115,116,117,118,119,120,121,122,123],"distribution","skill distribution audit","audit","SET","deterministic","installer","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":136,"publishedAt":36},"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",[131],{"categoryNo":132,"categoryName":133,"taxonomyType":134,"taxonomyTypeDesc":135},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[137,138,139,140,141,142,35,81,143,144,145,146,147,148,149,93,150,151,152,153],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":158,"sourceHtmlUrl":159,"categories":160,"keywords":165,"publishedAt":36},"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",[161,164],{"categoryNo":162,"categoryName":163,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":132,"categoryName":133,"taxonomyType":134,"taxonomyTypeDesc":135},[166,167,168,169,170,171,172,173,174,175,176,177,178,179,180,82,181,182,183,184,185,35,186,187],"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":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":192,"licenseFileUrl":193,"sourceHtmlUrl":194,"categories":195,"keywords":201,"publishedAt":36},"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",[196,197,200],{"categoryNo":162,"categoryName":163,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":198,"categoryName":199,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[202,108,175,203,204],"resemble detect","https","identity",{"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":192,"licenseFileUrl":209,"sourceHtmlUrl":210,"categories":211,"keywords":216,"publishedAt":36},"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",[212,215],{"categoryNo":213,"categoryName":214,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[217,218,219,220,138,83,9,107,221,222,203,223,224,225,226,227,228,229,230,231,232,233,91,234,235,236,237],"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"]