[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75C5W9KPX7Y6MKC5WW38R5M":3,"skill-same:01M75C5W9KPX7Y6MKC5WW38R5M":46},{"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":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75C5W9KPX7Y6MKC5WW38R5M","ci-fix",null,"Diagnose and fix GitHub Actions CI failures. Inspects workflow runs and logs, identifies root causes, implements minimal fixes, and pushes to a fix branch. Use when CI is failing, red, broken, or needs diagnosis.","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\u002Fci-fix\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: ci-fix\ndescription: Diagnose and fix GitHub Actions CI failures. Inspects workflow runs and logs, identifies root causes, implements minimal fixes, and pushes to a fix branch. Use when CI is failing, red, broken, or needs diagnosis.\nlicense: MIT\n---\n\n# CI Fix\n\nDiagnose CI failures and implement fixes with minimal, targeted diffs. Pushes fixes to a dedicated branch without creating PRs.\n\n## Prerequisites\n\nVerify GitHub CLI authentication before proceeding:\n\n```bash\ngh auth status\n```\n\nIf not authenticated, instruct the user to run `gh auth login` first.\n\n## Workflow\n\n### 1. Locate the Failing Run\n\nDetermine the failing workflow run. If working on a PR branch:\n\n```bash\ngh pr view --json statusCheckRollup --jq '.statusCheckRollup[] | select(.conclusion == \"FAILURE\")'\n```\n\nIf working from a branch or run ID:\n\n```bash\ngh run list --branch \u003Cbranch> --status failure --limit 5\ngh run view \u003Crun-id> --verbose\n```\n\n### 2. Extract Failure Logs\n\nPull logs from failed steps to identify the root cause:\n\n```bash\ngh run view \u003Crun-id> --log-failed\n```\n\nFor deeper inspection:\n\n```bash\ngh run view \u003Crun-id> --log --job \u003Cjob-id>\ngh run download \u003Crun-id> -D .artifacts\u002F\u003Crun-id>\n```\n\n### 3. Identify Root Cause\n\nAnalyze logs for common failure patterns:\n\n- **Build\u002Fcompilation errors**: Missing dependencies, type errors, syntax issues\n- **Test failures**: Assertion failures, timeouts, flaky tests\n- **Linting\u002Fformatting**: Style violations, unused imports\n- **Environment issues**: Missing secrets, permissions, resource limits\n\nPrefer the smallest fix that resolves the issue. Deterministic code fixes are better than workflow plumbing changes.\n\n### 4. Implement the Fix\n\nMake minimal, scoped changes matching the repository's existing style:\n\n- Fix only what's broken—avoid unrelated refactoring\n- Keep changes to the failing job\u002Fstep when possible\n- If modifying workflow files, preserve existing permissions and avoid expanding token access\n\n### 5. Push to Fix Branch\n\nCreate or update a dedicated fix branch:\n\n```bash\ngit checkout -b ci-fix\u002F\u003Coriginal-branch>\ngit add -A\ngit commit -m \"fix: resolve CI failure in \u003Cjob-name>\n\nCo-Authored-By: Warp \u003Cagent@warp.dev>\"\ngit push -u origin ci-fix\u002F\u003Coriginal-branch>\n```\n\nIf the fix branch already exists, update it:\n\n```bash\ngit checkout ci-fix\u002F\u003Coriginal-branch>\ngit pull origin \u003Coriginal-branch>\n# make fixes\ngit commit -m \"fix: \u003Cdescription>\n\nCo-Authored-By: Warp \u003Cagent@warp.dev>\"\ngit push\n```\n\n### 6. Verify the Fix\n\nTrigger CI on the fix branch and monitor:\n\n```bash\ngh run list --branch ci-fix\u002F\u003Coriginal-branch> --limit 1\ngh run watch \u003Cnew-run-id> --exit-status\n```\n\nTo rerun only failed jobs:\n\n```bash\ngh run rerun \u003Crun-id> --failed\n```\n\n## Safety Notes\n\n- Avoid `pull_request_target` unless explicitly requested—it can expose secrets to untrusted code\n- Keep workflow `permissions:` minimal; don't broaden access to make tests pass\n- For flaky tests, prefer deterministic fixes over blind reruns\n\n## Deliverable\n\nAfter fixing, provide a brief summary:\n\n- **Failing run**: Link or ID\n- **Root cause**: What broke and why\n- **Fix**: What changed\n- **Verification**: New run link showing green status\n","# CI Fix\n\nDiagnose CI failures and implement fixes with minimal, targeted diffs. Pushes fixes to a dedicated branch without creating PRs.\n\n## Prerequisites\n\nVerify GitHub CLI authentication before proceeding:\n\n```bash\ngh auth status\n```\n\nIf not authenticated, instruct the user to run `gh auth login` first.\n\n## Workflow\n\n### 1. Locate the Failing Run\n\nDetermine the failing workflow run. If working on a PR branch:\n\n```bash\ngh pr view --json statusCheckRollup --jq '.statusCheckRollup[] | select(.conclusion == \"FAILURE\")'\n```\n\nIf working from a branch or run ID:\n\n```bash\ngh run list --branch \u003Cbranch> --status failure --limit 5\ngh run view \u003Crun-id> --verbose\n```\n\n### 2. Extract Failure Logs\n\nPull logs from failed steps to identify the root cause:\n\n```bash\ngh run view \u003Crun-id> --log-failed\n```\n\nFor deeper inspection:\n\n```bash\ngh run view \u003Crun-id> --log --job \u003Cjob-id>\ngh run download \u003Crun-id> -D .artifacts\u002F\u003Crun-id>\n```\n\n### 3. Identify Root Cause\n\nAnalyze logs for common failure patterns:\n\n- **Build\u002Fcompilation errors**: Missing dependencies, type errors, syntax issues\n- **Test failures**: Assertion failures, timeouts, flaky tests\n- **Linting\u002Fformatting**: Style violations, unused imports\n- **Environment issues**: Missing secrets, permissions, resource limits\n\nPrefer the smallest fix that resolves the issue. Deterministic code fixes are better than workflow plumbing changes.\n\n### 4. Implement the Fix\n\nMake minimal, scoped changes matching the repository's existing style:\n\n- Fix only what's broken—avoid unrelated refactoring\n- Keep changes to the failing job\u002Fstep when possible\n- If modifying workflow files, preserve existing permissions and avoid expanding token access\n\n### 5. Push to Fix Branch\n\nCreate or update a dedicated fix branch:\n\n```bash\ngit checkout -b ci-fix\u002F\u003Coriginal-branch>\ngit add -A\ngit commit -m \"fix: resolve CI failure in \u003Cjob-name>\n\nCo-Authored-By: Warp \u003Cagent@warp.dev>\"\ngit push -u origin ci-fix\u002F\u003Coriginal-branch>\n```\n\nIf the fix branch already exists, update it:\n\n```bash\ngit checkout ci-fix\u002F\u003Coriginal-branch>\ngit pull origin \u003Coriginal-branch>\n# make fixes\ngit commit -m \"fix: \u003Cdescription>\n\nCo-Authored-By: Warp \u003Cagent@warp.dev>\"\ngit push\n```\n\n### 6. Verify the Fix\n\nTrigger CI on the fix branch and monitor:\n\n```bash\ngh run list --branch ci-fix\u002F\u003Coriginal-branch> --limit 1\ngh run watch \u003Cnew-run-id> --exit-status\n```\n\nTo rerun only failed jobs:\n\n```bash\ngh run rerun \u003Crun-id> --failed\n```\n\n## Safety Notes\n\n- Avoid `pull_request_target` unless explicitly requested—it can expose secrets to untrusted code\n- Keep workflow `permissions:` minimal; don't broaden access to make tests pass\n- For flaky tests, prefer deterministic fixes over blind reruns\n\n## Deliverable\n\nAfter fixing, provide a brief summary:\n\n- **Failing run**: Link or ID\n- **Root cause**: What broke and why\n- **Fix**: What changed\n- **Verification**: New run link showing green status\n",{"name":5,"license":14,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fci-fix",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":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add agisota\u002Fold-one --skill ci-fix",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill ci-fix",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill ci-fix","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fci-fix\u002FSKILL.md",true,[],[47,54,61,70,77,84],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"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":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"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":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"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":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"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":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"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":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"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",[],[]]