[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78G6FFG3EAY46ASEJDKB4GV":3,"skill-same:01M78G6FFG3EAY46ASEJDKB4GV":50},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M78G6FFG3EAY46ASEJDKB4GV","docs-writer",null,"Use this skill for writing, reviewing, and editing documentation (`\u002Fdocs` directory or any .md file) for Gemini CLI.","prit90\u002Fgemini","prit90","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F154298643?v=4","01M78G6A16V26SJD3W56CV5TSE","Prit Pansuriya ","01M78G6A1Y0DWXC12B2CERKG9A",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fprit90\u002Fgemini\u002Fblob\u002Fadibakm\u002Fhandle-inconsistency-schedulers\u002F.gemini\u002Fskills\u002Fdocs-writer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: docs-writer\ndescription:\n  Use this skill for writing, reviewing, and editing documentation (`\u002Fdocs`\n  directory or any .md file) for Gemini CLI.\n---\n\n# `docs-writer` skill instructions\n\nAs an expert technical writer and editor for the Gemini CLI project, your goal\nis to produce and refine documentation that is accurate, clear, consistent, and\neasy for users to understand. You must adhere to the documentation contribution\nprocess outlined in `CONTRIBUTING.md`.\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 work.\n2.  **Differentiate the task:** Determine if the request is primarily for\n    **writing** new content or **editing** existing content. If the request is\n    ambiguous (e.g., \"fix the docs\"), ask the user for clarification.\n3.  **Formulate a plan:** Create a clear, step-by-step plan for the required\n    changes.\n\n## Step 2: Investigate and gather information\n\n1.  **Read the code:** Thoroughly examine the relevant codebase, primarily\n    within\n    the `packages\u002F` directory, to ensure your work is backed by the\n    implementation and to identify any gaps.\n2.  **Identify files:** Locate the specific documentation files in the `docs\u002F`\n    directory that need to be modified. Always read the latest version of a file\n    before you begin work.\n3.  **Check for connections:** Consider related documentation. If you change a\n    command's behavior, check for other pages that reference it. If you add a new\n    page, check if `docs\u002Fsidebar.json` needs to be updated. Make sure all\n    links are up to date.\n\n## Step 3: Write or edit the documentation\n\n1.  **Follow the style guide:** Adhere to the rules in\n    `references\u002Fstyle-guide.md`. Read this file to understand the project's\n    documentation standards.\n2.   Ensure the new documentation accurately reflects the features in the code.\n3.  **Use `replace` and `write_file`:** Use file system tools to apply your\n    planned changes. For small edits, `replace` is preferred. For new files or\n    large rewrites, `write_file` is more appropriate.\n\n\n\n### Sub-step: Editing existing documentation (as clarified in Step 1)\n\n-   **Gaps:** Identify areas where the documentation is incomplete or no longer\n    reflects existing code.\n-   **Tone:** Ensure the tone is active and engaging, not passive.\n-   **Clarity:** Correct awkward wording, spelling, and grammar. Rephrase\n    sentences to make them easier for users to understand.\n-   **Consistency:** Check for consistent terminology and style across all\n    edited documents.\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, and the content is correct based on\n    existing code.\n2.  **Link verification:** Verify the validity of all links in the new content.\n    Verify the validity of existing links leading to the page with the new\n    content or deleted content.\n2.  **Offer to run npm format:** Once all changes are complete, offer to run the\n    project's formatting script to ensure consistency by proposing the command:\n    `npm run format`\n","# `docs-writer` skill instructions\n\nAs an expert technical writer and editor for the Gemini CLI project, your goal\nis to produce and refine documentation that is accurate, clear, consistent, and\neasy for users to understand. You must adhere to the documentation contribution\nprocess outlined in `CONTRIBUTING.md`.\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 work.\n2.  **Differentiate the task:** Determine if the request is primarily for\n    **writing** new content or **editing** existing content. If the request is\n    ambiguous (e.g., \"fix the docs\"), ask the user for clarification.\n3.  **Formulate a plan:** Create a clear, step-by-step plan for the required\n    changes.\n\n## Step 2: Investigate and gather information\n\n1.  **Read the code:** Thoroughly examine the relevant codebase, primarily\n    within\n    the `packages\u002F` directory, to ensure your work is backed by the\n    implementation and to identify any gaps.\n2.  **Identify files:** Locate the specific documentation files in the `docs\u002F`\n    directory that need to be modified. Always read the latest version of a file\n    before you begin work.\n3.  **Check for connections:** Consider related documentation. If you change a\n    command's behavior, check for other pages that reference it. If you add a new\n    page, check if `docs\u002Fsidebar.json` needs to be updated. Make sure all\n    links are up to date.\n\n## Step 3: Write or edit the documentation\n\n1.  **Follow the style guide:** Adhere to the rules in\n    `references\u002Fstyle-guide.md`. Read this file to understand the project's\n    documentation standards.\n2.   Ensure the new documentation accurately reflects the features in the code.\n3.  **Use `replace` and `write_file`:** Use file system tools to apply your\n    planned changes. For small edits, `replace` is preferred. For new files or\n    large rewrites, `write_file` is more appropriate.\n\n\n\n### Sub-step: Editing existing documentation (as clarified in Step 1)\n\n-   **Gaps:** Identify areas where the documentation is incomplete or no longer\n    reflects existing code.\n-   **Tone:** Ensure the tone is active and engaging, not passive.\n-   **Clarity:** Correct awkward wording, spelling, and grammar. Rephrase\n    sentences to make them easier for users to understand.\n-   **Consistency:** Check for consistent terminology and style across all\n    edited documents.\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, and the content is correct based on\n    existing code.\n2.  **Link verification:** Verify the validity of all links in the new content.\n    Verify the validity of existing links leading to the page with the new\n    content or deleted content.\n2.  **Offer to run npm format:** Once all changes are complete, offer to run the\n    project's formatting script to ensure consistency by proposing the command:\n    `npm run format`\n",{"name":5,"description":7},"adibakm\u002Fhandle-inconsistency-schedulers","41d08b1196e717e6c4fb1c2b24d05133655c41f5",".gemini\u002Fskills\u002Fdocs-writer","https:\u002F\u002Fgithub.com\u002Fprit90\u002Fgemini","https:\u002F\u002Fgithub.com\u002Fprit90","2026-10-05 14:02:57",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add prit90\u002Fgemini --skill docs-writer",{"tool":36,"command":37},"bunx","bunx skills add prit90\u002Fgemini --skill docs-writer",{"tool":39,"command":40},"pnpm","pnpm dlx skills add prit90\u002Fgemini --skill docs-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprit90\u002Fgemini\u002Fblob\u002Fadibakm\u002Fhandle-inconsistency-schedulers\u002F.gemini\u002Fskills\u002Fdocs-writer\u002FSKILL.md",true,[44],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"references\u002Fstyle-guide.md","REFERENCE","参考文档",3999,"https:\u002F\u002Fgithub.com\u002Fprit90\u002Fgemini\u002Fblob\u002Fadibakm\u002Fhandle-inconsistency-schedulers\u002F.gemini\u002Fskills\u002Fdocs-writer\u002Freferences\u002Fstyle-guide.md",[51,58,65,72],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M78G6NF7XGWZZ6Y3ZM8HNBQY","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\u002Fprit90\u002Fgemini\u002Fblob\u002Fadibakm\u002Fhandle-inconsistency-schedulers\u002Fpackages\u002Fcore\u002Fsrc\u002Fskills\u002Fbuiltin\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M78G6MGS0FCNDMHXDFP8PDCN","greeter","A friendly greeter skill","https:\u002F\u002Fgithub.com\u002Fprit90\u002Fgemini\u002Fblob\u002Fadibakm\u002Fhandle-inconsistency-schedulers\u002Fpackages\u002Fcli\u002Fsrc\u002Fcommands\u002Fextensions\u002Fexamples\u002Fskills\u002Fskills\u002Fgreeter\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M78G6J3T8H0C8E2TVGN033CP","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\u002Fprit90\u002Fgemini\u002Fblob\u002Fadibakm\u002Fhandle-inconsistency-schedulers\u002F.gemini\u002Fskills\u002Fpr-creator\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M78G6CJZ7QWKRFN6R684MWZ2","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\u002Fprit90\u002Fgemini\u002Fblob\u002Fadibakm\u002Fhandle-inconsistency-schedulers\u002F.gemini\u002Fskills\u002Fcode-reviewer\u002FSKILL.md",[],[]]