[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CYAE2T6H0Q8DZHXT38DFTY":3,"skill-same:01M6CYAE2T6H0Q8DZHXT38DFTY":131},{"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":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":6,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M6CYAE2T6H0Q8DZHXT38DFTY","docs-writer",null,"Use this skill when asked to write documentation (`\u002Fdocs` directory) for Gemini CLI.","PHNX3NT\u002Fexpert-lamp","PHNX3NT","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F236716966?v=4","01M6CYA8E2HXF66KTEZNYZKSCW","MILEHIGH-WORLD LLC.","01M6CYA8JJSD49EPCP2495JC7Y",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FPHNX3NT\u002Fexpert-lamp\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Fdocs-writer\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29],"docs","writer","docs writer","directory","cli","gemini","gemini cli","documentation","write","use","write documentation","2026-11-10 10:12:30",false,"---\nname: docs-writer\ndescription:\n  Use this skill when asked to write documentation (`\u002Fdocs` directory)\n  for Gemini CLI.\n---\n\n# `docs-writer` skill instructions\n\nAs an expert technical writer for the Gemini CLI project, your goal is to\nproduce documentation that is accurate, clear, and consistent with the project's\nstandards. You must adhere to the documentation contribution process outlined in\n`CONTRIBUTING.md` and the style guidelines from the Google Developer\nDocumentation Style Guide.\n\n## Step 1: Understand the goal and create a plan\n\n1.  **Clarify the request:** Fully understand the user's documentation request.\n    Identify the core feature, command, or concept that needs to be documented.\n2.  **Ask questions:** If the request is ambiguous or lacks detail, ask\n    clarifying questions. Don't invent or assume. It's better to ask than to\n    write incorrect documentation.\n3.  **Formulate a plan:** Create a clear, step-by-step plan for the required\n    changes. If requested or necessary, store this plan in a temporary file or\n    a file identified by the user.\n\n## Step 2: Investigate and gather information\n\n1.  **Read the code:** Thoroughly examine the relevant codebase, primarily within\n    the `packages\u002F` directory, to ensure your writing is backed by the\n    implementation.\n2.  **Identify files:** Locate the specific documentation files in the `docs\u002F`\n    directory that need to be modified. Always read the latest\n    version of a file before you begin to edit it.\n3.  **Check for connections:** Consider related documentation. If you add a new\n    page, check if `docs\u002Fsidebar.json` needs to be updated. If you change a\n    command's behavior, check for other pages that reference it. Make sure links\n    in these pages are up to date.\n\n## Step 3: Draft the documentation\n\n1.  **Follow the style guide:**\n    - Text must be wrapped at 80 characters. Exceptions are long links or\n      tables, unless otherwise stated by the user.\n    - Use sentence case for headings, titles, and bolded text.\n    - Address the reader as \"you\".\n    - Use contractions to keep the tone more casual.\n    - Use simple, direct, and active language and the present tense.\n    - Keep paragraphs short and focused.\n    - Always refer to Gemini CLI as `Gemini CLI`, never `the Gemini CLI`.\n2.  **Use `replace` and `write_file`:** Use the file system tools to apply your\n    planned changes precisely. For small edits, `replace` is preferred. For new\n    files or large rewrites, `write_file` is more appropriate.\n\n## Step 4: Verify and finalize\n\n1.  **Review your work:** After making changes, re-read the files to ensure the\n    documentation is well-formatted, content is correct and based on existing\n    code, and that all new links are valid.\n2.  **Offer to run npm format:** Once all changes are complete and the user\n    confirms they have no more requests, offer to run the project's formatting\n    script to ensure consistency. Propose the following command:\n    `npm run format`\n","# `docs-writer` skill instructions\n\nAs an expert technical writer for the Gemini CLI project, your goal is to\nproduce documentation that is accurate, clear, and consistent with the project's\nstandards. You must adhere to the documentation contribution process outlined in\n`CONTRIBUTING.md` and the style guidelines from the Google Developer\nDocumentation Style Guide.\n\n## Step 1: Understand the goal and create a plan\n\n1.  **Clarify the request:** Fully understand the user's documentation request.\n    Identify the core feature, command, or concept that needs to be documented.\n2.  **Ask questions:** If the request is ambiguous or lacks detail, ask\n    clarifying questions. Don't invent or assume. It's better to ask than to\n    write incorrect documentation.\n3.  **Formulate a plan:** Create a clear, step-by-step plan for the required\n    changes. If requested or necessary, store this plan in a temporary file or\n    a file identified by the user.\n\n## Step 2: Investigate and gather information\n\n1.  **Read the code:** Thoroughly examine the relevant codebase, primarily within\n    the `packages\u002F` directory, to ensure your writing is backed by the\n    implementation.\n2.  **Identify files:** Locate the specific documentation files in the `docs\u002F`\n    directory that need to be modified. Always read the latest\n    version of a file before you begin to edit it.\n3.  **Check for connections:** Consider related documentation. If you add a new\n    page, check if `docs\u002Fsidebar.json` needs to be updated. If you change a\n    command's behavior, check for other pages that reference it. Make sure links\n    in these pages are up to date.\n\n## Step 3: Draft the documentation\n\n1.  **Follow the style guide:**\n    - Text must be wrapped at 80 characters. Exceptions are long links or\n      tables, unless otherwise stated by the user.\n    - Use sentence case for headings, titles, and bolded text.\n    - Address the reader as \"you\".\n    - Use contractions to keep the tone more casual.\n    - Use simple, direct, and active language and the present tense.\n    - Keep paragraphs short and focused.\n    - Always refer to Gemini CLI as `Gemini CLI`, never `the Gemini CLI`.\n2.  **Use `replace` and `write_file`:** Use the file system tools to apply your\n    planned changes precisely. For small edits, `replace` is preferred. For new\n    files or large rewrites, `write_file` is more appropriate.\n\n## Step 4: Verify and finalize\n\n1.  **Review your work:** After making changes, re-read the files to ensure the\n    documentation is well-formatted, content is correct and based on existing\n    code, and that all new links are valid.\n2.  **Offer to run npm format:** Once all changes are complete and the user\n    confirms they have no more requests, offer to run the project's formatting\n    script to ensure consistency. Propose the following command:\n    `npm run format`\n",{"name":5,"description":7},"main","d6637d593ac7669a51a0dc38b6cdc0c1398897d2",".gemini\u002Fskills\u002Fdocs-writer",1,"https:\u002F\u002Fgithub.com\u002FPHNX3NT\u002Fexpert-lamp","https:\u002F\u002Fgithub.com\u002FPHNX3NT","MILEHIGH-WORLD LLC is an entertainment company that specializes in developing groundbreaking video games and stunning cinematic experiences.\r\n","2026-03-10 14:46:09",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add PHNX3NT\u002Fexpert-lamp --skill docs-writer",{"tool":49,"command":50},"bunx","bunx skills add PHNX3NT\u002Fexpert-lamp --skill docs-writer",{"tool":52,"command":53},"pnpm","pnpm dlx skills add PHNX3NT\u002Fexpert-lamp --skill docs-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPHNX3NT\u002Fexpert-lamp\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Fdocs-writer\u002FSKILL.md",true,[57,63,69,73,77,81,85,89,93,97,101,107,111,115,119,123,127],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"ATTRIBUTION.md","REFERENCE","参考文档",1401,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fjangtrinh\u002Fdesign-os-svg-animation\u002Fskills\u002Fes-tutorial-video\u002FATTRIBUTION.md",{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"build.mjs","SCRIPT","脚本",6502,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fjangtrinh\u002Fdesign-os-svg-animation\u002Fskills\u002Fes-tutorial-video\u002Fbuild.mjs",{"path":70,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":71,"sourceHtmlUrl":72},"concepts.md",3053,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fjangtrinh\u002Fdesign-os-svg-animation\u002Fskills\u002Fes-tutorial-video\u002Fconcepts.md",{"path":74,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":75,"sourceHtmlUrl":76},"contract.json",5963,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fjangtrinh\u002Fdesign-os-svg-animation\u002Fskills\u002Fes-tutorial-video\u002Fcontract.json",{"path":78,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":79,"sourceHtmlUrl":80},"examples\u002Fck-001.json",203,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fjangtrinh\u002Fdesign-os-svg-animation\u002Fskills\u002Fes-tutorial-video\u002Fexamples\u002Fck-001.json",{"path":82,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":83,"sourceHtmlUrl":84},"examples\u002Fdc-01.json",165,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fjangtrinh\u002Fdesign-os-svg-animation\u002Fskills\u002Fes-tutorial-video\u002Fexamples\u002Fdc-01.json",{"path":86,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":87,"sourceHtmlUrl":88},"kit-path.mjs",989,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fjangtrinh\u002Fdesign-os-svg-animation\u002Fskills\u002Fes-tutorial-video\u002Fkit-path.mjs",{"path":90,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":91,"sourceHtmlUrl":92},"look.md",2209,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fjangtrinh\u002Fdesign-os-svg-animation\u002Fskills\u002Fes-tutorial-video\u002Flook.md",{"path":94,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":95,"sourceHtmlUrl":96},"look.mjs",8488,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fjangtrinh\u002Fdesign-os-svg-animation\u002Fskills\u002Fes-tutorial-video\u002Flook.mjs",{"path":98,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":99,"sourceHtmlUrl":100},"rules.md",7273,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fjangtrinh\u002Fdesign-os-svg-animation\u002Fskills\u002Fes-tutorial-video\u002Frules.md",{"path":102,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":105,"sourceHtmlUrl":106},"templates\u002Fextract-evidence.py.tpl","OTHER","其他",1658,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fjangtrinh\u002Fdesign-os-svg-animation\u002Fskills\u002Fes-tutorial-video\u002Ftemplates\u002Fextract-evidence.py.tpl",{"path":108,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":109,"sourceHtmlUrl":110},"templates\u002Fproject-gitignore.tpl",299,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fjangtrinh\u002Fdesign-os-svg-animation\u002Fskills\u002Fes-tutorial-video\u002Ftemplates\u002Fproject-gitignore.tpl",{"path":112,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":113,"sourceHtmlUrl":114},"templates\u002Fscript-vi.json.tpl",321,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fjangtrinh\u002Fdesign-os-svg-animation\u002Fskills\u002Fes-tutorial-video\u002Ftemplates\u002Fscript-vi.json.tpl",{"path":116,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":117,"sourceHtmlUrl":118},"templates\u002Fstoryboard.md.tpl",930,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fjangtrinh\u002Fdesign-os-svg-animation\u002Fskills\u002Fes-tutorial-video\u002Ftemplates\u002Fstoryboard.md.tpl",{"path":120,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":121,"sourceHtmlUrl":122},"templates\u002Ftutorial-timeline.js.tpl",2111,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fjangtrinh\u002Fdesign-os-svg-animation\u002Fskills\u002Fes-tutorial-video\u002Ftemplates\u002Ftutorial-timeline.js.tpl",{"path":124,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":125,"sourceHtmlUrl":126},"templates\u002Ftutorial.config.json.tpl",668,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fjangtrinh\u002Fdesign-os-svg-animation\u002Fskills\u002Fes-tutorial-video\u002Ftemplates\u002Ftutorial.config.json.tpl",{"path":128,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":129,"sourceHtmlUrl":130},"validate.mjs",10183,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fjangtrinh\u002Fdesign-os-svg-animation\u002Fskills\u002Fes-tutorial-video\u002Fvalidate.mjs",[132,156,163,177],{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":143,"publishedAt":30},"01M6CYAMME96GY8DT0J4EVDFRP","skill-creator","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Gemini CLI's capabilities with specialized knowledge, workflows, or tool integrations.","https:\u002F\u002Fgithub.com\u002FPHNX3NT\u002Fexpert-lamp\u002Fblob\u002Fmain\u002Fpackages\u002Fcore\u002Fsrc\u002Fskills\u002Fbuiltin\u002Fskill-creator\u002FSKILL.md",[138],{"categoryNo":139,"categoryName":140,"taxonomyType":141,"taxonomyTypeDesc":142},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[144,145,23,24,25,146,147,148,149,150,151,152,153,154,155],"skill creator","capabilities","workflows","create","update","knowledge","tool","integrations","specialized","guide","new skill","existing skill",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":30},"01M6CYAJP657PQ895MY1023M6Y","greeter","A friendly greeter skill","https:\u002F\u002Fgithub.com\u002FPHNX3NT\u002Fexpert-lamp\u002Fblob\u002Fmain\u002Fpackages\u002Fcli\u002Fsrc\u002Fcommands\u002Fextensions\u002Fexamples\u002Fskills\u002Fskills\u002Fgreeter\u002FSKILL.md",[],[158],{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":30},"01M6CYAGR7MK719H99BBT6495D","pr-creator","Use this skill when asked to create a pull request (PR). It ensures all PRs follow the repository's established templates and standards.","https:\u002F\u002Fgithub.com\u002FPHNX3NT\u002Fexpert-lamp\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Fpr-creator\u002FSKILL.md",[],[170,171,28,172,173,174,175,147,176],"pr creator","pr","standards","templates","repository","pull","pull request",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":188,"publishedAt":30},"01M6CYABGZN5CEQDKBQQYBS4XD","code-reviewer","Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.","https:\u002F\u002Fgithub.com\u002FPHNX3NT\u002Fexpert-lamp\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Fcode-reviewer\u002FSKILL.md",[183],{"categoryNo":184,"categoryName":185,"taxonomyType":186,"taxonomyTypeDesc":187},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[189,190,191,192,193,194,195,172,28,196,175,197],"code","code reviewer","reviewer","review","maintainability","project","local","review code","pull requests"]