[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78D89E0P3CS3R0ZPSTFDA88":3,"skill-same:01M78D89E0P3CS3R0ZPSTFDA88":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":30,"commitSha":31,"skillDirectory":32,"forksCount":14,"repositoryHtmlUrl":33,"repositoryHomepageUrl":34,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M78D89E0P3CS3R0ZPSTFDA88","issues",null,"Interact with GitHub issues - create, list, and view issues.","princepatel04477-web\u002Ftrivoxa-group","princepatel04477-web","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F227740714?v=4","01M788ZAJ2KECD5KXVP55PZXKS","Prince Patel","01M788ZAJTCN8YSD737MRSKC5Q",0,"MIT","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fissues\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: issues\ndescription: Interact with GitHub issues - create, list, and view issues.\nallowed-tools: Bash(gh *)\nrisk: unknown\nsource: community\nmetadata:\n  author: Shpigford\n  version: \"1.0\"\n---\n\nInteract with GitHub issues - create, list, and view issues.\n\n## When to Use\n- The user wants to create, list, inspect, or otherwise work with GitHub issues.\n- The task involves issue intake or repository issue management through the GitHub CLI workflow.\n- You need a guided issue flow that gathers titles, descriptions, and action selection before running commands.\n\n## Instructions\n\nThis command helps you work with GitHub issues using the `gh` CLI.\n\n### Step 1: Determine Action\n\nUse AskUserQuestion to ask what the user wants to do:\n\n**Question:**\n- question: \"What would you like to do with GitHub issues?\"\n- header: \"Action\"\n- multiSelect: false\n- options:\n  - label: \"Create new issue\"\n    description: \"Open a new issue with title, body, and optional labels\"\n  - label: \"List issues\"\n    description: \"View open issues in the current repository\"\n  - label: \"View issue\"\n    description: \"See details of a specific issue by number\"\n\n---\n\n## If \"Create new issue\" selected:\n\n### Step 2a: Get Issue Title\n\nUse AskUserQuestion to get the issue title:\n\n**Question:**\n- question: \"What's a short, scannable title for this issue? Keep it brief (5-10 words max) - details go in the body. (Use 'Other' to type your title)\"\n- header: \"Title\"\n- multiSelect: false\n- options:\n  - label: \"I'll type a title\"\n    description: \"Enter a concise title like 'Login button unresponsive' or 'Add dark mode support'\"\n\n**Title guidelines:**\n- Keep titles SHORT and scannable (5-10 words max)\n- Good: \"Fix broken password reset flow\"\n- Bad: \"When I try to reset my password and click the button nothing happens and I get an error\"\n- The description\u002Fbody is where details belong, not the title\n\nIf the user provides a long title, help them shorten it and move the details to the body.\n\n### Step 3a: Get Issue Body\n\nUse AskUserQuestion to gather the issue body content:\n\n**Question 1 - Issue type context:**\n- question: \"What type of issue is this?\"\n- header: \"Type\"\n- multiSelect: false\n- options:\n  - label: \"Bug\"\n    description: \"Something broken that needs fixing\"\n  - label: \"Enhancement\"\n    description: \"Improvement to existing functionality\"\n  - label: \"New feature\"\n    description: \"Brand new functionality\"\n  - label: \"Task\"\n    description: \"General work item or chore\"\n\n**Question 2 - Description:**\n- question: \"Now provide the full details. This is where you explain context, background, and specifics that didn't fit in the title. (Use 'Other' to type your description)\"\n- header: \"Description\"\n- multiSelect: false\n- options:\n  - label: \"I'll describe it in detail\"\n    description: \"Provide context, steps, examples, and any relevant information\"\n\nThe user will select \"Other\" here to provide their full description.\n\n**Description guidelines:**\n- This is where ALL the detail goes - be thorough\n- Include context: what were you doing, what's the background?\n- Include specifics: error messages, URLs, versions, etc.\n- The more detail here, the better - unlike the title which should be brief\n\n**Question 3 - For bugs, ask about reproduction:**\nIf issue type is \"Bug\", use AskUserQuestion:\n\n- question: \"Can you provide steps to reproduce this bug? (Use 'Other' to type steps)\"\n- header: \"Repro steps\"\n- multiSelect: false\n- options:\n  - label: \"Provide steps\"\n    description: \"I'll describe how to reproduce the issue\"\n  - label: \"Not reproducible\"\n    description: \"The bug is intermittent or hard to reproduce\"\n\n**Question 4 - Expected vs actual behavior (for bugs):**\nIf issue type is \"Bug\", use AskUserQuestion:\n\n- question: \"What did you expect to happen vs what actually happened? (Use 'Other' to describe)\"\n- header: \"Behavior\"\n- multiSelect: false\n- options:\n  - label: \"Describe behavior\"\n    description: \"I'll explain expected vs actual behavior\"\n\n### Step 4a: Get Labels (Optional)\n\nUse AskUserQuestion to select labels:\n\n- question: \"Which labels should we add? (if any)\"\n- header: \"Labels\"\n- multiSelect: true\n- options:\n  - label: \"bug\"\n    description: \"Something isn't working\"\n  - label: \"enhancement\"\n    description: \"New feature or request\"\n  - label: \"documentation\"\n    description: \"Improvements to docs\"\n  - label: \"good first issue\"\n    description: \"Good for newcomers\"\n\n### Step 5a: Create the Issue\n\nConstruct the issue body based on the type:\n\n**For Bug reports:**\n```\n## Description\n[User's description]\n\n## Steps to Reproduce\n[User's reproduction steps or \"Not easily reproducible\"]\n\n## Expected Behavior\n[What should happen]\n\n## Actual Behavior\n[What actually happens]\n```\n\n**For Feature requests\u002FEnhancements:**\n```\n## Description\n[User's description]\n\n## Use Case\n[Why this would be useful]\n```\n\n**For Tasks\u002FOther:**\n```\n## Description\n[User's description]\n```\n\nRun the gh command to create the issue:\n```bash\ngh issue create --title \"[title]\" --body \"[constructed body]\" --label \"[labels]\"\n```\n\nReport the issue URL back to the user.\n\n---\n\n## If \"List issues\" selected:\n\n### Step 2b: Filter Options\n\nUse AskUserQuestion to determine filtering:\n\n- question: \"How would you like to filter issues?\"\n- header: \"Filter\"\n- multiSelect: false\n- options:\n  - label: \"All open issues\"\n    description: \"Show all open issues\"\n  - label: \"Assigned to me\"\n    description: \"Issues assigned to the current user\"\n  - label: \"Created by me\"\n    description: \"Issues I created\"\n  - label: \"With specific label\"\n    description: \"Filter by a label\"\n\nIf \"With specific label\" selected, use AskUserQuestion:\n\n- question: \"Which label to filter by? (Use 'Other' for custom label)\"\n- header: \"Label\"\n- multiSelect: false\n- options:\n  - label: \"bug\"\n    description: \"Bug reports\"\n  - label: \"enhancement\"\n    description: \"Feature requests\"\n  - label: \"documentation\"\n    description: \"Documentation issues\"\n\n### Step 3b: List Issues\n\nRun the appropriate gh command:\n- All open: `gh issue list`\n- Assigned to me: `gh issue list --assignee @me`\n- Created by me: `gh issue list --author @me`\n- With label: `gh issue list --label \"[label]\"`\n\nDisplay the results in a clean format.\n\n---\n\n## If \"View issue\" selected:\n\n### Step 2c: Get Issue Number\n\nUse AskUserQuestion:\n\n- question: \"Which issue number would you like to view? (Use 'Other' to enter the number)\"\n- header: \"Issue #\"\n- multiSelect: false\n- options:\n  - label: \"Enter issue number\"\n    description: \"I'll type the issue number\"\n\n### Step 3c: View Issue\n\nRun: `gh issue view [number]`\n\nDisplay the issue details including title, body, labels, assignees, and comments.\n\n---\n\n## Error Handling\n\nIf `gh` command fails:\n1. Check if user is authenticated: `gh auth status`\n2. If not authenticated, inform user to run `gh auth login`\n3. Check if in a git repository with a GitHub remote\n4. Report specific error message to user\n\n## Important Notes\n\n- **Titles should be succinct** (5-10 words) - if a user provides a long title, help shorten it and move details to body\n- **Bodies should be detailed** - encourage users to provide thorough context, steps, and specifics\n- Always confirm the issue was created successfully by showing the URL\n- For issue bodies, preserve user's formatting and newlines\n- If the user provides minimal information, that's okay - create the issue with what they gave\n- Use HEREDOC for the body to preserve formatting:\n  ```bash\n  gh issue create --title \"Title\" --body \"$(cat \u003C\u003C'EOF'\n  Body content here\n  EOF\n  )\"\n  ```\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","Interact with GitHub issues - create, list, and view issues.\n\n## When to Use\n- The user wants to create, list, inspect, or otherwise work with GitHub issues.\n- The task involves issue intake or repository issue management through the GitHub CLI workflow.\n- You need a guided issue flow that gathers titles, descriptions, and action selection before running commands.\n\n## Instructions\n\nThis command helps you work with GitHub issues using the `gh` CLI.\n\n### Step 1: Determine Action\n\nUse AskUserQuestion to ask what the user wants to do:\n\n**Question:**\n- question: \"What would you like to do with GitHub issues?\"\n- header: \"Action\"\n- multiSelect: false\n- options:\n  - label: \"Create new issue\"\n    description: \"Open a new issue with title, body, and optional labels\"\n  - label: \"List issues\"\n    description: \"View open issues in the current repository\"\n  - label: \"View issue\"\n    description: \"See details of a specific issue by number\"\n\n---\n\n## If \"Create new issue\" selected:\n\n### Step 2a: Get Issue Title\n\nUse AskUserQuestion to get the issue title:\n\n**Question:**\n- question: \"What's a short, scannable title for this issue? Keep it brief (5-10 words max) - details go in the body. (Use 'Other' to type your title)\"\n- header: \"Title\"\n- multiSelect: false\n- options:\n  - label: \"I'll type a title\"\n    description: \"Enter a concise title like 'Login button unresponsive' or 'Add dark mode support'\"\n\n**Title guidelines:**\n- Keep titles SHORT and scannable (5-10 words max)\n- Good: \"Fix broken password reset flow\"\n- Bad: \"When I try to reset my password and click the button nothing happens and I get an error\"\n- The description\u002Fbody is where details belong, not the title\n\nIf the user provides a long title, help them shorten it and move the details to the body.\n\n### Step 3a: Get Issue Body\n\nUse AskUserQuestion to gather the issue body content:\n\n**Question 1 - Issue type context:**\n- question: \"What type of issue is this?\"\n- header: \"Type\"\n- multiSelect: false\n- options:\n  - label: \"Bug\"\n    description: \"Something broken that needs fixing\"\n  - label: \"Enhancement\"\n    description: \"Improvement to existing functionality\"\n  - label: \"New feature\"\n    description: \"Brand new functionality\"\n  - label: \"Task\"\n    description: \"General work item or chore\"\n\n**Question 2 - Description:**\n- question: \"Now provide the full details. This is where you explain context, background, and specifics that didn't fit in the title. (Use 'Other' to type your description)\"\n- header: \"Description\"\n- multiSelect: false\n- options:\n  - label: \"I'll describe it in detail\"\n    description: \"Provide context, steps, examples, and any relevant information\"\n\nThe user will select \"Other\" here to provide their full description.\n\n**Description guidelines:**\n- This is where ALL the detail goes - be thorough\n- Include context: what were you doing, what's the background?\n- Include specifics: error messages, URLs, versions, etc.\n- The more detail here, the better - unlike the title which should be brief\n\n**Question 3 - For bugs, ask about reproduction:**\nIf issue type is \"Bug\", use AskUserQuestion:\n\n- question: \"Can you provide steps to reproduce this bug? (Use 'Other' to type steps)\"\n- header: \"Repro steps\"\n- multiSelect: false\n- options:\n  - label: \"Provide steps\"\n    description: \"I'll describe how to reproduce the issue\"\n  - label: \"Not reproducible\"\n    description: \"The bug is intermittent or hard to reproduce\"\n\n**Question 4 - Expected vs actual behavior (for bugs):**\nIf issue type is \"Bug\", use AskUserQuestion:\n\n- question: \"What did you expect to happen vs what actually happened? (Use 'Other' to describe)\"\n- header: \"Behavior\"\n- multiSelect: false\n- options:\n  - label: \"Describe behavior\"\n    description: \"I'll explain expected vs actual behavior\"\n\n### Step 4a: Get Labels (Optional)\n\nUse AskUserQuestion to select labels:\n\n- question: \"Which labels should we add? (if any)\"\n- header: \"Labels\"\n- multiSelect: true\n- options:\n  - label: \"bug\"\n    description: \"Something isn't working\"\n  - label: \"enhancement\"\n    description: \"New feature or request\"\n  - label: \"documentation\"\n    description: \"Improvements to docs\"\n  - label: \"good first issue\"\n    description: \"Good for newcomers\"\n\n### Step 5a: Create the Issue\n\nConstruct the issue body based on the type:\n\n**For Bug reports:**\n```\n## Description\n[User's description]\n\n## Steps to Reproduce\n[User's reproduction steps or \"Not easily reproducible\"]\n\n## Expected Behavior\n[What should happen]\n\n## Actual Behavior\n[What actually happens]\n```\n\n**For Feature requests\u002FEnhancements:**\n```\n## Description\n[User's description]\n\n## Use Case\n[Why this would be useful]\n```\n\n**For Tasks\u002FOther:**\n```\n## Description\n[User's description]\n```\n\nRun the gh command to create the issue:\n```bash\ngh issue create --title \"[title]\" --body \"[constructed body]\" --label \"[labels]\"\n```\n\nReport the issue URL back to the user.\n\n---\n\n## If \"List issues\" selected:\n\n### Step 2b: Filter Options\n\nUse AskUserQuestion to determine filtering:\n\n- question: \"How would you like to filter issues?\"\n- header: \"Filter\"\n- multiSelect: false\n- options:\n  - label: \"All open issues\"\n    description: \"Show all open issues\"\n  - label: \"Assigned to me\"\n    description: \"Issues assigned to the current user\"\n  - label: \"Created by me\"\n    description: \"Issues I created\"\n  - label: \"With specific label\"\n    description: \"Filter by a label\"\n\nIf \"With specific label\" selected, use AskUserQuestion:\n\n- question: \"Which label to filter by? (Use 'Other' for custom label)\"\n- header: \"Label\"\n- multiSelect: false\n- options:\n  - label: \"bug\"\n    description: \"Bug reports\"\n  - label: \"enhancement\"\n    description: \"Feature requests\"\n  - label: \"documentation\"\n    description: \"Documentation issues\"\n\n### Step 3b: List Issues\n\nRun the appropriate gh command:\n- All open: `gh issue list`\n- Assigned to me: `gh issue list --assignee @me`\n- Created by me: `gh issue list --author @me`\n- With label: `gh issue list --label \"[label]\"`\n\nDisplay the results in a clean format.\n\n---\n\n## If \"View issue\" selected:\n\n### Step 2c: Get Issue Number\n\nUse AskUserQuestion:\n\n- question: \"Which issue number would you like to view? (Use 'Other' to enter the number)\"\n- header: \"Issue #\"\n- multiSelect: false\n- options:\n  - label: \"Enter issue number\"\n    description: \"I'll type the issue number\"\n\n### Step 3c: View Issue\n\nRun: `gh issue view [number]`\n\nDisplay the issue details including title, body, labels, assignees, and comments.\n\n---\n\n## Error Handling\n\nIf `gh` command fails:\n1. Check if user is authenticated: `gh auth status`\n2. If not authenticated, inform user to run `gh auth login`\n3. Check if in a git repository with a GitHub remote\n4. Report specific error message to user\n\n## Important Notes\n\n- **Titles should be succinct** (5-10 words) - if a user provides a long title, help shorten it and move details to body\n- **Bodies should be detailed** - encourage users to provide thorough context, steps, and specifics\n- Always confirm the issue was created successfully by showing the URL\n- For issue bodies, preserve user's formatting and newlines\n- If the user provides minimal information, that's okay - create the issue with what they gave\n- Use HEREDOC for the body to preserve formatting:\n  ```bash\n  gh issue create --title \"Title\" --body \"$(cat \u003C\u003C'EOF'\n  Body content here\n  EOF\n  )\"\n  ```\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"metadata":26,"description":7,"allowed-tools":29},"unknown","community",{"author":27,"version":28},"Shpigford","1.0","Bash(gh *)","master","877653a671c51fae6476bd9f0d34ee6c408d68b9",".github\u002Fskills\u002Fissues","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group","https:\u002F\u002Ftrivoxa-group.vercel.app","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web","2026-08-01 17:29:31",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add princepatel04477-web\u002Ftrivoxa-group --skill issues",{"tool":43,"command":44},"bunx","bunx skills add princepatel04477-web\u002Ftrivoxa-group --skill issues",{"tool":46,"command":47},"pnpm","pnpm dlx skills add princepatel04477-web\u002Ftrivoxa-group --skill issues","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fissues\u002FSKILL.md",true,[],[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},"01M78G4Z5RFJ72G536XYPC77PG","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzustand-store-ts\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},"01M78G4WQMHRST36KDP7AV3NR3","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzoom-automation\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},"01M78G4T37F4SPS7M4KT0A8JJB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzoho-crm-automation\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},"01M78G4QAJMF71KD1G38MNDQYK","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzod-validation-expert\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},"01M78G4MS3WE96MH5P561KFY95","zipai-optimizer","Adaptive token optimizer: intelligent filtering, surgical output, ambiguity-first, context-window-aware, VCS-aware, MCP-aware.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzipai-optimizer\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},"01M78G4GZ0T47C6929V9CVH1AK","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[]]