[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78YT07NMRBVZRHBG130DWPD":3,"skill-same:01M78YT07NMRBVZRHBG130DWPD":57},{"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":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M78YT07NMRBVZRHBG130DWPD","coderabbit-performance-tuning",null,"Optimize CodeRabbit review speed, relevance, and signal-to-noise ratio.\nUse when reviews take too long, contain too many irrelevant comments,\nor when teams are experiencing review fatigue.\nTrigger with phrases like \"coderabbit performance\", \"optimize coderabbit\",\n\"coderabbit slow\", \"coderabbit noise\", \"coderabbit too many comments\", \"coderabbit relevance\".","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--coderabbit-pack--coderabbit-performance-tuning\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: coderabbit-performance-tuning\ndescription: |\n  Optimize CodeRabbit review speed, relevance, and signal-to-noise ratio.\n  Use when reviews take too long, contain too many irrelevant comments,\n  or when teams are experiencing review fatigue.\n  Trigger with phrases like \"coderabbit performance\", \"optimize coderabbit\",\n  \"coderabbit slow\", \"coderabbit noise\", \"coderabbit too many comments\", \"coderabbit relevance\".\nallowed-tools: Read, Write, Edit, Bash(gh:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, coderabbit, performance, tuning]\n---\n# CodeRabbit Performance Tuning\n\n## Overview\nOptimize CodeRabbit review speed, relevance, and developer experience. Review time is primarily a function of PR size. Comment quality is controlled by profile selection, path instructions, and learnings. This skill covers all the levers for tuning CodeRabbit to your team's needs.\n\n## Prerequisites\n- CodeRabbit installed and producing reviews\n- `.coderabbit.yaml` in repository root\n- Several PRs worth of review history to evaluate\n\n## Performance Factors\n\n| Factor | Impact | You Control? |\n|--------|--------|-------------|\n| PR size (lines changed) | Review speed (2-15 min) | Yes -- keep PRs small |\n| Profile (chill\u002Fassertive) | Comment volume | Yes -- `.coderabbit.yaml` |\n| Path instructions | Comment relevance | Yes -- `.coderabbit.yaml` |\n| Path filters | Files reviewed | Yes -- `.coderabbit.yaml` |\n| Learnings | Long-term quality | Yes -- via PR comment feedback |\n| CodeRabbit service load | Review latency | No -- check status page |\n\n## Instructions\n\n### Step 1: Optimize PR Size for Faster Reviews\n```markdown\n# PR size directly impacts review speed and quality\n\n| PR Size | Review Time | Review Quality |\n|---------|------------|----------------|\n| \u003C 200 lines | 2-3 min | Excellent -- focused, actionable |\n| 200-500 lines | 3-7 min | Good -- catches most issues |\n| 500-1000 lines | 7-12 min | Moderate -- may miss nuanced issues |\n| 1000+ lines | 12-15+ min | Low -- too much context |\n\n# Enforce PR size limits with CI:\n```\n\n```yaml\n# .github\u002Fworkflows\u002Fpr-size.yml\nname: PR Size Check\non: [pull_request]\njobs:\n  check:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n        with:\n          fetch-depth: 0\n      - name: Check PR size\n        run: |\n          TOTAL=$(git diff --stat origin\u002F${{ github.base_ref }}...HEAD | tail -1 | \\\n            grep -oP '\\d+ insertion|d+ deletion' | grep -oP '\\d+' | \\\n            awk '{sum+=$1} END {print sum+0}')\n          echo \"Lines changed: $TOTAL\"\n          if [ \"$TOTAL\" -gt 500 ]; then\n            echo \"::warning::Large PR ($TOTAL lines). Consider splitting for better CodeRabbit review quality.\"\n          fi\n```\n\n### Step 2: Choose the Right Review Profile\n```yaml\n# .coderabbit.yaml - Profile comparison\nreviews:\n  profile: \"assertive\"    # Start here, tune based on team feedback\n\n# Profile decision guide:\n#\n# \"chill\":\n#   - 1-3 comments per PR\n#   - Only critical issues and bugs\n#   - Best for: senior teams, high-trust environments\n#   - Warning: may miss moderate issues\n#\n# \"assertive\" (recommended):\n#   - 3-8 comments per PR\n#   - Bugs, security, best practices\n#   - Best for: most teams\n#   - Good balance of signal-to-noise\n#\n# Tune based on metrics:\n#   - Team ignoring most comments? → Switch to chill\n#   - Security issues slipping through? → Stay on assertive\n#   - New or junior team? → assertive catches more learning opportunities\n```\n\n### Step 3: Add Path Instructions for Relevance\n```yaml\n# .coderabbit.yaml - Context makes reviews more relevant\nreviews:\n  path_instructions:\n    # Tell CodeRabbit WHAT to look for (increases relevance)\n    - path: \"src\u002Fapi\u002F**\"\n      instructions: |\n        Review for: input validation, proper HTTP status codes, auth middleware.\n        Ignore: import order, logging format.\n\n    - path: \"src\u002Fcomponents\u002F**\"\n      instructions: |\n        Review for: accessibility (aria labels), performance (memo\u002FuseMemo).\n        Ignore: CSS naming, component file structure.\n\n    - path: \"**\u002F*.test.*\"\n      instructions: |\n        Review for: assertion completeness, edge cases, async handling.\n        Do NOT comment on: test naming conventions, import order.\n\n    # Tell CodeRabbit what NOT to comment on (reduces noise)\n    - path: \"src\u002Flegacy\u002F**\"\n      instructions: |\n        Legacy code being incrementally migrated.\n        ONLY flag: security vulnerabilities, data loss risks, crashes.\n        Do NOT suggest: refactoring, naming changes, style improvements.\n\n    - path: \"scripts\u002F**\"\n      instructions: |\n        One-off scripts. Only flag: security issues, destructive operations\n        without confirmation, missing error handling on file\u002Fnetwork ops.\n```\n\n### Step 4: Exclude Low-Value Files\n```yaml\n# .coderabbit.yaml - Skip files that generate noise\nreviews:\n  path_filters:\n    # Auto-generated files (no useful feedback possible)\n    - \"!**\u002F*.lock\"\n    - \"!**\u002Fpackage-lock.json\"\n    - \"!**\u002Fpnpm-lock.yaml\"\n    - \"!**\u002F*.generated.*\"\n    - \"!**\u002Fgenerated\u002F**\"\n\n    # Build output\n    - \"!dist\u002F**\"\n    - \"!build\u002F**\"\n    - \"!**\u002F*.min.js\"\n    - \"!**\u002F*.min.css\"\n\n    # Test fixtures and snapshots\n    - \"!**\u002F*.snap\"\n    - \"!**\u002F__mocks__\u002F**\"\n    - \"!**\u002Ffixtures\u002F**\"\n    - \"!**\u002Ftestdata\u002F**\"\n\n    # Third-party code\n    - \"!vendor\u002F**\"\n    - \"!node_modules\u002F**\"\n\n    # Data files\n    - \"!**\u002F*.csv\"\n    - \"!**\u002F*.sql\"           # DB migrations (review manually)\n\n  auto_review:\n    ignore_title_keywords:\n      - \"WIP\"\n      - \"DO NOT MERGE\"\n      - \"chore: bump\"\n      - \"chore(deps)\"\n      - \"auto-generated\"\n    drafts: false            # Skip draft PRs\n```\n\n### Step 5: Train CodeRabbit with Learnings\n```markdown\n# CodeRabbit learns from your feedback on PR comments.\n# This improves relevance over time.\n\n# When CodeRabbit gives feedback you disagree with, reply:\n\"We intentionally use default exports in this project for Next.js pages.\nPlease don't flag default exports in files under src\u002Fpages\u002F.\"\n\n# When CodeRabbit catches something valuable, reinforce it:\n\"Good catch! Always flag missing error boundaries in React components.\"\n\n# View and manage learnings:\n# app.coderabbit.ai > Organization > Learnings\n\n# Learnings persist across PRs and repos within the organization.\n# They are the most effective long-term tuning mechanism.\n```\n\n### Step 6: Measure Improvement\n```bash\nset -euo pipefail\nORG=\"${1:-your-org}\"\nREPO=\"${2:-your-repo}\"\n\necho \"=== Review Quality Metrics ===\"\n\nTOTAL_PRS=0\nTOTAL_COMMENTS=0\n\nfor PR_NUM in $(gh api \"repos\u002F$ORG\u002F$REPO\u002Fpulls?state=closed&per_page=20\" --jq '.[].number'); do\n  COMMENTS=$(gh api \"repos\u002F$ORG\u002F$REPO\u002Fpulls\u002F$PR_NUM\u002Fcomments\" \\\n    --jq '[.[] | select(.user.login==\"coderabbitai[bot]\")] | length' 2>\u002Fdev\u002Fnull || echo \"0\")\n  if [ \"$COMMENTS\" -gt 0 ]; then\n    TOTAL_PRS=$((TOTAL_PRS + 1))\n    TOTAL_COMMENTS=$((TOTAL_COMMENTS + COMMENTS))\n    echo \"PR #$PR_NUM: $COMMENTS comments\"\n  fi\ndone\n\nif [ \"$TOTAL_PRS\" -gt 0 ]; then\n  AVG=$(( TOTAL_COMMENTS \u002F TOTAL_PRS ))\n  echo \"\"\n  echo \"Average: $AVG comments\u002FPR\"\n  echo \"\"\n  if [ \"$AVG\" -gt 10 ]; then\n    echo \"Recommendation: Switch to 'chill' profile or add path_instructions\"\n  elif [ \"$AVG\" -lt 2 ]; then\n    echo \"Recommendation: Switch to 'assertive' profile for more thorough reviews\"\n  else\n    echo \"Good signal-to-noise ratio\"\n  fi\nfi\n```\n\n## Output\n- PR size guidelines documented and enforced via CI\n- Review profile selected based on team needs\n- Path instructions configured for relevant feedback\n- Low-value files excluded from review\n- Learnings trained from team feedback\n- Review quality measured with metrics\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Review takes 15+ min | PR too large (1000+ lines) | Split into smaller PRs |\n| Too many irrelevant comments | No path_instructions | Add context for key directories |\n| Team ignoring reviews | Review fatigue from noise | Switch to `chill`, add exclusions |\n| Same issue flagged repeatedly | Learning not created | Reply to comment stating the preference |\n| Reviews on generated code | Missing path_filters | Add `!**\u002Fgenerated\u002F**` to exclusions |\n\n## Resources\n- [CodeRabbit Review Profiles](https:\u002F\u002Fdocs.coderabbit.ai\u002Freference\u002Fconfiguration)\n- [Path Instructions Guide](https:\u002F\u002Fdocs.coderabbit.ai\u002Fguides\u002Freview-instructions)\n- [CodeRabbit Learnings](https:\u002F\u002Fdocs.coderabbit.ai\u002Fguides\u002Flearnings)\n\n## Next Steps\nFor learnings and advanced tuning, see `coderabbit-core-workflow-b`.\n","# CodeRabbit Performance Tuning\n\n## Overview\nOptimize CodeRabbit review speed, relevance, and developer experience. Review time is primarily a function of PR size. Comment quality is controlled by profile selection, path instructions, and learnings. This skill covers all the levers for tuning CodeRabbit to your team's needs.\n\n## Prerequisites\n- CodeRabbit installed and producing reviews\n- `.coderabbit.yaml` in repository root\n- Several PRs worth of review history to evaluate\n\n## Performance Factors\n\n| Factor | Impact | You Control? |\n|--------|--------|-------------|\n| PR size (lines changed) | Review speed (2-15 min) | Yes -- keep PRs small |\n| Profile (chill\u002Fassertive) | Comment volume | Yes -- `.coderabbit.yaml` |\n| Path instructions | Comment relevance | Yes -- `.coderabbit.yaml` |\n| Path filters | Files reviewed | Yes -- `.coderabbit.yaml` |\n| Learnings | Long-term quality | Yes -- via PR comment feedback |\n| CodeRabbit service load | Review latency | No -- check status page |\n\n## Instructions\n\n### Step 1: Optimize PR Size for Faster Reviews\n```markdown\n# PR size directly impacts review speed and quality\n\n| PR Size | Review Time | Review Quality |\n|---------|------------|----------------|\n| \u003C 200 lines | 2-3 min | Excellent -- focused, actionable |\n| 200-500 lines | 3-7 min | Good -- catches most issues |\n| 500-1000 lines | 7-12 min | Moderate -- may miss nuanced issues |\n| 1000+ lines | 12-15+ min | Low -- too much context |\n\n# Enforce PR size limits with CI:\n```\n\n```yaml\n# .github\u002Fworkflows\u002Fpr-size.yml\nname: PR Size Check\non: [pull_request]\njobs:\n  check:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n        with:\n          fetch-depth: 0\n      - name: Check PR size\n        run: |\n          TOTAL=$(git diff --stat origin\u002F${{ github.base_ref }}...HEAD | tail -1 | \\\n            grep -oP '\\d+ insertion|d+ deletion' | grep -oP '\\d+' | \\\n            awk '{sum+=$1} END {print sum+0}')\n          echo \"Lines changed: $TOTAL\"\n          if [ \"$TOTAL\" -gt 500 ]; then\n            echo \"::warning::Large PR ($TOTAL lines). Consider splitting for better CodeRabbit review quality.\"\n          fi\n```\n\n### Step 2: Choose the Right Review Profile\n```yaml\n# .coderabbit.yaml - Profile comparison\nreviews:\n  profile: \"assertive\"    # Start here, tune based on team feedback\n\n# Profile decision guide:\n#\n# \"chill\":\n#   - 1-3 comments per PR\n#   - Only critical issues and bugs\n#   - Best for: senior teams, high-trust environments\n#   - Warning: may miss moderate issues\n#\n# \"assertive\" (recommended):\n#   - 3-8 comments per PR\n#   - Bugs, security, best practices\n#   - Best for: most teams\n#   - Good balance of signal-to-noise\n#\n# Tune based on metrics:\n#   - Team ignoring most comments? → Switch to chill\n#   - Security issues slipping through? → Stay on assertive\n#   - New or junior team? → assertive catches more learning opportunities\n```\n\n### Step 3: Add Path Instructions for Relevance\n```yaml\n# .coderabbit.yaml - Context makes reviews more relevant\nreviews:\n  path_instructions:\n    # Tell CodeRabbit WHAT to look for (increases relevance)\n    - path: \"src\u002Fapi\u002F**\"\n      instructions: |\n        Review for: input validation, proper HTTP status codes, auth middleware.\n        Ignore: import order, logging format.\n\n    - path: \"src\u002Fcomponents\u002F**\"\n      instructions: |\n        Review for: accessibility (aria labels), performance (memo\u002FuseMemo).\n        Ignore: CSS naming, component file structure.\n\n    - path: \"**\u002F*.test.*\"\n      instructions: |\n        Review for: assertion completeness, edge cases, async handling.\n        Do NOT comment on: test naming conventions, import order.\n\n    # Tell CodeRabbit what NOT to comment on (reduces noise)\n    - path: \"src\u002Flegacy\u002F**\"\n      instructions: |\n        Legacy code being incrementally migrated.\n        ONLY flag: security vulnerabilities, data loss risks, crashes.\n        Do NOT suggest: refactoring, naming changes, style improvements.\n\n    - path: \"scripts\u002F**\"\n      instructions: |\n        One-off scripts. Only flag: security issues, destructive operations\n        without confirmation, missing error handling on file\u002Fnetwork ops.\n```\n\n### Step 4: Exclude Low-Value Files\n```yaml\n# .coderabbit.yaml - Skip files that generate noise\nreviews:\n  path_filters:\n    # Auto-generated files (no useful feedback possible)\n    - \"!**\u002F*.lock\"\n    - \"!**\u002Fpackage-lock.json\"\n    - \"!**\u002Fpnpm-lock.yaml\"\n    - \"!**\u002F*.generated.*\"\n    - \"!**\u002Fgenerated\u002F**\"\n\n    # Build output\n    - \"!dist\u002F**\"\n    - \"!build\u002F**\"\n    - \"!**\u002F*.min.js\"\n    - \"!**\u002F*.min.css\"\n\n    # Test fixtures and snapshots\n    - \"!**\u002F*.snap\"\n    - \"!**\u002F__mocks__\u002F**\"\n    - \"!**\u002Ffixtures\u002F**\"\n    - \"!**\u002Ftestdata\u002F**\"\n\n    # Third-party code\n    - \"!vendor\u002F**\"\n    - \"!node_modules\u002F**\"\n\n    # Data files\n    - \"!**\u002F*.csv\"\n    - \"!**\u002F*.sql\"           # DB migrations (review manually)\n\n  auto_review:\n    ignore_title_keywords:\n      - \"WIP\"\n      - \"DO NOT MERGE\"\n      - \"chore: bump\"\n      - \"chore(deps)\"\n      - \"auto-generated\"\n    drafts: false            # Skip draft PRs\n```\n\n### Step 5: Train CodeRabbit with Learnings\n```markdown\n# CodeRabbit learns from your feedback on PR comments.\n# This improves relevance over time.\n\n# When CodeRabbit gives feedback you disagree with, reply:\n\"We intentionally use default exports in this project for Next.js pages.\nPlease don't flag default exports in files under src\u002Fpages\u002F.\"\n\n# When CodeRabbit catches something valuable, reinforce it:\n\"Good catch! Always flag missing error boundaries in React components.\"\n\n# View and manage learnings:\n# app.coderabbit.ai > Organization > Learnings\n\n# Learnings persist across PRs and repos within the organization.\n# They are the most effective long-term tuning mechanism.\n```\n\n### Step 6: Measure Improvement\n```bash\nset -euo pipefail\nORG=\"${1:-your-org}\"\nREPO=\"${2:-your-repo}\"\n\necho \"=== Review Quality Metrics ===\"\n\nTOTAL_PRS=0\nTOTAL_COMMENTS=0\n\nfor PR_NUM in $(gh api \"repos\u002F$ORG\u002F$REPO\u002Fpulls?state=closed&per_page=20\" --jq '.[].number'); do\n  COMMENTS=$(gh api \"repos\u002F$ORG\u002F$REPO\u002Fpulls\u002F$PR_NUM\u002Fcomments\" \\\n    --jq '[.[] | select(.user.login==\"coderabbitai[bot]\")] | length' 2>\u002Fdev\u002Fnull || echo \"0\")\n  if [ \"$COMMENTS\" -gt 0 ]; then\n    TOTAL_PRS=$((TOTAL_PRS + 1))\n    TOTAL_COMMENTS=$((TOTAL_COMMENTS + COMMENTS))\n    echo \"PR #$PR_NUM: $COMMENTS comments\"\n  fi\ndone\n\nif [ \"$TOTAL_PRS\" -gt 0 ]; then\n  AVG=$(( TOTAL_COMMENTS \u002F TOTAL_PRS ))\n  echo \"\"\n  echo \"Average: $AVG comments\u002FPR\"\n  echo \"\"\n  if [ \"$AVG\" -gt 10 ]; then\n    echo \"Recommendation: Switch to 'chill' profile or add path_instructions\"\n  elif [ \"$AVG\" -lt 2 ]; then\n    echo \"Recommendation: Switch to 'assertive' profile for more thorough reviews\"\n  else\n    echo \"Good signal-to-noise ratio\"\n  fi\nfi\n```\n\n## Output\n- PR size guidelines documented and enforced via CI\n- Review profile selected based on team needs\n- Path instructions configured for relevant feedback\n- Low-value files excluded from review\n- Learnings trained from team feedback\n- Review quality measured with metrics\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Review takes 15+ min | PR too large (1000+ lines) | Split into smaller PRs |\n| Too many irrelevant comments | No path_instructions | Add context for key directories |\n| Team ignoring reviews | Review fatigue from noise | Switch to `chill`, add exclusions |\n| Same issue flagged repeatedly | Learning not created | Reply to comment stating the preference |\n| Reviews on generated code | Missing path_filters | Add `!**\u002Fgenerated\u002F**` to exclusions |\n\n## Resources\n- [CodeRabbit Review Profiles](https:\u002F\u002Fdocs.coderabbit.ai\u002Freference\u002Fconfiguration)\n- [Path Instructions Guide](https:\u002F\u002Fdocs.coderabbit.ai\u002Fguides\u002Freview-instructions)\n- [CodeRabbit Learnings](https:\u002F\u002Fdocs.coderabbit.ai\u002Fguides\u002Flearnings)\n\n## Next Steps\nFor learnings and advanced tuning, see `coderabbit-core-workflow-b`.\n",{"name":5,"tags":24,"author":29,"license":15,"version":30,"description":31,"allowed-tools":32,"compatible-with":33},[25,26,27,28],"saas","coderabbit","performance","tuning","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Optimize CodeRabbit review speed, relevance, and signal-to-noise ratio.\nUse when reviews take too long, contain too many irrelevant comments,\nor when teams are experiencing review fatigue.\nTrigger with phrases like \"coderabbit performance\", \"optimize coderabbit\",\n\"coderabbit slow\", \"coderabbit noise\", \"coderabbit too many comments\", \"coderabbit relevance\".\n","Read, Write, Edit, Bash(gh:*)","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--coderabbit-pack--coderabbit-performance-tuning",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill coderabbit-performance-tuning",{"tool":49,"command":50},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill coderabbit-performance-tuning",{"tool":52,"command":53},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill coderabbit-performance-tuning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--coderabbit-pack--coderabbit-performance-tuning\u002FSKILL.md",true,[],[58,65,72,79,86,94],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]