[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CARSZP2DDPWMQ40P5NHN4E":3,"skill-same:01M6CARSZP2DDPWMQ40P5NHN4E":102},{"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":22,"publishedAt":53,"linkOnly":54,"markdownContent":55,"markdownBody":56,"frontMatter":57,"refName":75,"commitSha":76,"skillDirectory":77,"forksCount":78,"repositoryHtmlUrl":79,"repositoryHomepageUrl":6,"ownerHtmlUrl":80,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":81,"install":82,"resources":95},"01M6CARSZP2DDPWMQ40P5NHN4E","stale-skill-audit",null,"Audit an existing SKILL.md for stale content and produce a safe-subset cleanup PR — drop dead Provenance footers, swap drifted canonical names (bd→br), normalize header dates, never rewrite content. Use when the user says 'cleanup this skill', 'this skill is bloated', names a specific skill that drifted, or a scheduled `agent-agent-mistakes` review flagged a file. Triggers: 'cleanup this skill', 'prune this skill', 'this skill is bloated', 'audit stale skill content', 'normalize dates in SKILL.md', 'swap bd to br', 'safe subset cleanup'.","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\u002Fhermes\u002Fskills\u002Fsoftware-development\u002Fstale-skill-audit\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52],"skill audit","stale skill audit","stale","audit","postmortem","when","br","scheduled","canonical","hermes-agent","authoring","drop","never","use","session","distill","review","prune","simplify","provenance","file","produce","harness","code","learn","cleanup","pr","windows","linux","safe","2026-11-10 10:12:30",false,"---\nname: stale-skill-audit\nversion: 1.0.0\nauthor: Hermes Agent\nlicense: MIT\nplatforms: [linux, macos, windows]\ndescription: \"Audit an existing SKILL.md for stale content and produce a safe-subset cleanup PR — drop dead Provenance footers, swap drifted canonical names (bd→br), normalize header dates, never rewrite content. Use when the user says 'cleanup this skill', 'this skill is bloated', names a specific skill that drifted, or a scheduled `agent-agent-mistakes` review flagged a file. Triggers: 'cleanup this skill', 'prune this skill', 'this skill is bloated', 'audit stale skill content', 'normalize dates in SKILL.md', 'swap bd to br', 'safe subset cleanup'.\"\nmetadata:\n  hermes:\n    tags: [skills, audit, cleanup, maintenance, staleness, sediment]\n    related_skills: [hermes-agent-skill-authoring, skillify, simplify-code, session-learn-distill, harness-postmortem]\n---\n\n# Stale-Skill Audit — Safe-Subset Cleanup for an Existing SKILL.md\n\nSkills accumulate **sediment**: dead Provenance footers, drifted CLI names, header dates that pin to a specific moment in time, WIP-forward language, and content-meaning edits that no longer pull their weight. This skill is the recipe for a single PR that removes the sediment **without rewriting the skill**.\n\n**Default philosophy: safe subset only.** No paragraph removal, no rule reordering, no content-meaning edits. Drop dead audit data, swap drifted names, normalize header dates. Stop there unless the user explicitly escalates.\n\n## When to Use\n\n- User says \"cleanup this skill\" \u002F \"prune this skill\" \u002F \"this skill is bloated\" \u002F \"audit stale skill content\".\n- User names a specific SKILL.md that drifted from current org conventions.\n- A scheduled `agent-agent-mistakes` or `meta-autonomy-violation-handler` review flagged a file.\n- The org changed canonical CLIs, paths, or defaults and a skill still references the old ones (e.g. `bd` → `br`).\n- The skill's description is approaching 1024 chars (validator forces a rewrite — may as well clean the body too).\n\n**Do NOT use this** for:\n- Proactive \"this looks old\" cleanup without a signal. Unsolicited cleanup PRs don't merge.\n- *Creating* a new skill (use `skillify`).\n- *Simplifying code* (use `simplify-code` — that one is for code, not docs).\n- Promoting local user-scope additions to the repo (separate \"promote to repo\" PR, not a cleanup PR).\n\n## Quick Start\n\n1. **Find the canonical file.** Check both `~\u002F.claude\u002Fskills\u002F\u003Cname>\u002FSKILL.md` (user-scope local) and the repo's `.claude\u002Fskills\u002F\u003Cname>\u002FSKILL.md` (remote canonical). They often drift.\n2. **Run the indicator greps** (see `references\u002Fstaleness-audit.md`). Each hit is a candidate edit.\n3. **Classify each hit:**\n   - Header\u002Fframe (description, lead-in, table title): normalize or drop.\n   - Incident-anchored (mid-rule, with a specific defect class or example): keep verbatim — it's load-bearing evidence.\n   - Provenance\u002Faudit footer: drop the whole section.\n4. **Apply minimal patches** with `patch` (or `skill_manage` action='patch' for in-repo skills). `replace_all=true` only when every occurrence is unambiguously the same edit (e.g. `bd` → `br`).\n5. **Edit local first** (`~\u002F.claude\u002Fskills\u002F\u003Cname>\u002FSKILL.md`) — user's local sessions read it.\n6. **Propagate to remote** via `github-pr-workflow` (branch from `origin\u002Fmain`, commit, push, `gh pr create`). Do NOT include user-scope local additions — those are content additions, not cleanups.\n7. **Verify:** `gh pr view N --json headRefOid --jq .headRefOid` matches local SHA; indicator greps on the remote head return 0 hits for `bd`, `Provenance` header, and unnormalized `2026-07-06` header dates.\n\nThe full recipe (exact grep commands, classification rules, foreign-checkout pitfall, and the safe-subset edge cases) is in `references\u002Fstaleness-audit.md`.\n\n## The Safe-Subset Contract\n\n| Edit | In safe subset? | Why |\n|---|---|---|\n| Drop `## Provenance` footer (dead runIds, bead IDs, SHA, PR URL) | ✓ | LLM has no way to resolve dead audit data |\n| `bd` → `br` when org migrated | ✓ | Drift fix; org-canonical CLI |\n| Header date `2026-07-06` → `2026-07` (description, lead-in, table cells) | ✓ | Header dates are pinpoints, not evidence |\n| Incident-anchored date inside a rule body | ✗ keep verbatim | The date is evidence the rule is battle-tested |\n| Typo that changes meaning (\"province\" → \"provenance\") | ✓ | Mechanical fix |\n| WIP-forward language (\"in progress as of ...\", \"TODO: \", \"TBD\") | ✓ | Ages badly; replace with current-state wording or drop |\n| Removing a paragraph | ✗ escalate | Content-meaning edit — ask user first |\n| Reordering rules | ✗ escalate | Content-meaning edit |\n| Promoting a user-scope local addition to the repo | ✗ separate PR | That's a content-addition PR, not a cleanup PR |\n\n## Pitfalls\n\n1. **\"Medium cleanup\" is not the default.** When the user says \"let's cleanup\", assume safe subset unless they explicitly escalate. Offer 2-3 scope options at most — don't make them pick from 4. If they pull back mid-conversation, narrow immediately, don't re-confirm.\n2. **Header dates ≠ incident dates.** Stripping `2026-07-07` from a rule that says \"Hit twice on 2026-07-07: `pr-retro-gapfill` (15\u002F15 verify agents died, ...)\" removes the *evidence the rule is battle-tested*. That date is load-bearing. Header\u002Fframe dates are safe to normalize.\n3. **`bd` → `br` is not always safe.** Confirm against `~\u002F.claude\u002FCLAUDE.md` and `projects\u002FAGENTS.md` before sweeping. Some projects genuinely still use `bd`.\n4. **Don't edit a foreign repo's live checkout in place.** It may be on someone else's branch with dirty work. Clone into `~\u002F.hermes\u002Fstate\u002Fworktrees\u002F\u003Crepo>` and work from there; no approval phrase is required to change directories.\n5. **Don't conflate local and remote.** The user-scope file at `~\u002F.claude\u002Fskills\u002F\u003Cname>\u002FSKILL.md` may have *more* recent additions than the remote (Domain-general paragraphs, new rules added locally). Treat the remote as canonical for the cleanup PR; flag the local additions in the PR description under \"Out of scope\" so the user can promote them separately.\n6. **`git rev-parse origin\u002F\u003Cbranch>` lies after a fresh push.** The local ref-cache doesn't update immediately. Verify with `gh pr view N --json headRefOid` instead, or `git fetch origin \u003Cbranch>` first.\n7. **Don't auto-run a sweep of every skill.** The user knows what's stale to them. A single targeted cleanup PR is welcome; a \"I cleaned 14 skills at once\" PR is not.\n\n## Verification Checklist\n\n- [ ] Local user-scope file (`~\u002F.claude\u002Fskills\u002F\u003Cname>\u002FSKILL.md`) edited first\n- [ ] Each `references\u002Fstaleness-audit.md` indicator grep run against both local and remote files\n- [ ] Each hit classified as header-frame \u002F incident-anchored \u002F provenance-audit \u002F typo\n- [ ] No content-meaning edits in the PR (paragraph removal, rule reordering, content additions)\n- [ ] Local additions flagged in PR description under \"Out of scope\" if they exist\n- [ ] Branch created from `origin\u002Fmain` (per `pr-branch-from-main.mdc`)\n- [ ] PR created via `gh pr create` with full description (What changed, why, out of scope, stats)\n- [ ] `gh pr view N --json headRefOid` matches local HEAD SHA\n- [ ] Indicator greps on the remote head return 0 hits for `bd`, `Provenance` header, and unnormalized `2026-07-06` header dates\n- [ ] CodeRabbit \u002F CI pre-checks all pass\n\n## Related\n\n- `hermes-agent-skill-authoring` — peer skill on authoring conventions; this skill is its **maintenance** counterpart.\n- `skillify` — the 11-item completeness contract for *creating* new skills. Use when adding a new skill; use this one when pruning an old one.\n- `simplify-code` — parallel 3-agent cleanup of recent code changes. Code, not skills.\n- `session-learn-distill` — post-session \u002Flearn extraction. Run after a cleanup PR merges to capture what was learned.\n- `harness-postmortem` — slash `\u002Fmeta` for agent behavior failures. Different scope (the harness, not the skills).\n\n## Support files\n\n- **`references\u002Fstaleness-audit.md`** — the full 5-phase recipe with exact grep commands, the 8 indicator patterns, the safe-subset classification table, the worked 2026-07-06 example, and edge cases (multi-skill PRs, skill-vs-repo-only, SOUL.md cross-references). Load this before any cleanup that touches more than one indicator hit.","# Stale-Skill Audit — Safe-Subset Cleanup for an Existing SKILL.md\n\nSkills accumulate **sediment**: dead Provenance footers, drifted CLI names, header dates that pin to a specific moment in time, WIP-forward language, and content-meaning edits that no longer pull their weight. This skill is the recipe for a single PR that removes the sediment **without rewriting the skill**.\n\n**Default philosophy: safe subset only.** No paragraph removal, no rule reordering, no content-meaning edits. Drop dead audit data, swap drifted names, normalize header dates. Stop there unless the user explicitly escalates.\n\n## When to Use\n\n- User says \"cleanup this skill\" \u002F \"prune this skill\" \u002F \"this skill is bloated\" \u002F \"audit stale skill content\".\n- User names a specific SKILL.md that drifted from current org conventions.\n- A scheduled `agent-agent-mistakes` or `meta-autonomy-violation-handler` review flagged a file.\n- The org changed canonical CLIs, paths, or defaults and a skill still references the old ones (e.g. `bd` → `br`).\n- The skill's description is approaching 1024 chars (validator forces a rewrite — may as well clean the body too).\n\n**Do NOT use this** for:\n- Proactive \"this looks old\" cleanup without a signal. Unsolicited cleanup PRs don't merge.\n- *Creating* a new skill (use `skillify`).\n- *Simplifying code* (use `simplify-code` — that one is for code, not docs).\n- Promoting local user-scope additions to the repo (separate \"promote to repo\" PR, not a cleanup PR).\n\n## Quick Start\n\n1. **Find the canonical file.** Check both `~\u002F.claude\u002Fskills\u002F\u003Cname>\u002FSKILL.md` (user-scope local) and the repo's `.claude\u002Fskills\u002F\u003Cname>\u002FSKILL.md` (remote canonical). They often drift.\n2. **Run the indicator greps** (see `references\u002Fstaleness-audit.md`). Each hit is a candidate edit.\n3. **Classify each hit:**\n   - Header\u002Fframe (description, lead-in, table title): normalize or drop.\n   - Incident-anchored (mid-rule, with a specific defect class or example): keep verbatim — it's load-bearing evidence.\n   - Provenance\u002Faudit footer: drop the whole section.\n4. **Apply minimal patches** with `patch` (or `skill_manage` action='patch' for in-repo skills). `replace_all=true` only when every occurrence is unambiguously the same edit (e.g. `bd` → `br`).\n5. **Edit local first** (`~\u002F.claude\u002Fskills\u002F\u003Cname>\u002FSKILL.md`) — user's local sessions read it.\n6. **Propagate to remote** via `github-pr-workflow` (branch from `origin\u002Fmain`, commit, push, `gh pr create`). Do NOT include user-scope local additions — those are content additions, not cleanups.\n7. **Verify:** `gh pr view N --json headRefOid --jq .headRefOid` matches local SHA; indicator greps on the remote head return 0 hits for `bd`, `Provenance` header, and unnormalized `2026-07-06` header dates.\n\nThe full recipe (exact grep commands, classification rules, foreign-checkout pitfall, and the safe-subset edge cases) is in `references\u002Fstaleness-audit.md`.\n\n## The Safe-Subset Contract\n\n| Edit | In safe subset? | Why |\n|---|---|---|\n| Drop `## Provenance` footer (dead runIds, bead IDs, SHA, PR URL) | ✓ | LLM has no way to resolve dead audit data |\n| `bd` → `br` when org migrated | ✓ | Drift fix; org-canonical CLI |\n| Header date `2026-07-06` → `2026-07` (description, lead-in, table cells) | ✓ | Header dates are pinpoints, not evidence |\n| Incident-anchored date inside a rule body | ✗ keep verbatim | The date is evidence the rule is battle-tested |\n| Typo that changes meaning (\"province\" → \"provenance\") | ✓ | Mechanical fix |\n| WIP-forward language (\"in progress as of ...\", \"TODO: \", \"TBD\") | ✓ | Ages badly; replace with current-state wording or drop |\n| Removing a paragraph | ✗ escalate | Content-meaning edit — ask user first |\n| Reordering rules | ✗ escalate | Content-meaning edit |\n| Promoting a user-scope local addition to the repo | ✗ separate PR | That's a content-addition PR, not a cleanup PR |\n\n## Pitfalls\n\n1. **\"Medium cleanup\" is not the default.** When the user says \"let's cleanup\", assume safe subset unless they explicitly escalate. Offer 2-3 scope options at most — don't make them pick from 4. If they pull back mid-conversation, narrow immediately, don't re-confirm.\n2. **Header dates ≠ incident dates.** Stripping `2026-07-07` from a rule that says \"Hit twice on 2026-07-07: `pr-retro-gapfill` (15\u002F15 verify agents died, ...)\" removes the *evidence the rule is battle-tested*. That date is load-bearing. Header\u002Fframe dates are safe to normalize.\n3. **`bd` → `br` is not always safe.** Confirm against `~\u002F.claude\u002FCLAUDE.md` and `projects\u002FAGENTS.md` before sweeping. Some projects genuinely still use `bd`.\n4. **Don't edit a foreign repo's live checkout in place.** It may be on someone else's branch with dirty work. Clone into `~\u002F.hermes\u002Fstate\u002Fworktrees\u002F\u003Crepo>` and work from there; no approval phrase is required to change directories.\n5. **Don't conflate local and remote.** The user-scope file at `~\u002F.claude\u002Fskills\u002F\u003Cname>\u002FSKILL.md` may have *more* recent additions than the remote (Domain-general paragraphs, new rules added locally). Treat the remote as canonical for the cleanup PR; flag the local additions in the PR description under \"Out of scope\" so the user can promote them separately.\n6. **`git rev-parse origin\u002F\u003Cbranch>` lies after a fresh push.** The local ref-cache doesn't update immediately. Verify with `gh pr view N --json headRefOid` instead, or `git fetch origin \u003Cbranch>` first.\n7. **Don't auto-run a sweep of every skill.** The user knows what's stale to them. A single targeted cleanup PR is welcome; a \"I cleaned 14 skills at once\" PR is not.\n\n## Verification Checklist\n\n- [ ] Local user-scope file (`~\u002F.claude\u002Fskills\u002F\u003Cname>\u002FSKILL.md`) edited first\n- [ ] Each `references\u002Fstaleness-audit.md` indicator grep run against both local and remote files\n- [ ] Each hit classified as header-frame \u002F incident-anchored \u002F provenance-audit \u002F typo\n- [ ] No content-meaning edits in the PR (paragraph removal, rule reordering, content additions)\n- [ ] Local additions flagged in PR description under \"Out of scope\" if they exist\n- [ ] Branch created from `origin\u002Fmain` (per `pr-branch-from-main.mdc`)\n- [ ] PR created via `gh pr create` with full description (What changed, why, out of scope, stats)\n- [ ] `gh pr view N --json headRefOid` matches local HEAD SHA\n- [ ] Indicator greps on the remote head return 0 hits for `bd`, `Provenance` header, and unnormalized `2026-07-06` header dates\n- [ ] CodeRabbit \u002F CI pre-checks all pass\n\n## Related\n\n- `hermes-agent-skill-authoring` — peer skill on authoring conventions; this skill is its **maintenance** counterpart.\n- `skillify` — the 11-item completeness contract for *creating* new skills. Use when adding a new skill; use this one when pruning an old one.\n- `simplify-code` — parallel 3-agent cleanup of recent code changes. Code, not skills.\n- `session-learn-distill` — post-session \u002Flearn extraction. Run after a cleanup PR merges to capture what was learned.\n- `harness-postmortem` — slash `\u002Fmeta` for agent behavior failures. Different scope (the harness, not the skills).\n\n## Support files\n\n- **`references\u002Fstaleness-audit.md`** — the full 5-phase recipe with exact grep commands, the 8 indicator patterns, the safe-subset classification table, the worked 2026-07-06 example, and edge cases (multi-skill PRs, skill-vs-repo-only, SOUL.md cross-references). Load this before any cleanup that touches more than one indicator hit.",{"name":5,"author":58,"license":14,"version":59,"metadata":60,"platforms":73,"description":7},"Hermes Agent","1.0.0",{"hermes":61},{"tags":62,"related_skills":67},[63,26,48,64,65,66],"skills","maintenance","staleness","sediment",[68,69,70,71,72],"hermes-agent-skill-authoring","skillify","simplify-code","session-learn-distill","harness-postmortem",[51,74,50],"macos","main","05df7380981a2c4af868ce0fa57962ae0eea62a9","hermes\u002Fskills\u002Fsoftware-development\u002Fstale-skill-audit",0,"https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills","https:\u002F\u002Fgithub.com\u002Fjleechanorg","2026-11-11 09:18:40",{"source":8,"skillName":5,"commands":83,"prompt":93,"zipAvailable":94},[84,87,90],{"tool":85,"command":86},"npx","npx skills add jleechanorg\u002Fjleechan-skills --skill stale-skill-audit",{"tool":88,"command":89},"bunx","bunx skills add jleechanorg\u002Fjleechan-skills --skill stale-skill-audit",{"tool":91,"command":92},"pnpm","pnpm dlx skills add jleechanorg\u002Fjleechan-skills --skill stale-skill-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Fsoftware-development\u002Fstale-skill-audit\u002FSKILL.md",true,[96],{"path":97,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fstaleness-audit.md","REFERENCE","参考文档",11314,"https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Fsoftware-development\u002Fstale-skill-audit\u002Freferences\u002Fstaleness-audit.md",[103,119,139,153,166,182],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":53},"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",[],[105,110,28,111,112,36,113,114,115,116,117,118],"user","replies","check","identity","whatsapp","gmail","read","message","ask",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":130,"publishedAt":53},"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",[125],{"categoryNo":126,"categoryName":127,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[121,131,132,42,133,134,44,135,136,137,138],"resume","compatibility","for","history","alias","briefing","state","fresh",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":146,"publishedAt":53},"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",[145],{"categoryNo":126,"categoryName":127,"taxonomyType":128,"taxonomyTypeDesc":129},[134,131,147,148,110,149,136,150,133,151,152,137,138],"history resume","branch","analysis","repository","worktree","sources",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":53},"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",[],[155,160,161,162,133,31,135,163,164,165],"dot","bot","workflow","conversation","browser","grokbot",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":172,"publishedAt":53},"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",[],[173,174,175,36,176,133,177,178,179,180,181],"codexa bench","work","split","default","duplicate","task","compare","normal","codex",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":186,"licenseFileUrl":187,"sourceHtmlUrl":188,"categories":189,"keywords":199,"publishedAt":53},"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",[190,193,196],{"categoryNo":191,"categoryName":192,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":194,"categoryName":195,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":197,"categoryName":198,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000032","设计师",[200,201,202,36,203,204,205,110,206,207,46,208,209,210,211,212,213,214,215,216,217,218,219,220,221,222,28,223],"frontend","design","frontend design","generic","ui design","react","html","components","artifacts","ui","aesthetics","Production","web components","landing","applications","quality","web","css","create","examples","with","react components","web ui","pages"]