[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75EW03K837D67FA84A7EXR0":3,"skill-same:01M75EW03K837D67FA84A7EXR0":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M75EW03K837D67FA84A7EXR0","jira-integration",null,"Use this skill when retrieving Jira tickets, analyzing requirements, updating ticket status, adding comments, or transitioning issues. Provides Jira API patterns via MCP or direct REST calls.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fjira-integration\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: jira-integration\ndescription: Use this skill when retrieving Jira tickets, analyzing requirements, updating ticket status, adding comments, or transitioning issues. Provides Jira API patterns via MCP or direct REST calls.\norigin: ECC\n---\n\n# Jira Integration Skill\n\nRetrieve, analyze, and update Jira tickets directly from your AI coding workflow. Supports both **MCP-based** (recommended) and **direct REST API** approaches.\n\n## When to Activate\n\n- Fetching a Jira ticket to understand requirements\n- Extracting testable acceptance criteria from a ticket\n- Adding progress comments to a Jira issue\n- Transitioning a ticket status (To Do → In Progress → Done)\n- Linking merge requests or branches to a Jira issue\n- Searching for issues by JQL query\n\n## Prerequisites\n\n### Option A: MCP Server (Recommended)\n\nInstall the `mcp-atlassian` MCP server. This exposes Jira tools directly to your AI agent.\n\n**Requirements:**\n- Python 3.10+\n- `uvx` (from `uv`), installed via your package manager or the official `uv` installation documentation\n\n**Add to your MCP config** (e.g., `~\u002F.claude.json` → `mcpServers`):\n\n```json\n{\n  \"jira\": {\n    \"command\": \"uvx\",\n    \"args\": [\"mcp-atlassian==0.21.0\"],\n    \"env\": {\n      \"JIRA_URL\": \"https:\u002F\u002FYOUR_ORG.atlassian.net\",\n      \"JIRA_EMAIL\": \"your.email@example.com\",\n      \"JIRA_API_TOKEN\": \"your-api-token\"\n    },\n    \"description\": \"Jira issue tracking — search, create, update, comment, transition\"\n  }\n}\n```\n\n> **Security:** Never hardcode secrets. Prefer setting `JIRA_URL`, `JIRA_EMAIL`, and `JIRA_API_TOKEN` in your system environment (or a secrets manager). Only use the MCP `env` block for local, uncommitted config files.\n\n**To get a Jira API token:**\n1. Go to \u003Chttps:\u002F\u002Fid.atlassian.com\u002Fmanage-profile\u002Fsecurity\u002Fapi-tokens>\n2. Click **Create API token**\n3. Copy the token — store it in your environment, never in source code\n\n### Option B: Direct REST API\n\nIf MCP is not available, use the Jira REST API v3 directly via `curl` or a helper script.\n\n**Required environment variables:**\n\n| Variable | Description |\n|----------|-------------|\n| `JIRA_URL` | Your Jira instance URL (e.g., `https:\u002F\u002Fyourorg.atlassian.net`) |\n| `JIRA_EMAIL` | Your Atlassian account email |\n| `JIRA_API_TOKEN` | API token from id.atlassian.com |\n\nStore these in your shell environment, secrets manager, or an untracked local env file. Do not commit them to the repo.\n\n## MCP Tools Reference\n\nWhen the `mcp-atlassian` MCP server is configured, these tools are available:\n\n| Tool | Purpose | Example |\n|------|---------|---------|\n| `jira_search` | JQL queries | `project = PROJ AND status = \"In Progress\"` |\n| `jira_get_issue` | Fetch full issue details by key | `PROJ-1234` |\n| `jira_create_issue` | Create issues (Task, Bug, Story, Epic) | New bug report |\n| `jira_update_issue` | Update fields (summary, description, assignee) | Change assignee |\n| `jira_transition_issue` | Change status | Move to \"In Review\" |\n| `jira_add_comment` | Add comments | Progress update |\n| `jira_get_sprint_issues` | List issues in a sprint | Active sprint review |\n| `jira_create_issue_link` | Link issues (Blocks, Relates to) | Dependency tracking |\n| `jira_get_issue_development_info` | See linked PRs, branches, commits | Dev context |\n\n> **Tip:** Always call `jira_get_transitions` before transitioning — transition IDs vary per project workflow.\n\n## Direct REST API Reference\n\n### Fetch a Ticket\n\n```bash\ncurl -s -u \"$JIRA_EMAIL:$JIRA_API_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  \"$JIRA_URL\u002Frest\u002Fapi\u002F3\u002Fissue\u002FPROJ-1234\" | jq '{\n    key: .key,\n    summary: .fields.summary,\n    status: .fields.status.name,\n    priority: .fields.priority.name,\n    type: .fields.issuetype.name,\n    assignee: .fields.assignee.displayName,\n    labels: .fields.labels,\n    description: .fields.description\n  }'\n```\n\n### Fetch Comments\n\n```bash\ncurl -s -u \"$JIRA_EMAIL:$JIRA_API_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  \"$JIRA_URL\u002Frest\u002Fapi\u002F3\u002Fissue\u002FPROJ-1234?fields=comment\" | jq '.fields.comment.comments[] | {\n    author: .author.displayName,\n    created: .created[:10],\n    body: .body\n  }'\n```\n\n### Add a Comment\n\n```bash\ncurl -s -X POST -u \"$JIRA_EMAIL:$JIRA_API_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"body\": {\n      \"version\": 1,\n      \"type\": \"doc\",\n      \"content\": [{\n        \"type\": \"paragraph\",\n        \"content\": [{\"type\": \"text\", \"text\": \"Your comment here\"}]\n      }]\n    }\n  }' \\\n  \"$JIRA_URL\u002Frest\u002Fapi\u002F3\u002Fissue\u002FPROJ-1234\u002Fcomment\"\n```\n\n### Transition a Ticket\n\n```bash\n# 1. Get available transitions\ncurl -s -u \"$JIRA_EMAIL:$JIRA_API_TOKEN\" \\\n  \"$JIRA_URL\u002Frest\u002Fapi\u002F3\u002Fissue\u002FPROJ-1234\u002Ftransitions\" | jq '.transitions[] | {id, name: .name}'\n\n# 2. Execute transition (replace TRANSITION_ID)\ncurl -s -X POST -u \"$JIRA_EMAIL:$JIRA_API_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"transition\": {\"id\": \"TRANSITION_ID\"}}' \\\n  \"$JIRA_URL\u002Frest\u002Fapi\u002F3\u002Fissue\u002FPROJ-1234\u002Ftransitions\"\n```\n\n### Search with JQL\n\n```bash\ncurl -s -G -u \"$JIRA_EMAIL:$JIRA_API_TOKEN\" \\\n  --data-urlencode \"jql=project = PROJ AND status = 'In Progress'\" \\\n  \"$JIRA_URL\u002Frest\u002Fapi\u002F3\u002Fsearch\"\n```\n\n## Analyzing a Ticket\n\nWhen retrieving a ticket for development or test automation, extract:\n\n### 1. Testable Requirements\n- **Functional requirements** — What the feature does\n- **Acceptance criteria** — Conditions that must be met\n- **Testable behaviors** — Specific actions and expected outcomes\n- **User roles** — Who uses this feature and their permissions\n- **Data requirements** — What data is needed\n- **Integration points** — APIs, services, or systems involved\n\n### 2. Test Types Needed\n- **Unit tests** — Individual functions and utilities\n- **Integration tests** — API endpoints and service interactions\n- **E2E tests** — User-facing UI flows\n- **API tests** — Endpoint contracts and error handling\n\n### 3. Edge Cases & Error Scenarios\n- Invalid inputs (empty, too long, special characters)\n- Unauthorized access\n- Network failures or timeouts\n- Concurrent users or race conditions\n- Boundary conditions\n- Missing or null data\n- State transitions (back navigation, refresh, etc.)\n\n### 4. Structured Analysis Output\n\n```\nTicket: PROJ-1234\nSummary: [ticket title]\nStatus: [current status]\nPriority: [High\u002FMedium\u002FLow]\nTest Types: Unit, Integration, E2E\n\nRequirements:\n1. [requirement 1]\n2. [requirement 2]\n\nAcceptance Criteria:\n- [ ] [criterion 1]\n- [ ] [criterion 2]\n\nTest Scenarios:\n- Happy Path: [description]\n- Error Case: [description]\n- Edge Case: [description]\n\nTest Data Needed:\n- [data item 1]\n- [data item 2]\n\nDependencies:\n- [dependency 1]\n- [dependency 2]\n```\n\n## Updating Tickets\n\n### When to Update\n\n| Workflow Step | Jira Update |\n|---|---|\n| Start work | Transition to \"In Progress\" |\n| Tests written | Comment with test coverage summary |\n| Branch created | Comment with branch name |\n| PR\u002FMR created | Comment with link, link issue |\n| Tests passing | Comment with results summary |\n| PR\u002FMR merged | Transition to \"Done\" or \"In Review\" |\n\n### Comment Templates\n\n**Starting Work:**\n```\nStarting implementation for this ticket.\nBranch: feat\u002FPROJ-1234-feature-name\n```\n\n**Tests Implemented:**\n```\nAutomated tests implemented:\n\nUnit Tests:\n- [test file 1] — [what it covers]\n- [test file 2] — [what it covers]\n\nIntegration Tests:\n- [test file] — [endpoints\u002Fflows covered]\n\nAll tests passing locally. Coverage: XX%\n```\n\n**PR Created:**\n```\nPull request created:\n[PR Title](https:\u002F\u002Fgithub.com\u002Forg\u002Frepo\u002Fpull\u002FXXX)\n\nReady for review.\n```\n\n**Work Complete:**\n```\nImplementation complete.\n\nPR merged: [link]\nTest results: All passing (X\u002FY)\nCoverage: XX%\n```\n\n## Security Guidelines\n\n- **Never hardcode** Jira API tokens in source code or skill files\n- **Always use** environment variables or a secrets manager\n- **Add `.env`** to `.gitignore` in every project\n- **Rotate tokens** immediately if exposed in git history\n- **Use least-privilege** API tokens scoped to required projects\n- **Validate** that credentials are set before making API calls — fail fast with a clear message\n\n## Troubleshooting\n\n| Error | Cause | Fix |\n|---|---|---|\n| `401 Unauthorized` | Invalid or expired API token | Regenerate at id.atlassian.com |\n| `403 Forbidden` | Token lacks project permissions | Check token scopes and project access |\n| `404 Not Found` | Wrong ticket key or base URL | Verify `JIRA_URL` and ticket key |\n| `spawn uvx ENOENT` | IDE cannot find `uvx` on PATH | Use full path (e.g., `~\u002F.local\u002Fbin\u002Fuvx`) or set PATH in `~\u002F.zprofile` |\n| Connection timeout | Network\u002FVPN issue | Check VPN connection and firewall rules |\n\n## Best Practices\n\n- Update Jira as you go, not all at once at the end\n- Keep comments concise but informative\n- Link rather than copy — point to PRs, test reports, and dashboards\n- Use @mentions if you need input from others\n- Check linked issues to understand full feature scope before starting\n- If acceptance criteria are vague, ask for clarification before writing code\n","# Jira Integration Skill\n\nRetrieve, analyze, and update Jira tickets directly from your AI coding workflow. Supports both **MCP-based** (recommended) and **direct REST API** approaches.\n\n## When to Activate\n\n- Fetching a Jira ticket to understand requirements\n- Extracting testable acceptance criteria from a ticket\n- Adding progress comments to a Jira issue\n- Transitioning a ticket status (To Do → In Progress → Done)\n- Linking merge requests or branches to a Jira issue\n- Searching for issues by JQL query\n\n## Prerequisites\n\n### Option A: MCP Server (Recommended)\n\nInstall the `mcp-atlassian` MCP server. This exposes Jira tools directly to your AI agent.\n\n**Requirements:**\n- Python 3.10+\n- `uvx` (from `uv`), installed via your package manager or the official `uv` installation documentation\n\n**Add to your MCP config** (e.g., `~\u002F.claude.json` → `mcpServers`):\n\n```json\n{\n  \"jira\": {\n    \"command\": \"uvx\",\n    \"args\": [\"mcp-atlassian==0.21.0\"],\n    \"env\": {\n      \"JIRA_URL\": \"https:\u002F\u002FYOUR_ORG.atlassian.net\",\n      \"JIRA_EMAIL\": \"your.email@example.com\",\n      \"JIRA_API_TOKEN\": \"your-api-token\"\n    },\n    \"description\": \"Jira issue tracking — search, create, update, comment, transition\"\n  }\n}\n```\n\n> **Security:** Never hardcode secrets. Prefer setting `JIRA_URL`, `JIRA_EMAIL`, and `JIRA_API_TOKEN` in your system environment (or a secrets manager). Only use the MCP `env` block for local, uncommitted config files.\n\n**To get a Jira API token:**\n1. Go to \u003Chttps:\u002F\u002Fid.atlassian.com\u002Fmanage-profile\u002Fsecurity\u002Fapi-tokens>\n2. Click **Create API token**\n3. Copy the token — store it in your environment, never in source code\n\n### Option B: Direct REST API\n\nIf MCP is not available, use the Jira REST API v3 directly via `curl` or a helper script.\n\n**Required environment variables:**\n\n| Variable | Description |\n|----------|-------------|\n| `JIRA_URL` | Your Jira instance URL (e.g., `https:\u002F\u002Fyourorg.atlassian.net`) |\n| `JIRA_EMAIL` | Your Atlassian account email |\n| `JIRA_API_TOKEN` | API token from id.atlassian.com |\n\nStore these in your shell environment, secrets manager, or an untracked local env file. Do not commit them to the repo.\n\n## MCP Tools Reference\n\nWhen the `mcp-atlassian` MCP server is configured, these tools are available:\n\n| Tool | Purpose | Example |\n|------|---------|---------|\n| `jira_search` | JQL queries | `project = PROJ AND status = \"In Progress\"` |\n| `jira_get_issue` | Fetch full issue details by key | `PROJ-1234` |\n| `jira_create_issue` | Create issues (Task, Bug, Story, Epic) | New bug report |\n| `jira_update_issue` | Update fields (summary, description, assignee) | Change assignee |\n| `jira_transition_issue` | Change status | Move to \"In Review\" |\n| `jira_add_comment` | Add comments | Progress update |\n| `jira_get_sprint_issues` | List issues in a sprint | Active sprint review |\n| `jira_create_issue_link` | Link issues (Blocks, Relates to) | Dependency tracking |\n| `jira_get_issue_development_info` | See linked PRs, branches, commits | Dev context |\n\n> **Tip:** Always call `jira_get_transitions` before transitioning — transition IDs vary per project workflow.\n\n## Direct REST API Reference\n\n### Fetch a Ticket\n\n```bash\ncurl -s -u \"$JIRA_EMAIL:$JIRA_API_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  \"$JIRA_URL\u002Frest\u002Fapi\u002F3\u002Fissue\u002FPROJ-1234\" | jq '{\n    key: .key,\n    summary: .fields.summary,\n    status: .fields.status.name,\n    priority: .fields.priority.name,\n    type: .fields.issuetype.name,\n    assignee: .fields.assignee.displayName,\n    labels: .fields.labels,\n    description: .fields.description\n  }'\n```\n\n### Fetch Comments\n\n```bash\ncurl -s -u \"$JIRA_EMAIL:$JIRA_API_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  \"$JIRA_URL\u002Frest\u002Fapi\u002F3\u002Fissue\u002FPROJ-1234?fields=comment\" | jq '.fields.comment.comments[] | {\n    author: .author.displayName,\n    created: .created[:10],\n    body: .body\n  }'\n```\n\n### Add a Comment\n\n```bash\ncurl -s -X POST -u \"$JIRA_EMAIL:$JIRA_API_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"body\": {\n      \"version\": 1,\n      \"type\": \"doc\",\n      \"content\": [{\n        \"type\": \"paragraph\",\n        \"content\": [{\"type\": \"text\", \"text\": \"Your comment here\"}]\n      }]\n    }\n  }' \\\n  \"$JIRA_URL\u002Frest\u002Fapi\u002F3\u002Fissue\u002FPROJ-1234\u002Fcomment\"\n```\n\n### Transition a Ticket\n\n```bash\n# 1. Get available transitions\ncurl -s -u \"$JIRA_EMAIL:$JIRA_API_TOKEN\" \\\n  \"$JIRA_URL\u002Frest\u002Fapi\u002F3\u002Fissue\u002FPROJ-1234\u002Ftransitions\" | jq '.transitions[] | {id, name: .name}'\n\n# 2. Execute transition (replace TRANSITION_ID)\ncurl -s -X POST -u \"$JIRA_EMAIL:$JIRA_API_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"transition\": {\"id\": \"TRANSITION_ID\"}}' \\\n  \"$JIRA_URL\u002Frest\u002Fapi\u002F3\u002Fissue\u002FPROJ-1234\u002Ftransitions\"\n```\n\n### Search with JQL\n\n```bash\ncurl -s -G -u \"$JIRA_EMAIL:$JIRA_API_TOKEN\" \\\n  --data-urlencode \"jql=project = PROJ AND status = 'In Progress'\" \\\n  \"$JIRA_URL\u002Frest\u002Fapi\u002F3\u002Fsearch\"\n```\n\n## Analyzing a Ticket\n\nWhen retrieving a ticket for development or test automation, extract:\n\n### 1. Testable Requirements\n- **Functional requirements** — What the feature does\n- **Acceptance criteria** — Conditions that must be met\n- **Testable behaviors** — Specific actions and expected outcomes\n- **User roles** — Who uses this feature and their permissions\n- **Data requirements** — What data is needed\n- **Integration points** — APIs, services, or systems involved\n\n### 2. Test Types Needed\n- **Unit tests** — Individual functions and utilities\n- **Integration tests** — API endpoints and service interactions\n- **E2E tests** — User-facing UI flows\n- **API tests** — Endpoint contracts and error handling\n\n### 3. Edge Cases & Error Scenarios\n- Invalid inputs (empty, too long, special characters)\n- Unauthorized access\n- Network failures or timeouts\n- Concurrent users or race conditions\n- Boundary conditions\n- Missing or null data\n- State transitions (back navigation, refresh, etc.)\n\n### 4. Structured Analysis Output\n\n```\nTicket: PROJ-1234\nSummary: [ticket title]\nStatus: [current status]\nPriority: [High\u002FMedium\u002FLow]\nTest Types: Unit, Integration, E2E\n\nRequirements:\n1. [requirement 1]\n2. [requirement 2]\n\nAcceptance Criteria:\n- [ ] [criterion 1]\n- [ ] [criterion 2]\n\nTest Scenarios:\n- Happy Path: [description]\n- Error Case: [description]\n- Edge Case: [description]\n\nTest Data Needed:\n- [data item 1]\n- [data item 2]\n\nDependencies:\n- [dependency 1]\n- [dependency 2]\n```\n\n## Updating Tickets\n\n### When to Update\n\n| Workflow Step | Jira Update |\n|---|---|\n| Start work | Transition to \"In Progress\" |\n| Tests written | Comment with test coverage summary |\n| Branch created | Comment with branch name |\n| PR\u002FMR created | Comment with link, link issue |\n| Tests passing | Comment with results summary |\n| PR\u002FMR merged | Transition to \"Done\" or \"In Review\" |\n\n### Comment Templates\n\n**Starting Work:**\n```\nStarting implementation for this ticket.\nBranch: feat\u002FPROJ-1234-feature-name\n```\n\n**Tests Implemented:**\n```\nAutomated tests implemented:\n\nUnit Tests:\n- [test file 1] — [what it covers]\n- [test file 2] — [what it covers]\n\nIntegration Tests:\n- [test file] — [endpoints\u002Fflows covered]\n\nAll tests passing locally. Coverage: XX%\n```\n\n**PR Created:**\n```\nPull request created:\n[PR Title](https:\u002F\u002Fgithub.com\u002Forg\u002Frepo\u002Fpull\u002FXXX)\n\nReady for review.\n```\n\n**Work Complete:**\n```\nImplementation complete.\n\nPR merged: [link]\nTest results: All passing (X\u002FY)\nCoverage: XX%\n```\n\n## Security Guidelines\n\n- **Never hardcode** Jira API tokens in source code or skill files\n- **Always use** environment variables or a secrets manager\n- **Add `.env`** to `.gitignore` in every project\n- **Rotate tokens** immediately if exposed in git history\n- **Use least-privilege** API tokens scoped to required projects\n- **Validate** that credentials are set before making API calls — fail fast with a clear message\n\n## Troubleshooting\n\n| Error | Cause | Fix |\n|---|---|---|\n| `401 Unauthorized` | Invalid or expired API token | Regenerate at id.atlassian.com |\n| `403 Forbidden` | Token lacks project permissions | Check token scopes and project access |\n| `404 Not Found` | Wrong ticket key or base URL | Verify `JIRA_URL` and ticket key |\n| `spawn uvx ENOENT` | IDE cannot find `uvx` on PATH | Use full path (e.g., `~\u002F.local\u002Fbin\u002Fuvx`) or set PATH in `~\u002F.zprofile` |\n| Connection timeout | Network\u002FVPN issue | Check VPN connection and firewall rules |\n\n## Best Practices\n\n- Update Jira as you go, not all at once at the end\n- Keep comments concise but informative\n- Link rather than copy — point to PRs, test reports, and dashboards\n- Use @mentions if you need input from others\n- Check linked issues to understand full feature scope before starting\n- If acceptance criteria are vague, ask for clarification before writing code\n",{"name":5,"origin":23,"description":7},"ECC","main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fjira-integration",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add agisota\u002Fold-one --skill jira-integration",{"tool":39,"command":40},"bunx","bunx skills add agisota\u002Fold-one --skill jira-integration",{"tool":42,"command":43},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill jira-integration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fjira-integration\u002FSKILL.md",true,[],[48,55,62,71,78,85],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","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\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":66,"licenseFileUrl":67,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]