[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C2DFMEZ7AWKA6E0Z6AF2F5":3,"skill-same:01M6C2DFMEZ7AWKA6E0Z6AF2F5":56},{"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":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":41,"install":42,"resources":55},"01M6C2DFMEZ7AWKA6E0Z6AF2F5","skillify",null,"Use when creating or updating a reusable Claude skill, deciding whether a workflow belongs in a skill, or exporting a requested skill package.","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\u002Fskillify\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[5,23,24,25,26,27,28,29],"workflow","package","use","reusable","claude skill","skill package","when","2026-11-10 10:12:30",false,"---\nname: skillify\ndescription: Use when creating or updating a reusable Claude skill, deciding whether a workflow belongs in a skill, or exporting a requested skill package.\n---\n\n# Skillify\n\n## Retained review integrations\n\nThe shared catalog preserves host-installed `\u002Fadvice` and `\u002Fweb-advice` integrations instead of installing them. Before invoking either, resolve its `..\u002Fadvice\u002FSKILL.md` or `..\u002Fweb-advice\u002FSKILL.md` relative to this package and read the existing skill. For a remote invocation, check the corresponding skill on the target host. If absent, report that integration as `UNAVAILABLE` and identify the missing package; do not invent a replacement runner, claim an approval, or treat a required gate as passed. Continue independent authorized work, but leave any dependent readiness or plan-approval gate unmet. Existing review quorum, external-disclosure authorization, and optional-review rules still apply.\n\n\nCreate or improve one reusable Claude skill with the smallest coherent change.\nThe canonical source for shared Claude skills is\n`~\u002F.claude\u002Fskills\u002F\u003Cname>\u002FSKILL.md` (or the explicitly selected native Claude\nhome when the user names one).\n\n## Contract\n\n- Reuse before create. Inspect the target and nearby skills before choosing a\n  name or adding a package. Update the actual owner when one exists.\n- Inspect both the live Claude home and the repository or export source. Follow\n  symlinks and record which path is canonical; do not infer ownership from a\n  copied file, archive, or stale report.\n- `~\u002F.claude\u002Fskills\u002F` is the Claude source of truth when the request names the\n  normal Claude home; an explicitly selected native Claude home is honored.\n  `${HOME}\u002F.codex\u002Fskills\u002F` and `${HOME}\u002F.agents\u002Fskills\u002F` are projection paths\n  only when they are symlinks to that source. Never write independent copies\n  there.\n- A skill package has one `SKILL.md` at its package root. Do not create a\n  nested `SKILL.md` under another skill, and keep backups outside every active\n  skill-discovery root.\n- A slash command is optional. If one is needed, keep it a thin pointer that\n  reads the canonical skill and forwards `$ARGUMENTS`; put the workflow in the\n  skill. Do not add a command merely to satisfy a checklist.\n- Hermes is an explicit contextual route. Use it only when the user or native\n  Hermes instructions select it, and follow that runtime's own resolver and\n  packaging rules. Do not apply gbrain, Hermes, resolver, or brain requirements\n  to every Claude skill.\n\n## Steps\n\n### 1. Discover the owner\n\nRead the requested target and its nearest existing pattern. Inspect the live\nClaude path, the repository path, and any symlink targets. Search for a\nsame-purpose skill or command before creating a name. Classify the target as\none of:\n\n- existing canonical skill to update;\n- existing skill that should be reused without a new package; or\n- genuinely new Claude skill.\n\nIf the user requests an export, resolve the requested package's dependency\nclosure first. Export only that package and closure into an isolated skills\nrepository worktree; preserve unrelated dirty files, home changes, and remote\nstate.\n\n### 2. Author the minimum useful skill\n\nKeep `SKILL.md` concise and operational. Its frontmatter contains only the\nportable `name` and `description`, with the directory name matching `name`.\nThe description states when the skill applies and uses terms a user would\nactually say. The body should explain the purpose, decision boundaries,\nordered actions, and output or evidence contract.\n\nAdd a `references\u002F` or `scripts\u002F` file only when it has concrete reuse value.\nDo not invent deterministic code, tests, evals, resolver entries, brain or\nmemory filings, services, schemas, or artifacts that the target and request do\nnot need. Do not move model judgment into keyword, regex, score, or hardcoded\nrouting logic.\n\nFor a command, use the existing local dispatcher form, for example:\n\n```markdown\n---\nname: skillify\ndescription: Use when creating or updating a reusable Claude skill.\n---\n\nRead `${CLAUDE_HOME:-$HOME\u002F.claude}\u002Fskills\u002Fskillify\u002FSKILL.md` completely, then execute it with `$ARGUMENTS`.\n```\n\n### 3. Validate proportionately\n\nFor instruction-only edits, run structural and spelling checks and inspect the\nrendered frontmatter. Check any command locally before documenting it; do not\nencode a guessed path or flag. Run an existing targeted test when it covers\nthe changed export or dispatcher. Export changes also run the relevant\ninstaller and portability checks already present in the repository.\n\nFor behavior changes, capture a baseline and candidate using realistic\npressure scenarios that exercise the requested boundary. Run an independent\nforward check against the candidate. Confirm that the skill preserves existing\nauthorization, autonomy, evidence, and user-visible failure boundaries. A\nwritten checklist or self-report is not independent proof.\n\nThere is no fixed completeness score. Mark each applicable validation as\npassed, failed, or not applicable with its reason. Do not claim a resolver,\ntest, integration, or runtime result when that capability was not run.\n\n### 4. Reconcile and export safely\n\nBefore replacing an existing canonical file, make a recoverable backup outside\nevery active discovery root and record its path. An ignored file inside a\nskills tree is still unsafe as a backup. Inspect the export diff for scope,\nfrontmatter, symlink, and dependency errors. Test the staged export in its\nisolated worktree, then promote it only when the user has authorized that\npromotion. After promotion or synchronization, hash the exact artifact and\nread it back from every requested destination to confirm identical content.\n\nHonor the user's requested PR, `\u002Fadvice`, `\u002Fwa`, merge, and synchronization\nscope. Do not invent an additional approval or a self-recursive ironclad or\nskillify loop. An explicit merge or sync authorization does not authorize\nunrelated packages, home writes, force-pushes, or destructive cleanup.\n\n## Output\n\nReport the canonical owner, whether the skill was reused or created, the files\nchanged, applicable checks and their fresh results, and any requested export\nor synchronization paths with hashes and readback results. State blockers as a\nspecific unmet authority or failed check, and leave unrelated work untouched.\n","# Skillify\n\n## Retained review integrations\n\nThe shared catalog preserves host-installed `\u002Fadvice` and `\u002Fweb-advice` integrations instead of installing them. Before invoking either, resolve its `..\u002Fadvice\u002FSKILL.md` or `..\u002Fweb-advice\u002FSKILL.md` relative to this package and read the existing skill. For a remote invocation, check the corresponding skill on the target host. If absent, report that integration as `UNAVAILABLE` and identify the missing package; do not invent a replacement runner, claim an approval, or treat a required gate as passed. Continue independent authorized work, but leave any dependent readiness or plan-approval gate unmet. Existing review quorum, external-disclosure authorization, and optional-review rules still apply.\n\n\nCreate or improve one reusable Claude skill with the smallest coherent change.\nThe canonical source for shared Claude skills is\n`~\u002F.claude\u002Fskills\u002F\u003Cname>\u002FSKILL.md` (or the explicitly selected native Claude\nhome when the user names one).\n\n## Contract\n\n- Reuse before create. Inspect the target and nearby skills before choosing a\n  name or adding a package. Update the actual owner when one exists.\n- Inspect both the live Claude home and the repository or export source. Follow\n  symlinks and record which path is canonical; do not infer ownership from a\n  copied file, archive, or stale report.\n- `~\u002F.claude\u002Fskills\u002F` is the Claude source of truth when the request names the\n  normal Claude home; an explicitly selected native Claude home is honored.\n  `${HOME}\u002F.codex\u002Fskills\u002F` and `${HOME}\u002F.agents\u002Fskills\u002F` are projection paths\n  only when they are symlinks to that source. Never write independent copies\n  there.\n- A skill package has one `SKILL.md` at its package root. Do not create a\n  nested `SKILL.md` under another skill, and keep backups outside every active\n  skill-discovery root.\n- A slash command is optional. If one is needed, keep it a thin pointer that\n  reads the canonical skill and forwards `$ARGUMENTS`; put the workflow in the\n  skill. Do not add a command merely to satisfy a checklist.\n- Hermes is an explicit contextual route. Use it only when the user or native\n  Hermes instructions select it, and follow that runtime's own resolver and\n  packaging rules. Do not apply gbrain, Hermes, resolver, or brain requirements\n  to every Claude skill.\n\n## Steps\n\n### 1. Discover the owner\n\nRead the requested target and its nearest existing pattern. Inspect the live\nClaude path, the repository path, and any symlink targets. Search for a\nsame-purpose skill or command before creating a name. Classify the target as\none of:\n\n- existing canonical skill to update;\n- existing skill that should be reused without a new package; or\n- genuinely new Claude skill.\n\nIf the user requests an export, resolve the requested package's dependency\nclosure first. Export only that package and closure into an isolated skills\nrepository worktree; preserve unrelated dirty files, home changes, and remote\nstate.\n\n### 2. Author the minimum useful skill\n\nKeep `SKILL.md` concise and operational. Its frontmatter contains only the\nportable `name` and `description`, with the directory name matching `name`.\nThe description states when the skill applies and uses terms a user would\nactually say. The body should explain the purpose, decision boundaries,\nordered actions, and output or evidence contract.\n\nAdd a `references\u002F` or `scripts\u002F` file only when it has concrete reuse value.\nDo not invent deterministic code, tests, evals, resolver entries, brain or\nmemory filings, services, schemas, or artifacts that the target and request do\nnot need. Do not move model judgment into keyword, regex, score, or hardcoded\nrouting logic.\n\nFor a command, use the existing local dispatcher form, for example:\n\n```markdown\n---\nname: skillify\ndescription: Use when creating or updating a reusable Claude skill.\n---\n\nRead `${CLAUDE_HOME:-$HOME\u002F.claude}\u002Fskills\u002Fskillify\u002FSKILL.md` completely, then execute it with `$ARGUMENTS`.\n```\n\n### 3. Validate proportionately\n\nFor instruction-only edits, run structural and spelling checks and inspect the\nrendered frontmatter. Check any command locally before documenting it; do not\nencode a guessed path or flag. Run an existing targeted test when it covers\nthe changed export or dispatcher. Export changes also run the relevant\ninstaller and portability checks already present in the repository.\n\nFor behavior changes, capture a baseline and candidate using realistic\npressure scenarios that exercise the requested boundary. Run an independent\nforward check against the candidate. Confirm that the skill preserves existing\nauthorization, autonomy, evidence, and user-visible failure boundaries. A\nwritten checklist or self-report is not independent proof.\n\nThere is no fixed completeness score. Mark each applicable validation as\npassed, failed, or not applicable with its reason. Do not claim a resolver,\ntest, integration, or runtime result when that capability was not run.\n\n### 4. Reconcile and export safely\n\nBefore replacing an existing canonical file, make a recoverable backup outside\nevery active discovery root and record its path. An ignored file inside a\nskills tree is still unsafe as a backup. Inspect the export diff for scope,\nfrontmatter, symlink, and dependency errors. Test the staged export in its\nisolated worktree, then promote it only when the user has authorized that\npromotion. After promotion or synchronization, hash the exact artifact and\nread it back from every requested destination to confirm identical content.\n\nHonor the user's requested PR, `\u002Fadvice`, `\u002Fwa`, merge, and synchronization\nscope. Do not invent an additional approval or a self-recursive ironclad or\nskillify loop. An explicit merge or sync authorization does not authorize\nunrelated packages, home writes, force-pushes, or destructive cleanup.\n\n## Output\n\nReport the canonical owner, whether the skill was reused or created, the files\nchanged, applicable checks and their fresh results, and any requested export\nor synchronization paths with hashes and readback results. State blockers as a\nspecific unmet authority or failed check, and leave unrelated work untouched.\n",{"name":5,"description":7},"main","42ccd02cbf5e8e47839dc3eab6fc754dc6b339cf",".claude\u002Fskills\u002Fskillify",0,"https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills","https:\u002F\u002Fgithub.com\u002Fjleechanorg","2026-11-11 22:19:36",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add jleechanorg\u002Fjleechan-skills --skill skillify",{"tool":48,"command":49},"bunx","bunx skills add jleechanorg\u002Fjleechan-skills --skill skillify",{"tool":51,"command":52},"pnpm","pnpm dlx skills add jleechanorg\u002Fjleechan-skills --skill skillify","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fskillify\u002FSKILL.md",true,[],[57,73,95,109,122,138],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":30},"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",[],[59,64,29,65,66,25,67,68,69,70,71,72],"user","replies","check","identity","whatsapp","gmail","read","message","ask",{"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":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":84,"publishedAt":30},"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",[79],{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[75,85,86,87,88,89,90,91,92,93,94],"resume","compatibility","provenance","for","history","produce","alias","briefing","state","fresh",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":102,"publishedAt":30},"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",[101],{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},[89,85,103,104,64,105,92,106,88,107,108,93,94],"history resume","branch","analysis","repository","worktree","sources",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":30},"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",[],[111,116,117,23,88,118,91,119,120,121],"dot","bot","canonical","conversation","browser","grokbot",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":30},"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",[],[129,130,131,25,132,88,133,134,135,136,137],"codexa bench","work","split","default","duplicate","task","compare","normal","codex",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":142,"licenseFileUrl":143,"sourceHtmlUrl":144,"categories":145,"keywords":155,"publishedAt":30},"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",[146,149,152],{"categoryNo":147,"categoryName":148,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":150,"categoryName":151,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":153,"categoryName":154,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000032","设计师",[156,157,158,25,159,160,161,64,162,163,164,165,166,167,168,169,170,171,172,173,174,175,176,177,178,179,29,180],"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"]