[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6K0RXZB4N96ZPB4JCSKBKHZ":3,"skill-same:01M6K0RXZB4N96ZPB4JCSKBKHZ":102},{"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":23,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":70,"commitSha":71,"skillDirectory":72,"forksCount":73,"repositoryHtmlUrl":74,"repositoryHomepageUrl":6,"ownerHtmlUrl":75,"ownerBlogUrl":6,"ownerDescription":76,"updatedAt":77,"install":78,"resources":91},"01M6K0RXZB4N96ZPB4JCSKBKHZ","skill-creator",null,"帮用户创建、拆分、审查和改写 xiaok skill，尤其适合目标模糊、scope 过大或不知道 skill 原则的时候","kaisersong\u002Fxiaok-cli","kaisersong","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F4091099?v=4","01M6K0R4Q69MQEAE0ZNYVPFTP3","Kaiser","01M6K0R4W7XF0VQAMTDVC77WYM",17,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fkaisersong\u002Fxiaok-cli\u002Fblob\u002Fmaster\u002Fdata\u002Fskills\u002Fskill-creator\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"creator","skill creator","refine","new","when","vague","Existing","split","recommendation","scope","draft","structure","use","edit","write","read","improve","release","routing","create","workflow","review","2026-11-10 10:12:30",false,"---\nname: skill-creator\ndescription: 帮用户创建、拆分、审查和改写 xiaok skill，尤其适合目标模糊、scope 过大或不知道 skill 原则的时候\nwhen-to-use: Use when the user wants to create a new skill, split an overloaded skill, or improve an existing skill's routing, validation, or structure.\nallowed-tools:\n  - AskUserQuestion\n  - read\n  - grep\n  - glob\n  - write\n  - edit\n  - validate_skill\ntask-goals:\n  - create or refine one verifiable skill\ninput-kinds:\n  - vague skill idea\n  - existing SKILL.md\n  - overloaded workflow\noutput-kinds:\n  - validated skill draft\n  - split recommendation\nexamples:\n  - 帮我创建一个 release review skill\n  - 这个 skill 太大了，帮我拆一下\n  - 检查这个 SKILL.md 是否合格\n---\n# Skill Creator\n\nYou are the official meta skill for skill authoring in `xiaok`.\n\nYour job is not just to write files. Your job is to help the user end up with a\nskill that is narrow enough to trigger well, explicit enough to execute\nreliably, and concrete enough to validate.\n\nIf the user tries to pack multiple independent jobs into one skill, recommend a\nsplit and explain the routing tradeoff, but follow the user's scope choice.\n\n## Core Principles\n\n1. Single-goal principle\n   Prefer one primary job because it usually routes more clearly. If the user\n   wants multiple deliverables or unrelated triggers, recommend a split, but do\n   not reject the user's chosen shape.\n\n2. Progressive disclosure\n   Keep `SKILL.md` focused on routing, workflow, and success criteria. Move long\n   detail into `references\u002F`, `scripts\u002F`, or `assets\u002F` when the skill grows.\n\n3. Validation before trust\n   Run `validate_skill` on the saved draft. Fix errors before presenting it as\n   complete. Report warnings as optional improvements; warnings do not make a\n   runnable skill invalid.\n\n4. Verifiability\n   Recommend these fields and sections when they materially improve the skill:\n   - clear `when-to-use`\n   - one primary `task-goals` entry by default\n   - at least one `examples` entry\n   - explicit success criteria in the body\n\n   They are authoring guidance, not execution permissions. A non-strict skill\n   may remain valid without them. Only describe a check as mandatory when the\n   user explicitly chooses `strict: true` and the check is encoded in the\n   structured contract.\n\nRead `references\u002Fprinciples.md` if you need the longer rubric, and\n`references\u002Ftemplate.md` if you need a starter template.\n\n## Workflow\n\n1. Classify the request\n   - `create`: make a new skill from scratch\n   - `refine`: improve an existing skill\n   - `split`: break an overloaded skill into smaller ones\n   - `audit`: explain why a skill is weak and how to fix it\n\n2. Shape the scope before writing\n   Infer what you safely can and collect only the minimum information needed:\n   - primary job\n   - optional trigger \u002F when-to-use guidance\n   - optional success artifact or observable outcome\n   - relevant non-goals\n   - project or global scope\n\n3. Default save location\n   Save project-local skills to `.xiaok\u002Fskills\u002F\u003Cskill-name>\u002FSKILL.md` unless the\n   user explicitly asks for a global reusable skill.\n\n4. Default structure\n   Generate directory-style skills by default. Even minimal skills should use a\n   directory so references can be added later without migration.\n\n5. Quality gate\n   After saving, run `validate_skill` on the generated file. Fix errors\n   immediately. If warnings remain, explain them briefly as recommendations and\n   allow the draft to complete unless the user asks for a warning-free result.\n\n## Authoring Rules\n\n- Prefer one primary `task-goals` entry when structured routing will help.\n- Put optional routing signals in frontmatter, not buried in prose.\n- Keep `description` short and trigger-oriented.\n- Recommend `when-to-use` when the description alone is ambiguous.\n- Add `Non-Goals` when the skill could be confused with adjacent workflows.\n- If the body becomes long, create `references\u002F` and move detail there.\n\n## Recommended Output Shape\n\nWhen useful, produce a draft that includes:\n\n- frontmatter with `name`, `description`, `when-to-use`, `task-goals`, and `examples`\n- a `# Goal` section\n- a workflow section\n- a `## Success Criteria` section\n\nOnly `name` and `description` are required for a non-strict skill to load. Do\nnot add placeholder metadata merely to silence warnings; omit it when it does\nnot add useful routing or evaluation information.\n\nDo not leave the user with only advice if they clearly asked you to create or\nrefine the skill. Finish the draft, validate it, and report the result.\n","# Skill Creator\n\nYou are the official meta skill for skill authoring in `xiaok`.\n\nYour job is not just to write files. Your job is to help the user end up with a\nskill that is narrow enough to trigger well, explicit enough to execute\nreliably, and concrete enough to validate.\n\nIf the user tries to pack multiple independent jobs into one skill, recommend a\nsplit and explain the routing tradeoff, but follow the user's scope choice.\n\n## Core Principles\n\n1. Single-goal principle\n   Prefer one primary job because it usually routes more clearly. If the user\n   wants multiple deliverables or unrelated triggers, recommend a split, but do\n   not reject the user's chosen shape.\n\n2. Progressive disclosure\n   Keep `SKILL.md` focused on routing, workflow, and success criteria. Move long\n   detail into `references\u002F`, `scripts\u002F`, or `assets\u002F` when the skill grows.\n\n3. Validation before trust\n   Run `validate_skill` on the saved draft. Fix errors before presenting it as\n   complete. Report warnings as optional improvements; warnings do not make a\n   runnable skill invalid.\n\n4. Verifiability\n   Recommend these fields and sections when they materially improve the skill:\n   - clear `when-to-use`\n   - one primary `task-goals` entry by default\n   - at least one `examples` entry\n   - explicit success criteria in the body\n\n   They are authoring guidance, not execution permissions. A non-strict skill\n   may remain valid without them. Only describe a check as mandatory when the\n   user explicitly chooses `strict: true` and the check is encoded in the\n   structured contract.\n\nRead `references\u002Fprinciples.md` if you need the longer rubric, and\n`references\u002Ftemplate.md` if you need a starter template.\n\n## Workflow\n\n1. Classify the request\n   - `create`: make a new skill from scratch\n   - `refine`: improve an existing skill\n   - `split`: break an overloaded skill into smaller ones\n   - `audit`: explain why a skill is weak and how to fix it\n\n2. Shape the scope before writing\n   Infer what you safely can and collect only the minimum information needed:\n   - primary job\n   - optional trigger \u002F when-to-use guidance\n   - optional success artifact or observable outcome\n   - relevant non-goals\n   - project or global scope\n\n3. Default save location\n   Save project-local skills to `.xiaok\u002Fskills\u002F\u003Cskill-name>\u002FSKILL.md` unless the\n   user explicitly asks for a global reusable skill.\n\n4. Default structure\n   Generate directory-style skills by default. Even minimal skills should use a\n   directory so references can be added later without migration.\n\n5. Quality gate\n   After saving, run `validate_skill` on the generated file. Fix errors\n   immediately. If warnings remain, explain them briefly as recommendations and\n   allow the draft to complete unless the user asks for a warning-free result.\n\n## Authoring Rules\n\n- Prefer one primary `task-goals` entry when structured routing will help.\n- Put optional routing signals in frontmatter, not buried in prose.\n- Keep `description` short and trigger-oriented.\n- Recommend `when-to-use` when the description alone is ambiguous.\n- Add `Non-Goals` when the skill could be confused with adjacent workflows.\n- If the body becomes long, create `references\u002F` and move detail there.\n\n## Recommended Output Shape\n\nWhen useful, produce a draft that includes:\n\n- frontmatter with `name`, `description`, `when-to-use`, `task-goals`, and `examples`\n- a `# Goal` section\n- a workflow section\n- a `## Success Criteria` section\n\nOnly `name` and `description` are required for a non-strict skill to load. Do\nnot add placeholder metadata merely to silence warnings; omit it when it does\nnot add useful routing or evaluation information.\n\nDo not leave the user with only advice if they clearly asked you to create or\nrefine the skill. Finish the draft, validate it, and report the result.\n",{"name":5,"examples":51,"task-goals":55,"description":7,"input-kinds":57,"when-to-use":61,"output-kinds":62,"allowed-tools":65},[52,53,54],"帮我创建一个 release review skill","这个 skill 太大了，帮我拆一下","检查这个 SKILL.md 是否合格",[56],"create or refine one verifiable skill",[58,59,60],"vague skill idea","existing SKILL.md","overloaded workflow","Use when the user wants to create a new skill, split an overloaded skill, or improve an existing skill's routing, validation, or structure.",[63,64],"validated skill draft","split recommendation",[66,39,67,68,38,37,69],"AskUserQuestion","grep","glob","validate_skill","master","14ba9213ab5e180ee9ae87435665f84b7f8bc0d5","data\u002Fskills\u002Fskill-creator",5,"https:\u002F\u002Fgithub.com\u002Fkaisersong\u002Fxiaok-cli","https:\u002F\u002Fgithub.com\u002Fkaisersong","Bot？","2026-11-12 00:46:48",{"source":8,"skillName":5,"commands":79,"prompt":89,"zipAvailable":90},[80,83,86],{"tool":81,"command":82},"npx","npx skills add kaisersong\u002Fxiaok-cli --skill skill-creator",{"tool":84,"command":85},"bunx","bunx skills add kaisersong\u002Fxiaok-cli --skill skill-creator",{"tool":87,"command":88},"pnpm","pnpm dlx skills add kaisersong\u002Fxiaok-cli --skill skill-creator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkaisersong\u002Fxiaok-cli\u002Fblob\u002Fmaster\u002Fdata\u002Fskills\u002Fskill-creator\u002FSKILL.md",true,[92,98],{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fprinciples.md","REFERENCE","参考文档",1513,"https:\u002F\u002Fgithub.com\u002Fkaisersong\u002Fxiaok-cli\u002Fblob\u002Fmaster\u002Fdata\u002Fskills\u002Fskill-creator\u002Freferences\u002Fprinciples.md",{"path":99,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Ftemplate.md",508,"https:\u002F\u002Fgithub.com\u002Fkaisersong\u002Fxiaok-cli\u002Fblob\u002Fmaster\u002Fdata\u002Fskills\u002Fskill-creator\u002Freferences\u002Ftemplate.md",[103,129,152,162],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":46},"01M6K0S8027KVHKF06AQE1FMN2","release-checklist","Validate whether a single repository change is ready to ship","https:\u002F\u002Fgithub.com\u002Fkaisersong\u002Fxiaok-cli\u002Fblob\u002Fmaster\u002Fevals\u002Fskill-quality-fixtures\u002Fvalid-release-checklist\u002FSKILL.md",[],[41,110,111,112,113,28,114,115,116,117,118,119,120,36,121,122,123,124,125,126,127,128],"release checklist","checklist","validate","user","single","release readiness","for","readiness","summary","ready","diff","verify release","check","branch","ship","verify","repository","code","change",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":46},"01M6K0S3B0GH0PM3879G0XB13G","overloaded-multi-job","Handle launch plans, write reports, and review release risk","https:\u002F\u002Fgithub.com\u002Fkaisersong\u002Fxiaok-cli\u002Fblob\u002Fmaster\u002Fevals\u002Fskill-quality-fixtures\u002Foverloaded-multi-job\u002FSKILL.md",[],[136,137,28,138,116,139,140,141,142,143,118,144,145,146,36,38,147,41,148,149,150,45,151],"overloaded multi job","multi","request","follow-up","release review","plans","feature","generation","reports","up","review release","risk","report","planning","launch","plan",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":158,"publishedAt":46},"01M6K0S1RH1Y6X8ET6ZN96YGHR","missing-verifiability","misc helper","https:\u002F\u002Fgithub.com\u002Fkaisersong\u002Fxiaok-cli\u002Fblob\u002Fmaster\u002Fevals\u002Fskill-quality-fixtures\u002Fmissing-verifiability\u002FSKILL.md",[],[159,160,161],"missing verifiability","missing","helper",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":166,"licenseFileUrl":167,"sourceHtmlUrl":168,"categories":169,"keywords":175,"publishedAt":46},"01M6K0RQX4MGJSR68KBW6XHNPZ","typesafe-ai","Build AI-powered software with TypeSafe: small units of AI intelligence you can use like programming primitives. Its System One models, including Jev, turn natural language and application state into typed judgments and probabilities that code can combine. Use when a feature needs programmable common sense, when brainstorming what AI could make possible in an app, or when an LLM prompt-and-parse step could become a structured decision. Applications include routing, ranking, extraction, verification, and interactive experiences; these are starting points, not the limits. Read live docs and cookbooks to find useful patterns and discover new combinations.","MIT","https:\u002F\u002Fgithub.com\u002Fkaisersong\u002Fxiaok-cli\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Ftypesafe-ai\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fkaisersong\u002Fxiaok-cli\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Ftypesafe-ai\u002FSKILL.md",[170],{"categoryNo":171,"categoryName":172,"taxonomyType":173,"taxonomyTypeDesc":174},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[176,177,142,178,179,180,181,182,183,36,184,185,39,186,187,188,189,190,191,192,28,127,27,193,194,195,196,197,198,199,200,201],"typesafe ai","interactive","live","combinations","discover","intelligence","natural language","patterns","primitives","app","prompt","programming","common","decision","system","applications","verification","useful","parse","limits","can","combine","you","with","ranking","software"]