[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C28WK1XB5AMA35FEXV8KKS":3,"skill-same:01M6C28WK1XB5AMA35FEXV8KKS":115},{"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":30,"publishedAt":63,"linkOnly":64,"markdownContent":65,"markdownBody":66,"frontMatter":67,"refName":74,"commitSha":75,"skillDirectory":76,"forksCount":77,"repositoryHtmlUrl":78,"repositoryHomepageUrl":6,"ownerHtmlUrl":79,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":80,"install":81,"resources":94},"01M6C28WK1XB5AMA35FEXV8KKS","minimax-401-diagnostic",null,"Diagnose MiniMax 401 auth errors in AO workers. A redacted or invalid MINIMAX_API_KEY is one possible cause; verify current provider errors and configuration before identifying the cause or changing settings.","jleechanorg\u002Fjleechan-skills","jleechanorg","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F221404966?v=4","01M6C1VJ99XG950X1DWPEBCBGX","01M6C1VJDK5YVDNT3362RT5WSB",6,"MIT","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fminimax-401-diagnostic\u002FSKILL.md",[17,22,25],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":26,"categoryName":27,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,59,60,61,62],"diagnostic","minimax","minimax 401 diagnostic","settings","when","login","errors","error","invalid","worker","please","incident","ao","ms","launchd","use","auth","edit","write","read","prompt","model","Bash","verify","api","credentials","proxy","issues","routing","run","diagnose","config","2026-11-10 10:12:30",false,"---\nname: minimax-401-diagnostic\ndescription: Diagnose MiniMax 401 auth errors in AO workers. A redacted or invalid MINIMAX_API_KEY is one possible cause; verify current provider errors and configuration before identifying the cause or changing settings.\nwhen_to_use: \"Use when: (1) an AO worker tmux pane shows 'Please run \u002Flogin · API Error: 401' or 'login fail: carry the API secret key', (2) worker is stuck waiting for input despite having 'minimax' model config, (3) \u002Fms surfaces another 401 incident. Do NOT use for general auth issues — this skill is specifically for the MiniMax proxy 401 + \u002Flogin prompt stall pattern.\"\nallowed-tools: [\"Bash\", \"Read\", \"Write\", \"Edit\"]\ncontext: \"A redacted or invalid MINIMAX_API_KEY in the launchd configuration is one known cause of 401 errors. A \u002Flogin prompt may follow a provider 401, but verify the current response and configuration before concluding that credentials or model routing caused it. Do not swap models as a substitute for diagnosis.\"\n---\n\n# MiniMax 401 Diagnostic\n\n## Common symptom pattern\n\nThis sequence is one possible failure pattern; verify each step from current\nprovider output and worker configuration.\n\n1. AO worker starts → hits MiniMax proxy → proxy returns `401 Unauthorized`\n2. Claude Code intercepts 401 → shows `\u002Flogin` prompt in tmux pane\n3. Worker appears to hang (\"waiting for input\") but is actually blocked on `\u002Flogin`\n4. `tmux capture-pane` shows: `Please run \u002Flogin · API Error: 401` or `login fail: carry the API secret key in the 'Authorization' field`\n5. Config shows `agent: minimax` or `model: MiniMax-M2.7` — this alone does not establish the cause\n\n## Quick Diagnosis\n\n### Step 0 — Plist template check (do this FIRST)\n\n```bash\n# Check for unsubstituted @VAR@ tokens in the installed plist\n# If any exist, bash expands them to empty → 401 on every API call\npython3 - \"$HOME\u002FLibrary\u002FLaunchAgents\u002Fai.agento.lifecycle-all.plist\" \u003C\u003C'EOF'\nimport plistlib, re, sys\ncontent = open(sys.argv[1]).read()\nvars = re.findall(r'@[A-Z_][A-Z0-9_]*@', content)\nif vars:\n    print(f'BAD: Unsubstituted tokens: {sorted(set(vars))}')\nelse:\n    print('OK: No unsubstituted @VAR@ tokens')\nEOF\n\n# If BAD: re-run setup to regenerate plist with real env vars:\nbash scripts\u002Fsetup-launchd.sh lifecycle\n# Then verify:\nbash scripts\u002Ftest-launchd-env.sh\n```\n\nUnsubstituted `@VAR@` tokens establish that the plist template was not rendered.\nUse the repository's launchd setup workflow, then continue diagnosis if the\n401 persists.\n\n```bash\npython3 - \"$HOME\u002FLibrary\u002FLaunchAgents\u002Fai.agento.lifecycle-all.plist\" \u003C\u003C'EOF'\nimport plistlib, re, sys\n\nwith open(sys.argv[1], \"rb\") as source:\n    data = plistlib.load(source)\nvariables = re.findall(r\"@[A-Z_][A-Z0-9_]*@\", str(data))\nkey = data.get(\"EnvironmentVariables\", {}).get(\"MINIMAX_API_KEY\", \"\")\nprint(\"BAD: unsubstituted plist template tokens\" if variables else \"OK: no template tokens\")\nif key == \"__OPENCLAW_REDACTED__\":\n    print(\"BAD: MINIMAX_API_KEY is the redacted sentinel\")\nelif key:\n    print(\"OK: MINIMAX_API_KEY is configured; value not displayed\")\nelse:\n    print(\"BAD: MINIMAX_API_KEY is missing\")\nEOF\n```\n\nDo not print the plist or retrieve the keychain item's value. For safe\ncredential handling, follow [cloud-ops-credential-guard](..\u002Fcloud-ops-credential-guard\u002FSKILL.md)\nand the repository's launchd setup workflow.\n\n## Full Diagnostic Steps\n\n### Step 1: Capture the worker's tmux pane\n\n```bash\n# Find the tmux session for the stuck worker\ntmux list-sessions | grep \u003Cworker-name>\n\n# Capture the stuck state\ntmux capture-pane -pt \u003Csession>:0.0 -S -100\n```\n\nLook for: `Please run \u002Flogin`, `API Error: 401`, `login fail`, `MINIMAX_API_KEY`\n\n### Step 2: Check the plist's MINIMAX_API_KEY without displaying it\n\n```bash\npython3 - \"$HOME\u002FLibrary\u002FLaunchAgents\u002Fai.agento.lifecycle-all.plist\" \u003C\u003C'EOF'\nimport plistlib, sys\nwith open(sys.argv[1], \"rb\") as source:\n    data = plistlib.load(source)\nkey = data.get(\"EnvironmentVariables\", {}).get(\"MINIMAX_API_KEY\", \"\")\nif key == \"__OPENCLAW_REDACTED__\":\n    print(\"BAD: redacted sentinel\")\nelif key:\n    print(\"OK: configured; value not displayed\")\nelse:\n    print(\"BAD: missing\")\nEOF\n```\n\n### Step 3: Check keychain for the real key\n\n```bash\n# Check presence without leaking credential to terminal\nsecurity find-generic-password -s MINIMAX_API_KEY >\u002Fdev\u002Fnull 2>&1 && echo \"Keychain: MINIMAX_API_KEY present\" || echo \"Keychain: MINIMAX_API_KEY missing\"\n```\n\nThis check reports presence only. Never retrieve or print the keychain value.\n\n### Step 4: Fix — use the repository's launchd setup workflow\n\n```bash\n# Use the repository's launchd setup to repair the service configuration\nbash scripts\u002Fsetup-launchd.sh lifecycle\n```\n\nDo not copy a credential into a plist or shell variable manually. Follow the\nrepository's launchd setup workflow and the credential-handling rules in\n[cloud-ops-credential-guard](..\u002Fcloud-ops-credential-guard\u002FSKILL.md).\n\n### Step 5: Reload the launchd service\n\n```bash\nlaunchctl bootout gui\u002F$(id -u)\u002Fai.agento.lifecycle-all\nlaunchctl bootstrap gui\u002F$(id -u) ~\u002FLibrary\u002FLaunchAgents\u002Fai.agento.lifecycle-all.plist\nlaunchctl kickstart -k gui\u002F$(id -u)\u002Fai.agento.lifecycle-all\n```\n\n### Step 6: Verify workers recover\n\n```bash\nsleep 5\npgrep -f \"lifecycle-worker\" | wc -l  # Should show 12+ workers\ntmux list-sessions | grep ao-        # Should show active sessions, not stuck on \u002Flogin\n```\n\n## Verify Before Changing the Model\n\nYou might see `model: MiniMax-M2.7` in the config and think \"just switch to Claude Opus.\" A model change does not establish or repair the cause of an authentication error. First:\n\n1. Verify that the current provider response is a 401 and identify which route returned it.\n2. Confirm the active worker configuration and credential-presence status without displaying credential values.\n3. Change model routing only when the current configuration and provider evidence show it is the cause.\n\n## Anti-Patterns\n\n- **WRONG**: `ao spawn --agent codex` to \"fix\" the 401 — masks the symptom, wrong model for the task\n- **WRONG**: `export MINIMAX_API_KEY=...` in a running shell — doesn't fix the launchd service's env\n- **WRONG**: Changing `model` in agent-orchestrator.yaml without evidence that routing is the cause\n- **WRONG**: Killing and respawning the worker without fixing the plist — it will hit the same 401 immediately\n\n## Recurring Incident History\n\n| Date | Worker | Manifestation | Root Cause |\n|------|--------|---------------|------------|\n| 2026-04-15 | PRs #454, #453, #452, #450, #444 | 5 PRs stuck with 401 | `__OPENCLAW_REDACTED__` in plist |\n| 2026-05-01 | ao-4449 (PR #511) | `\u002Flogin` + 401, stuck at \"Brewed for 3m 13s\" | `__OPENCLAW_REDACTED__` in plist |\n\n## Files to Check\n\n- `~\u002FLibrary\u002FLaunchAgents\u002Fai.agento.lifecycle-all.plist` — MINIMAX_API_KEY value\n- `scripts\u002Fsetup-launchd.sh` — how MINIMAX_API_KEY is substituted into the plist\n- `~\u002F.hermes_prod\u002Fconfig.yaml` — MiniMax credential source\n\n## Claim Class\n\nThis skill covers a recurring credential-related failure pattern. Verify the\ncurrent error and active configuration before applying its remediation.\n","# MiniMax 401 Diagnostic\n\n## Common symptom pattern\n\nThis sequence is one possible failure pattern; verify each step from current\nprovider output and worker configuration.\n\n1. AO worker starts → hits MiniMax proxy → proxy returns `401 Unauthorized`\n2. Claude Code intercepts 401 → shows `\u002Flogin` prompt in tmux pane\n3. Worker appears to hang (\"waiting for input\") but is actually blocked on `\u002Flogin`\n4. `tmux capture-pane` shows: `Please run \u002Flogin · API Error: 401` or `login fail: carry the API secret key in the 'Authorization' field`\n5. Config shows `agent: minimax` or `model: MiniMax-M2.7` — this alone does not establish the cause\n\n## Quick Diagnosis\n\n### Step 0 — Plist template check (do this FIRST)\n\n```bash\n# Check for unsubstituted @VAR@ tokens in the installed plist\n# If any exist, bash expands them to empty → 401 on every API call\npython3 - \"$HOME\u002FLibrary\u002FLaunchAgents\u002Fai.agento.lifecycle-all.plist\" \u003C\u003C'EOF'\nimport plistlib, re, sys\ncontent = open(sys.argv[1]).read()\nvars = re.findall(r'@[A-Z_][A-Z0-9_]*@', content)\nif vars:\n    print(f'BAD: Unsubstituted tokens: {sorted(set(vars))}')\nelse:\n    print('OK: No unsubstituted @VAR@ tokens')\nEOF\n\n# If BAD: re-run setup to regenerate plist with real env vars:\nbash scripts\u002Fsetup-launchd.sh lifecycle\n# Then verify:\nbash scripts\u002Ftest-launchd-env.sh\n```\n\nUnsubstituted `@VAR@` tokens establish that the plist template was not rendered.\nUse the repository's launchd setup workflow, then continue diagnosis if the\n401 persists.\n\n```bash\npython3 - \"$HOME\u002FLibrary\u002FLaunchAgents\u002Fai.agento.lifecycle-all.plist\" \u003C\u003C'EOF'\nimport plistlib, re, sys\n\nwith open(sys.argv[1], \"rb\") as source:\n    data = plistlib.load(source)\nvariables = re.findall(r\"@[A-Z_][A-Z0-9_]*@\", str(data))\nkey = data.get(\"EnvironmentVariables\", {}).get(\"MINIMAX_API_KEY\", \"\")\nprint(\"BAD: unsubstituted plist template tokens\" if variables else \"OK: no template tokens\")\nif key == \"__OPENCLAW_REDACTED__\":\n    print(\"BAD: MINIMAX_API_KEY is the redacted sentinel\")\nelif key:\n    print(\"OK: MINIMAX_API_KEY is configured; value not displayed\")\nelse:\n    print(\"BAD: MINIMAX_API_KEY is missing\")\nEOF\n```\n\nDo not print the plist or retrieve the keychain item's value. For safe\ncredential handling, follow [cloud-ops-credential-guard](..\u002Fcloud-ops-credential-guard\u002FSKILL.md)\nand the repository's launchd setup workflow.\n\n## Full Diagnostic Steps\n\n### Step 1: Capture the worker's tmux pane\n\n```bash\n# Find the tmux session for the stuck worker\ntmux list-sessions | grep \u003Cworker-name>\n\n# Capture the stuck state\ntmux capture-pane -pt \u003Csession>:0.0 -S -100\n```\n\nLook for: `Please run \u002Flogin`, `API Error: 401`, `login fail`, `MINIMAX_API_KEY`\n\n### Step 2: Check the plist's MINIMAX_API_KEY without displaying it\n\n```bash\npython3 - \"$HOME\u002FLibrary\u002FLaunchAgents\u002Fai.agento.lifecycle-all.plist\" \u003C\u003C'EOF'\nimport plistlib, sys\nwith open(sys.argv[1], \"rb\") as source:\n    data = plistlib.load(source)\nkey = data.get(\"EnvironmentVariables\", {}).get(\"MINIMAX_API_KEY\", \"\")\nif key == \"__OPENCLAW_REDACTED__\":\n    print(\"BAD: redacted sentinel\")\nelif key:\n    print(\"OK: configured; value not displayed\")\nelse:\n    print(\"BAD: missing\")\nEOF\n```\n\n### Step 3: Check keychain for the real key\n\n```bash\n# Check presence without leaking credential to terminal\nsecurity find-generic-password -s MINIMAX_API_KEY >\u002Fdev\u002Fnull 2>&1 && echo \"Keychain: MINIMAX_API_KEY present\" || echo \"Keychain: MINIMAX_API_KEY missing\"\n```\n\nThis check reports presence only. Never retrieve or print the keychain value.\n\n### Step 4: Fix — use the repository's launchd setup workflow\n\n```bash\n# Use the repository's launchd setup to repair the service configuration\nbash scripts\u002Fsetup-launchd.sh lifecycle\n```\n\nDo not copy a credential into a plist or shell variable manually. Follow the\nrepository's launchd setup workflow and the credential-handling rules in\n[cloud-ops-credential-guard](..\u002Fcloud-ops-credential-guard\u002FSKILL.md).\n\n### Step 5: Reload the launchd service\n\n```bash\nlaunchctl bootout gui\u002F$(id -u)\u002Fai.agento.lifecycle-all\nlaunchctl bootstrap gui\u002F$(id -u) ~\u002FLibrary\u002FLaunchAgents\u002Fai.agento.lifecycle-all.plist\nlaunchctl kickstart -k gui\u002F$(id -u)\u002Fai.agento.lifecycle-all\n```\n\n### Step 6: Verify workers recover\n\n```bash\nsleep 5\npgrep -f \"lifecycle-worker\" | wc -l  # Should show 12+ workers\ntmux list-sessions | grep ao-        # Should show active sessions, not stuck on \u002Flogin\n```\n\n## Verify Before Changing the Model\n\nYou might see `model: MiniMax-M2.7` in the config and think \"just switch to Claude Opus.\" A model change does not establish or repair the cause of an authentication error. First:\n\n1. Verify that the current provider response is a 401 and identify which route returned it.\n2. Confirm the active worker configuration and credential-presence status without displaying credential values.\n3. Change model routing only when the current configuration and provider evidence show it is the cause.\n\n## Anti-Patterns\n\n- **WRONG**: `ao spawn --agent codex` to \"fix\" the 401 — masks the symptom, wrong model for the task\n- **WRONG**: `export MINIMAX_API_KEY=...` in a running shell — doesn't fix the launchd service's env\n- **WRONG**: Changing `model` in agent-orchestrator.yaml without evidence that routing is the cause\n- **WRONG**: Killing and respawning the worker without fixing the plist — it will hit the same 401 immediately\n\n## Recurring Incident History\n\n| Date | Worker | Manifestation | Root Cause |\n|------|--------|---------------|------------|\n| 2026-04-15 | PRs #454, #453, #452, #450, #444 | 5 PRs stuck with 401 | `__OPENCLAW_REDACTED__` in plist |\n| 2026-05-01 | ao-4449 (PR #511) | `\u002Flogin` + 401, stuck at \"Brewed for 3m 13s\" | `__OPENCLAW_REDACTED__` in plist |\n\n## Files to Check\n\n- `~\u002FLibrary\u002FLaunchAgents\u002Fai.agento.lifecycle-all.plist` — MINIMAX_API_KEY value\n- `scripts\u002Fsetup-launchd.sh` — how MINIMAX_API_KEY is substituted into the plist\n- `~\u002F.hermes_prod\u002Fconfig.yaml` — MiniMax credential source\n\n## Claim Class\n\nThis skill covers a recurring credential-related failure pattern. Verify the\ncurrent error and active configuration before applying its remediation.\n",{"name":5,"context":68,"description":7,"when_to_use":69,"allowed-tools":70},"A redacted or invalid MINIMAX_API_KEY in the launchd configuration is one known cause of 401 errors. A \u002Flogin prompt may follow a provider 401, but verify the current response and configuration before concluding that credentials or model routing caused it. Do not swap models as a substitute for diagnosis.","Use when: (1) an AO worker tmux pane shows 'Please run \u002Flogin · API Error: 401' or 'login fail: carry the API secret key', (2) worker is stuck waiting for input despite having 'minimax' model config, (3) \u002Fms surfaces another 401 incident. Do NOT use for general auth issues — this skill is specifically for the MiniMax proxy 401 + \u002Flogin prompt stall pattern.",[53,71,72,73],"Read","Write","Edit","main","42ccd02cbf5e8e47839dc3eab6fc754dc6b339cf",".claude\u002Fskills\u002Fminimax-401-diagnostic",0,"https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills","https:\u002F\u002Fgithub.com\u002Fjleechanorg","2026-11-14 03:18:13",{"source":8,"skillName":5,"commands":82,"prompt":92,"zipAvailable":93},[83,86,89],{"tool":84,"command":85},"npx","npx skills add jleechanorg\u002Fjleechan-skills --skill minimax-401-diagnostic",{"tool":87,"command":88},"bunx","bunx skills add jleechanorg\u002Fjleechan-skills --skill minimax-401-diagnostic",{"tool":90,"command":91},"pnpm","pnpm dlx skills add jleechanorg\u002Fjleechan-skills --skill minimax-401-diagnostic","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fminimax-401-diagnostic\u002FSKILL.md",true,[95,101,107,111],{"path":96,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":99,"sourceHtmlUrl":100},"_sudowork_meta.json","REFERENCE","参考文档",293,"https:\u002F\u002Fgithub.com\u002Fsudoprivacy\u002Fsudowork\u002Fblob\u002Fdev\u002Fapps\u002Fdesktop\u002Fskills\u002F_builtin\u002Fvideo-subtitles\u002F_sudowork_meta.json",{"path":102,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":105,"sourceHtmlUrl":106},"scripts\u002Fcloud_media.py","SCRIPT","脚本",5020,"https:\u002F\u002Fgithub.com\u002Fsudoprivacy\u002Fsudowork\u002Fblob\u002Fdev\u002Fapps\u002Fdesktop\u002Fskills\u002F_builtin\u002Fvideo-subtitles\u002Fscripts\u002Fcloud_media.py",{"path":108,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":109,"sourceHtmlUrl":110},"scripts\u002Frequirements-cloud.txt",33,"https:\u002F\u002Fgithub.com\u002Fsudoprivacy\u002Fsudowork\u002Fblob\u002Fdev\u002Fapps\u002Fdesktop\u002Fskills\u002F_builtin\u002Fvideo-subtitles\u002Fscripts\u002Frequirements-cloud.txt",{"path":112,"resourceType":103,"resourceTypeDesc":104,"sizeBytes":113,"sourceHtmlUrl":114},"scripts\u002Fsubtitles.mjs",4688,"https:\u002F\u002Fgithub.com\u002Fsudoprivacy\u002Fsudowork\u002Fblob\u002Fdev\u002Fapps\u002Fdesktop\u002Fskills\u002F_builtin\u002Fvideo-subtitles\u002Fscripts\u002Fsubtitles.mjs",[116,131,151,165,179,195],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":63},"01M716Y5MTJ6GYJZ2ATXCJK8G4","instinct","Use when the user invokes \u002Finstinct or \u002Fin, or asks to \"message Instinct\", \"ask Instinct\", \"tell Instinct\", \"check Instinct\", or read replies from the configured peer assistant. iMessage first, WhatsApp Web as fallback.","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Finstinct\u002FSKILL.md",[],[118,123,35,124,125,46,126,127,128,50,129,130],"user","replies","check","identity","whatsapp","gmail","message","ask",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":140,"publishedAt":63},"01M716Y4HF7FVVMJSA2CCVN5VF","hr","Compatibility alias for history-resume; produce the same fresh-state, provenance-aware resume briefing.","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fhr\u002FSKILL.md",[137],{"categoryNo":138,"categoryName":139,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000038","人力资源",[133,141,142,143,144,145,146,147,148,149,150],"resume","compatibility","provenance","for","history","produce","alias","briefing","state","fresh",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":158,"publishedAt":63},"01M716Y1FFNFKFJYYKF8HQA6T8","history-resume","Resume briefing for the current repository branch or worktree using fresh state and admitted history sources.","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fhistory-resume\u002FSKILL.md",[157],{"categoryNo":138,"categoryName":139,"taxonomyType":28,"taxonomyTypeDesc":29},[145,141,159,160,123,161,148,162,144,163,164,149,150],"history resume","branch","analysis","repository","worktree","sources",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":171,"publishedAt":63},"01M716XWXJ8EPHK4RH9T14TR85","grok","Alias for the canonical grokbot browser conversation workflow; \u002Fgrok talks to the Grok bot the same way \u002Fdot talks to Dot.","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgrok\u002FSKILL.md",[],[167,172,173,174,144,175,147,176,177,178],"dot","bot","workflow","canonical","conversation","browser","grokbot",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":185,"publishedAt":63},"01M70N9Q07DTE0EW5KFXMMMSJ0","codexa-bench","Compare `codexa` and normal `codex` on a fair split of comparable work by default; use `--strict` for duplicate runs of the exact same task.","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcodexa-bench\u002FSKILL.md",[],[186,187,188,46,189,144,190,191,192,193,194],"codexa bench","work","split","default","duplicate","task","compare","normal","codex",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":199,"licenseFileUrl":200,"sourceHtmlUrl":201,"categories":202,"keywords":212,"publishedAt":63},"01M6C24S2X60SP8BBFGAEKPEGW","frontend-design","Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ffrontend-design\u002FSKILL.md",[203,206,209],{"categoryNo":204,"categoryName":205,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":207,"categoryName":208,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":210,"categoryName":211,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000032","设计师",[213,214,215,46,216,217,218,123,219,220,221,222,223,224,225,226,227,228,229,230,231,232,233,234,235,236,35,237],"frontend","design","frontend design","generic","ui design","react","html","components","code","artifacts","ui","aesthetics","Production","web components","landing","applications","quality","web","css","create","examples","with","react components","web ui","pages"]