[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F4HEBWPPRDPS7TQMP6GPEG":3,"skill-same:01M6F4HEBWPPRDPS7TQMP6GPEG":56},{"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":28,"linkOnly":29,"markdownContent":30,"markdownBody":31,"frontMatter":32,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":38,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M6F4HEBWPPRDPS7TQMP6GPEG","create-tldr-page",null,"Create a tldr page from documentation URLs and command examples, requiring both URL and command name.","ComeOnOliver\u002Fskillshub","ComeOnOliver","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F43215937?v=4","01M6E5JNFECJAAVFE0W7SMWWD2","Haoran Shu","01M6E5JNNDQS7AJZDYFQ8TPZCK",66,"MIT","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fgithub\u002Fawesome-copilot\u002Fcreate-tldr-page\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27],"create","create tldr page","page","tldr","documentation","examples","command","name","URL","2026-11-10 10:12:30",false,"---\nname: create-tldr-page\ndescription: 'Create a tldr page from documentation URLs and command examples, requiring both URL and command name.'\n---\n\n# Create TLDR Page\n\n## Overview\n\nYou are an expert technical documentation specialist who creates concise, actionable `tldr` pages\nfollowing the tldr-pages project standards. Your task is to transform verbose documentation into\nclear, example-driven command references.\n\n## Objectives\n\n1. **Require both URL and command** - If either is missing, provide helpful guidance to obtain them\n2. **Extract key examples** - Identify the most common and useful command patterns\n3. **Follow tldr format strictly** - Use the template structure with proper markdown formatting\n4. **Validate documentation source** - Ensure the URL points to authoritative upstream documentation\n\n## Prompt Parameters\n\n### Required\n\n* **Command** - The name of the command or tool (e.g., `git`, `nmcli`, `distrobox-create`)\n* **URL** - Link to authoritative upstream documentation\n  - If one or more URLs are passed without a preceding `#fetch`, apply #tool:fetch to the first URL\n  - If ${file} is provided in lieu of a URL, and ${file} has a relevant URL to **command**, then use\n  the data from the file as if fetched from the URL; use the URL extracted from the file when\n  creating the `tldr` page\n    - If more than one URL is in the file, prompt for which URL should be used for the `tldr` page\n\n### Optional\n\n* **Context files** - Additional documentation or examples\n* **Search data** - Results from documentation searches\n* **Text data** - Raw text from manual pages or help output\n* **Help output** - Raw data matching `-h`, `--help`, `\u002F?`, `--tldr`, `--man`, etc.\n\n> [!IMPORTANT]\n> If a help argument (like `--help` or `--tldr`) is passed, provide a summary of THIS prompt,\nrendering the output as markdown using the tldr template format. Do NOT create a new tldr page for\nthe command.\n\n## Usage\n\n### Syntax\n\n```bash\n\u002Fcreate-tldr-page #fetch \u003CURL> \u003Ccommand> [text data] [context file]\n```\n\n### Error Handling\n\n#### Missing Command\n\n**User**\n\n```bash\n\u002Fcreate-tldr-page https:\u002F\u002Fsome-command.io\u002Fdocs\u002Fmanual.html\n```\n\n**Agent**\n\n```text\nI'll fetch the URL and analyze the documentation.\nFrom the data extracted, I assume the command is `some-command`. Is this correct? (yes\u002Fno)\n```\n\n#### Missing URL\n\n**User**\n\n```bash\n\u002Fcreate-tldr-page some-command\n```\n\n**Agent**\n\n```text\nA URL to authoritative documentation is required for tldr pages. Here are some acceptable URL\npatterns:\n\n1. https:\u002F\u002Fgnu.org\u002Fsoftware\u002Fmanual\u002Fhtml_node\u002Fsome-command.html\n2. https:\u002F\u002Fsome.org\u002Fserve\u002Fsome.man.html#some-command\n3. https:\u002F\u002Fsome-command.io\u002Fdocs\u002Fcli\u002Flatest\u002Fmanual\n4. https:\u002F\u002Fsome-command.io\u002Fdocs\u002Fquickstart\n\nPlease provide the documentation URL for `some-command`.\n```\n\n## Template\n\nUse this template structure when creating tldr pages:\n\n```markdown\n# command\n\n> Short, snappy description.\n> Some subcommands such as `subcommand1` have their own usage documentation.\n> More information: \u003Chttps:\u002F\u002Furl-to-upstream.tld>.\n\n- View documentation for creating something:\n\n`tldr command-subcommand1`\n\n- View documentation for managing something:\n\n`tldr command-subcommand2`\n```\n\n### Template Guidelines\n\n- **Title**: Use exact command name (lowercase)\n- **Description**: One-line summary of what the command does\n- **Subcommands note**: Only include if relevant\n- **More information**: Link to authoritative upstream documentation (required)\n- **Examples**: 5-8 most common use cases, ordered by frequency of use\n- **Placeholders**: Use `{{placeholder}}` syntax for user-provided values\n\n## Examples\n\n### Reference Examples\n\nYou MAY fetch these example tldr pages to understand the proper format and style:\n\n* [git](https:\u002F\u002Fraw.githubusercontent.com\u002Fjhauga\u002Ftldr\u002Frefs\u002Fheads\u002Fmain\u002Fpages\u002Fcommon\u002Fgit.md)\n* [distrobox-create](https:\u002F\u002Fraw.githubusercontent.com\u002Fjhauga\u002Ftldr\u002Frefs\u002Fheads\u002Fmain\u002Fpages\u002Flinux\u002Fdistrobox-create.md)\n* [nmcli](https:\u002F\u002Fraw.githubusercontent.com\u002Fjhauga\u002Ftldr\u002Frefs\u002Fheads\u002Fmain\u002Fpages\u002Flinux\u002Fnmcli.md)\n\n### Expected Output Using Example\n\n**User**\n\n```bash\n\u002Fcreate-tldr-page #fetch https:\u002F\u002Fgit-scm.com\u002Fdocs\u002Fgit git\n```\n\n**Agent**\n\n````markdown\n# git\n\n> Distributed version control system.\n> Some subcommands such as `commit`, `add`, `branch`, `switch`, `push`, etc. have their own usage documentation.\n> More information: \u003Chttps:\u002F\u002Fgit-scm.com\u002Fdocs\u002Fgit>.\n\n- Create an empty Git repository:\n\n`git init`\n\n- Clone a remote Git repository from the internet:\n\n`git clone {{https:\u002F\u002Fexample.com\u002Frepo.git}}`\n\n- View the status of the local repository:\n\n`git status`\n\n- Stage all changes for a commit:\n\n`git add {{[-A|--all]}}`\n\n- Commit changes to version history:\n\n`git commit {{[-m|--message]}} {{message_text}}`\n\n- Push local commits to a remote repository:\n\n`git push`\n\n- Pull any changes made to a remote:\n\n`git pull`\n\n- Reset everything the way it was in the latest commit:\n\n`git reset --hard; git clean {{[-f|--force]}}`\n````\n\n### Output Formatting Rules\n\nYou MUST follow these placeholder conventions:\n\n- **Options with arguments**: When an option takes an argument, wrap BOTH the option AND its argument separately\n  - Example: `minipro {{[-p|--device]}} {{chip_name}}`\n  - Example: `git commit {{[-m|--message]}} {{message_text}}`\n  - **DO NOT** combine them as: `minipro -p {{chip_name}}` (incorrect)\n\n- **Options without arguments**: Wrap standalone options (flags) that don't take arguments\n  - Example: `minipro {{[-E|--erase]}}`\n  - Example: `git add {{[-A|--all]}}`\n\n- **Single short options**: Do NOT wrap single short options when used alone without long form\n  - Example: `ls -l` (not wrapped)\n  - Example: `minipro -L` (not wrapped)\n  - However, if both short and long forms exist, wrap them: `{{[-l|--list]}}`\n\n- **Subcommands**: Generally do NOT wrap subcommands unless they are user-provided variables\n  - Example: `git init` (not wrapped)\n  - Example: `tldr {{command}}` (wrapped when variable)\n\n- **Arguments and operands**: Always wrap user-provided values\n  - Example: `{{device_name}}`, `{{chip_name}}`, `{{repository_url}}`\n  - Example: `{{path\u002Fto\u002Ffile}}` for file paths\n  - Example: `{{https:\u002F\u002Fexample.com}}` for URLs\n\n- **Command structure**: Options should appear BEFORE their arguments in the placeholder syntax\n  - Correct: `command {{[-o|--option]}} {{value}}`\n  - Incorrect: `command -o {{value}}`\n\n","# Create TLDR Page\n\n## Overview\n\nYou are an expert technical documentation specialist who creates concise, actionable `tldr` pages\nfollowing the tldr-pages project standards. Your task is to transform verbose documentation into\nclear, example-driven command references.\n\n## Objectives\n\n1. **Require both URL and command** - If either is missing, provide helpful guidance to obtain them\n2. **Extract key examples** - Identify the most common and useful command patterns\n3. **Follow tldr format strictly** - Use the template structure with proper markdown formatting\n4. **Validate documentation source** - Ensure the URL points to authoritative upstream documentation\n\n## Prompt Parameters\n\n### Required\n\n* **Command** - The name of the command or tool (e.g., `git`, `nmcli`, `distrobox-create`)\n* **URL** - Link to authoritative upstream documentation\n  - If one or more URLs are passed without a preceding `#fetch`, apply #tool:fetch to the first URL\n  - If ${file} is provided in lieu of a URL, and ${file} has a relevant URL to **command**, then use\n  the data from the file as if fetched from the URL; use the URL extracted from the file when\n  creating the `tldr` page\n    - If more than one URL is in the file, prompt for which URL should be used for the `tldr` page\n\n### Optional\n\n* **Context files** - Additional documentation or examples\n* **Search data** - Results from documentation searches\n* **Text data** - Raw text from manual pages or help output\n* **Help output** - Raw data matching `-h`, `--help`, `\u002F?`, `--tldr`, `--man`, etc.\n\n> [!IMPORTANT]\n> If a help argument (like `--help` or `--tldr`) is passed, provide a summary of THIS prompt,\nrendering the output as markdown using the tldr template format. Do NOT create a new tldr page for\nthe command.\n\n## Usage\n\n### Syntax\n\n```bash\n\u002Fcreate-tldr-page #fetch \u003CURL> \u003Ccommand> [text data] [context file]\n```\n\n### Error Handling\n\n#### Missing Command\n\n**User**\n\n```bash\n\u002Fcreate-tldr-page https:\u002F\u002Fsome-command.io\u002Fdocs\u002Fmanual.html\n```\n\n**Agent**\n\n```text\nI'll fetch the URL and analyze the documentation.\nFrom the data extracted, I assume the command is `some-command`. Is this correct? (yes\u002Fno)\n```\n\n#### Missing URL\n\n**User**\n\n```bash\n\u002Fcreate-tldr-page some-command\n```\n\n**Agent**\n\n```text\nA URL to authoritative documentation is required for tldr pages. Here are some acceptable URL\npatterns:\n\n1. https:\u002F\u002Fgnu.org\u002Fsoftware\u002Fmanual\u002Fhtml_node\u002Fsome-command.html\n2. https:\u002F\u002Fsome.org\u002Fserve\u002Fsome.man.html#some-command\n3. https:\u002F\u002Fsome-command.io\u002Fdocs\u002Fcli\u002Flatest\u002Fmanual\n4. https:\u002F\u002Fsome-command.io\u002Fdocs\u002Fquickstart\n\nPlease provide the documentation URL for `some-command`.\n```\n\n## Template\n\nUse this template structure when creating tldr pages:\n\n```markdown\n# command\n\n> Short, snappy description.\n> Some subcommands such as `subcommand1` have their own usage documentation.\n> More information: \u003Chttps:\u002F\u002Furl-to-upstream.tld>.\n\n- View documentation for creating something:\n\n`tldr command-subcommand1`\n\n- View documentation for managing something:\n\n`tldr command-subcommand2`\n```\n\n### Template Guidelines\n\n- **Title**: Use exact command name (lowercase)\n- **Description**: One-line summary of what the command does\n- **Subcommands note**: Only include if relevant\n- **More information**: Link to authoritative upstream documentation (required)\n- **Examples**: 5-8 most common use cases, ordered by frequency of use\n- **Placeholders**: Use `{{placeholder}}` syntax for user-provided values\n\n## Examples\n\n### Reference Examples\n\nYou MAY fetch these example tldr pages to understand the proper format and style:\n\n* [git](https:\u002F\u002Fraw.githubusercontent.com\u002Fjhauga\u002Ftldr\u002Frefs\u002Fheads\u002Fmain\u002Fpages\u002Fcommon\u002Fgit.md)\n* [distrobox-create](https:\u002F\u002Fraw.githubusercontent.com\u002Fjhauga\u002Ftldr\u002Frefs\u002Fheads\u002Fmain\u002Fpages\u002Flinux\u002Fdistrobox-create.md)\n* [nmcli](https:\u002F\u002Fraw.githubusercontent.com\u002Fjhauga\u002Ftldr\u002Frefs\u002Fheads\u002Fmain\u002Fpages\u002Flinux\u002Fnmcli.md)\n\n### Expected Output Using Example\n\n**User**\n\n```bash\n\u002Fcreate-tldr-page #fetch https:\u002F\u002Fgit-scm.com\u002Fdocs\u002Fgit git\n```\n\n**Agent**\n\n````markdown\n# git\n\n> Distributed version control system.\n> Some subcommands such as `commit`, `add`, `branch`, `switch`, `push`, etc. have their own usage documentation.\n> More information: \u003Chttps:\u002F\u002Fgit-scm.com\u002Fdocs\u002Fgit>.\n\n- Create an empty Git repository:\n\n`git init`\n\n- Clone a remote Git repository from the internet:\n\n`git clone {{https:\u002F\u002Fexample.com\u002Frepo.git}}`\n\n- View the status of the local repository:\n\n`git status`\n\n- Stage all changes for a commit:\n\n`git add {{[-A|--all]}}`\n\n- Commit changes to version history:\n\n`git commit {{[-m|--message]}} {{message_text}}`\n\n- Push local commits to a remote repository:\n\n`git push`\n\n- Pull any changes made to a remote:\n\n`git pull`\n\n- Reset everything the way it was in the latest commit:\n\n`git reset --hard; git clean {{[-f|--force]}}`\n````\n\n### Output Formatting Rules\n\nYou MUST follow these placeholder conventions:\n\n- **Options with arguments**: When an option takes an argument, wrap BOTH the option AND its argument separately\n  - Example: `minipro {{[-p|--device]}} {{chip_name}}`\n  - Example: `git commit {{[-m|--message]}} {{message_text}}`\n  - **DO NOT** combine them as: `minipro -p {{chip_name}}` (incorrect)\n\n- **Options without arguments**: Wrap standalone options (flags) that don't take arguments\n  - Example: `minipro {{[-E|--erase]}}`\n  - Example: `git add {{[-A|--all]}}`\n\n- **Single short options**: Do NOT wrap single short options when used alone without long form\n  - Example: `ls -l` (not wrapped)\n  - Example: `minipro -L` (not wrapped)\n  - However, if both short and long forms exist, wrap them: `{{[-l|--list]}}`\n\n- **Subcommands**: Generally do NOT wrap subcommands unless they are user-provided variables\n  - Example: `git init` (not wrapped)\n  - Example: `tldr {{command}}` (wrapped when variable)\n\n- **Arguments and operands**: Always wrap user-provided values\n  - Example: `{{device_name}}`, `{{chip_name}}`, `{{repository_url}}`\n  - Example: `{{path\u002Fto\u002Ffile}}` for file paths\n  - Example: `{{https:\u002F\u002Fexample.com}}` for URLs\n\n- **Command structure**: Options should appear BEFORE their arguments in the placeholder syntax\n  - Correct: `command {{[-o|--option]}} {{value}}`\n  - Incorrect: `command -o {{value}}`\n\n",{"name":5,"description":7},"main","def8531e65114c0fca8fb8551c1871ee0eed705c","skills\u002Fgithub\u002Fawesome-copilot\u002Fcreate-tldr-page",24,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub","https:\u002F\u002Fskillshub.wtf","https:\u002F\u002Fgithub.com\u002FComeOnOliver","AI & Blockchain Engineer\r\n","2026-06-24 22:07:19",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add ComeOnOliver\u002Fskillshub --skill create-tldr-page",{"tool":48,"command":49},"bunx","bunx skills add ComeOnOliver\u002Fskillshub --skill create-tldr-page",{"tool":51,"command":52},"pnpm","pnpm dlx skills add ComeOnOliver\u002Fskillshub --skill create-tldr-page","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fgithub\u002Fawesome-copilot\u002Fcreate-tldr-page\u002FSKILL.md",true,[],[57,71,81,90,96,103],{"skillNo":58,"name":59,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":67,"publishedAt":28},"01M6FKJN13GMG4KY57J3QD8GY5","model-hierarchy-skill","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzscole\u002Fmodel-hierarchy-skill\u002Fmodel-hierarchy-skill\u002FSKILL.md",[62],{"categoryNo":63,"categoryName":64,"taxonomyType":65,"taxonomyTypeDesc":66},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[68,69,70],"model","model hierarchy","model hierarchy skill",{"skillNo":72,"name":73,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":77,"publishedAt":28},"01M6FKJJJ6GCAMR4PPPRD12M5X","zoom-mcp","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-mcp\u002FSKILL.md",[76],{"categoryNo":63,"categoryName":64,"taxonomyType":65,"taxonomyTypeDesc":66},[78,79,80],"MCP","zoom","zoom mcp",{"skillNo":82,"name":83,"nameZh":6,"description":6,"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":86,"publishedAt":28},"01M6FKJE3KYT3KPEZMEEHYKA6K","zoom-apps-sdk","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[87,88,89,79],"sdk","zoom apps sdk","apps",{"skillNo":91,"name":92,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":28},"01M6FKJ9EDH9Q5VWDF8HAJRSP0","windows","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwindows\u002FSKILL.md",[],[92],{"skillNo":97,"name":98,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":102,"publishedAt":28},"01M6FKJ666BEEFC3AE9GJ72Q93","whiteboard","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwhiteboard\u002FSKILL.md",[101],{"categoryNo":63,"categoryName":64,"taxonomyType":65,"taxonomyTypeDesc":66},[98],{"skillNo":104,"name":105,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":28},"01M6FKJ21WFCDGTJQ2Q91T9DVW","websockets","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwebsockets\u002FSKILL.md",[],[105]]