[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7361FSWFQ3MDFT867VWTXDF":3,"skill-same:01M7361FSWFQ3MDFT867VWTXDF":51},{"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":29,"updatedAt":30,"install":31,"resources":44},"01M7361FSWFQ3MDFT867VWTXDF","docs-writer",null,"Always use this skill when the task involves writing, reviewing, or editing files in the `\u002Fdocs` directory or any `.md` files in the repository.","Diogo17\u002Fgemini-cli","Diogo17","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F30201684?v=4","01M72W4JV7R6BXQK8JDAE25JEP","Diogo Mota","01M73616ER2AY6F2XTHSMP18TE",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FDiogo17\u002Fgemini-cli\u002Fblob\u002Fabhi\u002Fsession-browser-refactor.5\u002F.gemini\u002Fskills\u002Fdocs-writer\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: docs-writer\ndescription:\n  Always use this skill when the task involves writing, reviewing, or editing \n  files in the `\u002Fdocs` directory or any `.md` files in the repository.\n---\n\n# `docs-writer` skill instructions\n\nAs an expert technical writer and editor for the Gemini CLI project, you produce\naccurate, clear, and consistent documentation. When asked to write, edit, or\nreview documentation, you must ensure the content strictly adheres to the\nprovided documentation standards and accurately reflects the current codebase.\nAdhere to the contribution process in `CONTRIBUTING.md` and the following\nproject standards.\n\n## Phase 1: Documentation standards\n\nAdhering to these principles and standards when writing, editing, and reviewing.\n\n### Voice and tone\nAdopt a tone that balances professionalism with a helpful, conversational\napproach.\n\n- **Perspective and tense:** Address the reader as \"you.\" Use active voice and\n  present tense (e.g., \"The API returns...\").\n- **Tone:** Professional, friendly, and direct. \n- **Clarity:** Use simple vocabulary. Avoid jargon, slang, and marketing hype.\n- **Global Audience:** Write in standard US English. Avoid idioms and cultural\n  references.\n- **Requirements:** Be clear about requirements (\"must\") vs. recommendations\n  (\"we recommend\"). Avoid \"should.\"\n- **Word Choice:** Avoid \"please\" and anthropomorphism (e.g., \"the server\n  thinks\"). Use contractions (don't, it's).\n\n### Language and grammar\nWrite precisely to ensure your instructions are unambiguous.\n\n- **Abbreviations:** Avoid Latin abbreviations; use \"for example\" (not \"e.g.\")\n  and \"that is\" (not \"i.e.\").\n- **Punctuation:** Use the serial comma. Place periods and commas inside\n  quotation marks.\n- **Dates:** Use unambiguous formats (e.g., \"January 22, 2026\").\n- **Conciseness:** Use \"lets you\" instead of \"allows you to.\" Use precise,\n  specific verbs.\n- **Examples:** Use meaningful names in examples; avoid placeholders like\n  \"foo\" or \"bar.\"\n- **Quota and limit terminology:** For any content involving resource capacity\n  or using the word \"quota\" or \"limit\", strictly adhere to the guidelines in\n  the `quota-limit-style-guide.md` resource file. Generally, Use \"quota\" for the\n  administrative bucket and \"limit\" for the numerical ceiling.\n\n### Formatting and syntax\nApply consistent formatting to make documentation visually organized and\naccessible.\n\n- **Overview paragraphs:** Every heading must be followed by at least one\n  introductory overview paragraph before any lists or sub-headings.\n- **Text wrap:** Wrap text at 80 characters (except long links or tables).\n- **Casing:** Use sentence case for headings, titles, and bolded text.\n- **Naming:** Always refer to the project as `Gemini CLI` (never\n  `the Gemini CLI`).\n- **Lists:** Use numbered lists for sequential steps and bulleted lists\n  otherwise. Keep list items parallel in structure.\n- **UI and code:** Use **bold** for UI elements and `code font` for filenames,\n  snippets, commands, and API elements. Focus on the task when discussing\n  interaction.\n- **Links:** Use descriptive anchor text; avoid \"click here.\" Ensure the link\n  makes sense out of context.\n- **Accessibility:** Use semantic HTML elements correctly (headings, lists, \n  tables).\n- **Media:** Use lowercase hyphenated filenames. Provide descriptive alt text\n  for all images.\n\n### Structure\n- **BLUF:** Start with an introduction explaining what to expect.\n- **Experimental features:** If a feature is clearly noted as experimental,\nadd the following note immediately after the introductory paragraph:\n  `> **Note:** This is a preview feature currently under active development.`\n- **Headings:** Use hierarchical headings to support the user journey.\n- **Procedures:** \n  - Introduce lists of steps with a complete sentence.\n  - Start each step with an imperative verb.\n  - Number sequential steps; use bullets for non-sequential lists.\n  - Put conditions before instructions (e.g., \"On the Settings page, click...\").\n  - Provide clear context for where the action takes place.\n  - Indicate optional steps clearly (e.g., \"Optional: ...\").\n- **Elements:** Use bullet lists, tables, notes (`> **Note:**`), and warnings \n  (`> **Warning:**`).\n- **Avoid using a table of contents:** If a table of contents is present, remove\n  it.\n- **Next steps:** Conclude with a \"Next steps\" section if applicable.\n\n## Phase 2: Preparation\nBefore modifying any documentation, thoroughly investigate the request and the\nsurrounding context. \n\n1.  **Clarify:** Understand the core request. Differentiate between writing new\n    content and editing existing content. If the request is ambiguous (e.g.,\n    \"fix the docs\"), ask for clarification.\n2.  **Investigate:** Examine relevant code (primarily in `packages\u002F`) for\n    accuracy.\n3.  **Audit:** Read the latest versions of relevant files in `docs\u002F`.\n4.  **Connect:** Identify all referencing pages if changing behavior. Check if\n    `docs\u002Fsidebar.json` needs updates.\n5.  **Plan:** Create a step-by-step plan before making changes.\n\n## Phase 3: Execution\nImplement your plan by either updating existing files or creating new ones\nusing the appropriate file system tools. Use `replace` for small edits and\n`write_file` for new files or large rewrites.\n\n### Editing existing documentation\nFollow these additional steps when asked to review or update existing\ndocumentation.\n\n- **Gaps:** Identify areas where the documentation is incomplete or no longer\n  reflects existing code.\n- **Structure:** Apply \"Structure (New Docs)\" rules (BLUF, headings, etc.) when \n  adding new sections to existing pages.\n- **Headers**: If you change a header, you must check for links that lead to\n  that header and update them.\n- **Tone:** Ensure the tone is active and engaging. Use \"you\" and contractions.\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 edited\n  documents.\n\n\n## Phase 4: Verification and finalization\nPerform a final quality check to ensure that all changes are correctly formatted\nand that all links are functional.\n\n1.  **Accuracy:** Ensure content accurately reflects the implementation and\n  technical behavior.\n2.  **Self-review:** Re-read changes for formatting, correctness, and flow.\n3.  **Link check:** Verify all new and existing links leading to or from modified\n    pages. If you changed a header, ensure that any links that lead to it are\n    updated.\n4.  **Format:** Once all changes are complete, ask to execute `npm run format`\n    to ensure consistent formatting across the project. If the user confirms,\n    execute the command.\n","# `docs-writer` skill instructions\n\nAs an expert technical writer and editor for the Gemini CLI project, you produce\naccurate, clear, and consistent documentation. When asked to write, edit, or\nreview documentation, you must ensure the content strictly adheres to the\nprovided documentation standards and accurately reflects the current codebase.\nAdhere to the contribution process in `CONTRIBUTING.md` and the following\nproject standards.\n\n## Phase 1: Documentation standards\n\nAdhering to these principles and standards when writing, editing, and reviewing.\n\n### Voice and tone\nAdopt a tone that balances professionalism with a helpful, conversational\napproach.\n\n- **Perspective and tense:** Address the reader as \"you.\" Use active voice and\n  present tense (e.g., \"The API returns...\").\n- **Tone:** Professional, friendly, and direct. \n- **Clarity:** Use simple vocabulary. Avoid jargon, slang, and marketing hype.\n- **Global Audience:** Write in standard US English. Avoid idioms and cultural\n  references.\n- **Requirements:** Be clear about requirements (\"must\") vs. recommendations\n  (\"we recommend\"). Avoid \"should.\"\n- **Word Choice:** Avoid \"please\" and anthropomorphism (e.g., \"the server\n  thinks\"). Use contractions (don't, it's).\n\n### Language and grammar\nWrite precisely to ensure your instructions are unambiguous.\n\n- **Abbreviations:** Avoid Latin abbreviations; use \"for example\" (not \"e.g.\")\n  and \"that is\" (not \"i.e.\").\n- **Punctuation:** Use the serial comma. Place periods and commas inside\n  quotation marks.\n- **Dates:** Use unambiguous formats (e.g., \"January 22, 2026\").\n- **Conciseness:** Use \"lets you\" instead of \"allows you to.\" Use precise,\n  specific verbs.\n- **Examples:** Use meaningful names in examples; avoid placeholders like\n  \"foo\" or \"bar.\"\n- **Quota and limit terminology:** For any content involving resource capacity\n  or using the word \"quota\" or \"limit\", strictly adhere to the guidelines in\n  the `quota-limit-style-guide.md` resource file. Generally, Use \"quota\" for the\n  administrative bucket and \"limit\" for the numerical ceiling.\n\n### Formatting and syntax\nApply consistent formatting to make documentation visually organized and\naccessible.\n\n- **Overview paragraphs:** Every heading must be followed by at least one\n  introductory overview paragraph before any lists or sub-headings.\n- **Text wrap:** Wrap text at 80 characters (except long links or tables).\n- **Casing:** Use sentence case for headings, titles, and bolded text.\n- **Naming:** Always refer to the project as `Gemini CLI` (never\n  `the Gemini CLI`).\n- **Lists:** Use numbered lists for sequential steps and bulleted lists\n  otherwise. Keep list items parallel in structure.\n- **UI and code:** Use **bold** for UI elements and `code font` for filenames,\n  snippets, commands, and API elements. Focus on the task when discussing\n  interaction.\n- **Links:** Use descriptive anchor text; avoid \"click here.\" Ensure the link\n  makes sense out of context.\n- **Accessibility:** Use semantic HTML elements correctly (headings, lists, \n  tables).\n- **Media:** Use lowercase hyphenated filenames. Provide descriptive alt text\n  for all images.\n\n### Structure\n- **BLUF:** Start with an introduction explaining what to expect.\n- **Experimental features:** If a feature is clearly noted as experimental,\nadd the following note immediately after the introductory paragraph:\n  `> **Note:** This is a preview feature currently under active development.`\n- **Headings:** Use hierarchical headings to support the user journey.\n- **Procedures:** \n  - Introduce lists of steps with a complete sentence.\n  - Start each step with an imperative verb.\n  - Number sequential steps; use bullets for non-sequential lists.\n  - Put conditions before instructions (e.g., \"On the Settings page, click...\").\n  - Provide clear context for where the action takes place.\n  - Indicate optional steps clearly (e.g., \"Optional: ...\").\n- **Elements:** Use bullet lists, tables, notes (`> **Note:**`), and warnings \n  (`> **Warning:**`).\n- **Avoid using a table of contents:** If a table of contents is present, remove\n  it.\n- **Next steps:** Conclude with a \"Next steps\" section if applicable.\n\n## Phase 2: Preparation\nBefore modifying any documentation, thoroughly investigate the request and the\nsurrounding context. \n\n1.  **Clarify:** Understand the core request. Differentiate between writing new\n    content and editing existing content. If the request is ambiguous (e.g.,\n    \"fix the docs\"), ask for clarification.\n2.  **Investigate:** Examine relevant code (primarily in `packages\u002F`) for\n    accuracy.\n3.  **Audit:** Read the latest versions of relevant files in `docs\u002F`.\n4.  **Connect:** Identify all referencing pages if changing behavior. Check if\n    `docs\u002Fsidebar.json` needs updates.\n5.  **Plan:** Create a step-by-step plan before making changes.\n\n## Phase 3: Execution\nImplement your plan by either updating existing files or creating new ones\nusing the appropriate file system tools. Use `replace` for small edits and\n`write_file` for new files or large rewrites.\n\n### Editing existing documentation\nFollow these additional steps when asked to review or update existing\ndocumentation.\n\n- **Gaps:** Identify areas where the documentation is incomplete or no longer\n  reflects existing code.\n- **Structure:** Apply \"Structure (New Docs)\" rules (BLUF, headings, etc.) when \n  adding new sections to existing pages.\n- **Headers**: If you change a header, you must check for links that lead to\n  that header and update them.\n- **Tone:** Ensure the tone is active and engaging. Use \"you\" and contractions.\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 edited\n  documents.\n\n\n## Phase 4: Verification and finalization\nPerform a final quality check to ensure that all changes are correctly formatted\nand that all links are functional.\n\n1.  **Accuracy:** Ensure content accurately reflects the implementation and\n  technical behavior.\n2.  **Self-review:** Re-read changes for formatting, correctness, and flow.\n3.  **Link check:** Verify all new and existing links leading to or from modified\n    pages. If you changed a header, ensure that any links that lead to it are\n    updated.\n4.  **Format:** Once all changes are complete, ask to execute `npm run format`\n    to ensure consistent formatting across the project. If the user confirms,\n    execute the command.\n",{"name":5,"description":7},"abhi\u002Fsession-browser-refactor.5","556861602ce23c5ea0e55835902e8aa6557d7898",".gemini\u002Fskills\u002Fdocs-writer","https:\u002F\u002Fgithub.com\u002FDiogo17\u002Fgemini-cli","https:\u002F\u002Fgithub.com\u002FDiogo17"," 🚀 Sobre Mim  \r\n\r\n👋 Olá! Sou Diogo Mota, designer, social media e copywriter apaixonado por marketing digital, lançamentos e estratégias políticas. ","2026-05-20 00:21:08",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Diogo17\u002Fgemini-cli --skill docs-writer",{"tool":37,"command":38},"bunx","bunx skills add Diogo17\u002Fgemini-cli --skill docs-writer",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Diogo17\u002Fgemini-cli --skill docs-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDiogo17\u002Fgemini-cli\u002Fblob\u002Fabhi\u002Fsession-browser-refactor.5\u002F.gemini\u002Fskills\u002Fdocs-writer\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"quota-limit-style-guide.md","REFERENCE","参考文档",2120,"https:\u002F\u002Fgithub.com\u002FDiogo17\u002Fgemini-cli\u002Fblob\u002Fabhi\u002Fsession-browser-refactor.5\u002F.gemini\u002Fskills\u002Fdocs-writer\u002Fquota-limit-style-guide.md",[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M73622273WNXSVXE8XKJK0FC","pirate-skill","Speak like a pirate.","https:\u002F\u002Fgithub.com\u002FDiogo17\u002Fgemini-cli\u002Fblob\u002Fabhi\u002Fsession-browser-refactor.5\u002Fpackages\u002Fsdk\u002Ftest-data\u002Fskills\u002Fpirate-skill\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7361YG8JAXGZ7MPX5DNARXW","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\u002FDiogo17\u002Fgemini-cli\u002Fblob\u002Fabhi\u002Fsession-browser-refactor.5\u002Fpackages\u002Fcore\u002Fsrc\u002Fskills\u002Fbuiltin\u002Fskill-creator\u002FSKILL.md",[],[],{"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":72,"publishedAt":19},"01M7361WFF0F2WG9FDXQ1RBY6G","greeter","A friendly greeter skill","https:\u002F\u002Fgithub.com\u002FDiogo17\u002Fgemini-cli\u002Fblob\u002Fabhi\u002Fsession-browser-refactor.5\u002Fpackages\u002Fcli\u002Fsrc\u002Fcommands\u002Fextensions\u002Fexamples\u002Fskills\u002Fskills\u002Fgreeter\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7361S7JXFMB7GBXJS1TBVHC","string-reviewer","Use this skill when asked to review text and user-facing strings within the codebase. It ensures that these strings follow rules on clarity, usefulness, brevity and style.","https:\u002F\u002Fgithub.com\u002FDiogo17\u002Fgemini-cli\u002Fblob\u002Fabhi\u002Fsession-browser-refactor.5\u002F.gemini\u002Fskills\u002Fstring-reviewer\u002FSKILL.md",[],[],{"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":86,"publishedAt":19},"01M7361QKNJHE3A2ZH07YCAT5Q","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\u002FDiogo17\u002Fgemini-cli\u002Fblob\u002Fabhi\u002Fsession-browser-refactor.5\u002F.gemini\u002Fskills\u002Fpr-creator\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7361MW3WPG8X17JSN1VD1YJ","pr-address-comments","Use this skill if the user asks you to help them address GitHub PR comments for their current branch of the Gemini CLI. Requires `gh` CLI tool.","https:\u002F\u002Fgithub.com\u002FDiogo17\u002Fgemini-cli\u002Fblob\u002Fabhi\u002Fsession-browser-refactor.5\u002F.gemini\u002Fskills\u002Fpr-address-comments\u002FSKILL.md",[],[]]