[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AJRGF6CADYZ837BKC53ZR2":3,"skill-same:01M7AJRGF6CADYZ837BKC53ZR2":43},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"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":5,"forksCount":25,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M7AJRGF6CADYZ837BKC53ZR2","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.","davidanthonyn\u002Fagent-skills","davidanthonyn","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F55152980?v=4","01M7AJ4MY8S5C2RJCGX6626J0G","01M7AJ4MZB7EC7CAP27ANCSE7N",1,"MIT","https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fagent-skills\u002Fblob\u002Fmain\u002Fci-fix\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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","6b73b29e4866f997b1eb47fe8d9631396265fc24",0,"https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fagent-skills","https:\u002F\u002Fgithub.com\u002Fdavidanthonyn","2026-09-09 16:06:07",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add davidanthonyn\u002Fagent-skills --skill ci-fix",{"tool":35,"command":36},"bunx","bunx skills add davidanthonyn\u002Fagent-skills --skill ci-fix",{"tool":38,"command":39},"pnpm","pnpm dlx skills add davidanthonyn\u002Fagent-skills --skill ci-fix","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fagent-skills\u002Fblob\u002Fmain\u002Fci-fix\u002FSKILL.md",true,[],[44,51,59,66,73,82],{"skillNo":45,"name":46,"nameZh":6,"description":47,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":48,"categories":49,"keywords":50,"publishedAt":18},"01M7AQNJDXVNVMN08N5BHBGZBF","zustand-state-management","Production-tested setup for Zustand state management in React applications with TypeScript.\nThis skill provides comprehensive patterns for building scalable, type-safe global state.\n\nUse when: setting up global state in React, migrating from Redux or Context API, implementing\nstate persistence with localStorage, configuring TypeScript with Zustand, using slices pattern\nfor modular stores, adding devtools middleware for debugging, handling Next.js SSR hydration,\nor encountering hydration errors, TypeScript inference issues, or persist middleware problems.\n\nPrevents 5 documented issues: Next.js hydration mismatches, TypeScript double parentheses\nsyntax errors, persist middleware export errors, infinite render loops, and slices pattern\ntype inference failures.\n\nKeywords: zustand, state management, React state, TypeScript state, persist middleware,\ndevtools, slices pattern, global state, React hooks, create store, useBoundStore,\nStateCreator, hydration error, text content mismatch, infinite render, localStorage,\nsessionStorage, immer middleware, shallow equality, selector pattern, zustand v5","https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fagent-skills\u002Fblob\u002Fmain\u002Fzustand-state-management\u002FSKILL.md",[],[],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":55,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M7AQN2DW9DTPM8BYNZSHQANC","zetic-mlange","Help users integrate the ZETIC Melange (MLange) on-device AI SDK into Android (Kotlin\u002FJava) and iOS (Swift) mobile apps. Use this skill whenever the user mentions Zetic, MLange, Melange, ZeticMLangeModel, ZeticMLangeLLMModel, ZeticMLangeHFModel, on-device NPU inference for mobile, or deploying ML models to Android\u002FiOS with NPU acceleration. Also trigger when users ask about running LLMs on-device with GGUF quantization, mobile NPU model deployment, or converting PyTorch\u002FONNX models for mobile inference. Covers general model inference, LLM inference (streaming token generation), and HuggingFace model loading.","https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fagent-skills\u002Fblob\u002Fmain\u002Fzetic-mlange\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fagent-skills\u002Fblob\u002Fmain\u002Fzetic-mlange\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M7AQMEK370FBPC75N2W8WA4W","youtube-downloader","Download videos, audio, playlists, and channels from YouTube and 1000+ websites using yt-dlp. Supports quality selection, format conversion, subtitle download, playlist filtering, metadata extraction, thumbnail download, and batch operations. Use when downloading YouTube videos in any quality (4K, 8K, HDR), extracting audio as MP3\u002FM4A\u002FFLAC, downloading entire playlists\u002Fchannels, getting subtitles in multiple languages, converting to specific formats, downloading live streams, archiving content, or batch processing multiple URLs. Optimized for reliability with automatic retries, rate limiting, and error handling.","https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fagent-skills\u002Fblob\u002Fmain\u002Fyoutube-downloader\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M7AQHKQ4VQB04NH6BG4SV9Q7","wordpress-plugin-core","This skill provides comprehensive knowledge for WordPress plugin development, covering core patterns, security best practices, database interactions, hooks\u002Ffilters, Settings API, custom post types, REST API, and AJAX. This skill should be used when creating WordPress plugins, troubleshooting security issues, implementing custom post types\u002Ftaxonomies, building admin interfaces, or working with the WordPress database.\n\nUse when: Creating new WordPress plugins, implementing nonces\u002Fsanitization\u002Fescaping, working with $wpdb and prepared statements, building Settings API pages, registering custom post types or taxonomies, implementing REST API endpoints, handling AJAX requests, debugging plugin activation\u002Fdeactivation issues, preventing SQL injection\u002FXSS\u002FCSRF vulnerabilities.\n\nKeywords: wordpress plugin development, wordpress security, wordpress hooks, wordpress filters, wordpress database, wpdb prepare, sanitize_text_field, esc_html, wp_nonce, custom post type, register_post_type, settings api, rest api, admin-ajax, wordpress sql injection, wordpress xss, wordpress csrf, plugin header, activation hook, deactivation hook, wordpress coding standards, wordpress plugin architecture","https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fagent-skills\u002Fblob\u002Fmain\u002Fwordpress-plugin-core\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":77,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7AQH4JW8F2MJFS1C43TZ2TY","webapp-testing","Test local web applications with Playwright. Use when asked to verify frontend functionality, debug UI behavior, capture browser screenshots, or inspect browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fagent-skills\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fagent-skills\u002Fblob\u002Fmain\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7AQH0PWD6Z1NN66V15DT25M","web-performance-audit","Audit web performance using Chrome DevTools MCP. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed.","https:\u002F\u002Fgithub.com\u002Fdavidanthonyn\u002Fagent-skills\u002Fblob\u002Fmain\u002Fweb-performance-audit\u002FSKILL.md",[],[]]