[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6X0FPR8CSYZ56FZGZ5GACM8":3,"skill-same:01M6X0FPR8CSYZ56FZGZ5GACM8":62},{"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":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":44,"ownerHtmlUrl":45,"ownerBlogUrl":46,"ownerDescription":47,"updatedAt":48,"install":49,"resources":61},"01M6X0FPR8CSYZ56FZGZ5GACM8","Create a user skill",null,"Create a new user skill at setting\u002Fskills\u002F\u003Cid>\u002FSKILL.md.","microsoft\u002FHuabu","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M6X0DDX0PRP3DDSC7SC0HNAS",172,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FHuabu\u002Fblob\u002Fmain\u002Fapps\u002Fserver\u002Fsrc\u002Fprompt\u002Fskills\u002Fcreate-skill\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,5,27,28,29,30,31],"create","user","user skill","id","operate","true","at","new user","2026-11-10 10:12:30",false,"---\nname: Create a user skill\ndescription: 'Create a new user skill at setting\u002Fskills\u002F\u003Cid>\u002FSKILL.md.'\nappliesTo:\n  - operate\nuserInvokable: true\n---\n\n# Create a user skill\n\nYou were called because the user typed `\u002Fcreate-skill \u003Cinstructions>` in the chat input. Your job for this turn is **create a brand-new user skill** that captures the reusable how-to \u002F recipe \u002F pattern they described — no analysis or judgement required, just author it cleanly and write it.\n\n## Inputs you have\n\n- **The free-text after `\u002Fcreate-skill`** in the most recent user message — this is the brief. It may be terse (\"a skill for warm-healing story outlines\") or detailed (\"…and use a 5-frame layout with these colour rules…\"). Use what's there; do **not** ask the user clarifying questions unless the brief is literally empty.\n- **The skill catalogue** in your system prompt — scan it briefly to avoid duplicating an existing skill id. If a near-match exists, prefer `\u002Fupdate-skill` semantics over `\u002Fcreate-skill`, but **only** mention this in your final reply; do not silently switch modes.\n\n## Pick the id\n\n- Kebab-case, derived from the brief's noun phrase. Keep it short (≤ 5 words).\n  - \"warm-healing outline\" → `warm-healing-outline`\n  - \"research paper summary\" → `research-paper-summary`\n- Must not collide with an existing skill id (check the catalogue).\n- Must match `[a-z0-9-]+` — no slashes, dots, underscores, or uppercase.\n\n## Compose the file\n\nSubmit the **entire** file via `fs_write`, including the YAML frontmatter fence. The skill id comes from the `\u003Cid>` directory segment in the path — it is **not** a frontmatter key. Frontmatter fields:\n\n| field         | value                                                                                 |\n| ------------- | ------------------------------------------------------------------------------------- |\n| `name`        | human-readable label (Title Case is fine)                                             |\n| `description` | one-sentence catalogue blurb — what the skill does, not when (the body covers when)   |\n| `appliesTo`   | array; default to `[\"ask\", \"operate\"]` unless the brief obviously narrows the surface |\n\n`triggers` and `version` are optional — omit unless the brief calls for them.\n\nBody structure (use these section headings verbatim — keeps user skills consistent and easy to scan):\n\n```\n# \u003CDisplay name>\n\n## When to use\n…short list of scenarios, written from the user's perspective.\n\n## How to apply\n…step-by-step \u002F checklist \u002F decision rules. Be concrete.\n\n## Examples\n…minimal, copy-pasteable. Optional but very valuable.\n```\n\nBody length: keep it tight. Every byte ends up in someone's prompt later; aim for ≤ 60 lines.\n\n## Write it\n\nUse `fs_write` exactly once:\n\n```json\n{\n  \"path\": \"skills\u002F\u003Cid>\u002FSKILL.md\",\n  \"mode\": \"overwrite\",\n  \"rationale\": \"\u003C≥ 20 chars explaining why no existing skill fits>\",\n  \"body\": \"---\\nname: \\\"…\\\"\\ndescription: \\\"…\\\"\\nappliesTo: [\\\"ask\\\", \\\"operate\\\"]\\n---\\n\\n# …\\n\\n## When to use\\n\\n…\\n\"\n}\n```\n\n`rationale` is **required** by `fs_write` because this is a skill-create on a path that doesn't yet exist. Make it substantive — \"the user explicitly requested this skill via \u002Fcreate-skill: \u003Cbrief>\" is the minimum bar; better if you can name a near-miss skill from the catalogue you considered and explain why it didn't fit.\n\n## After writing\n\n- Briefly confirm to the user: skill id, one-line summary of what it does, and a reminder that they can now invoke it via `\u002F\u003Cid>`.\n- Do **not** make Space changes in the same turn; this slash skill is write-the-skill-and-stop.\n","# Create a user skill\n\nYou were called because the user typed `\u002Fcreate-skill \u003Cinstructions>` in the chat input. Your job for this turn is **create a brand-new user skill** that captures the reusable how-to \u002F recipe \u002F pattern they described — no analysis or judgement required, just author it cleanly and write it.\n\n## Inputs you have\n\n- **The free-text after `\u002Fcreate-skill`** in the most recent user message — this is the brief. It may be terse (\"a skill for warm-healing story outlines\") or detailed (\"…and use a 5-frame layout with these colour rules…\"). Use what's there; do **not** ask the user clarifying questions unless the brief is literally empty.\n- **The skill catalogue** in your system prompt — scan it briefly to avoid duplicating an existing skill id. If a near-match exists, prefer `\u002Fupdate-skill` semantics over `\u002Fcreate-skill`, but **only** mention this in your final reply; do not silently switch modes.\n\n## Pick the id\n\n- Kebab-case, derived from the brief's noun phrase. Keep it short (≤ 5 words).\n  - \"warm-healing outline\" → `warm-healing-outline`\n  - \"research paper summary\" → `research-paper-summary`\n- Must not collide with an existing skill id (check the catalogue).\n- Must match `[a-z0-9-]+` — no slashes, dots, underscores, or uppercase.\n\n## Compose the file\n\nSubmit the **entire** file via `fs_write`, including the YAML frontmatter fence. The skill id comes from the `\u003Cid>` directory segment in the path — it is **not** a frontmatter key. Frontmatter fields:\n\n| field         | value                                                                                 |\n| ------------- | ------------------------------------------------------------------------------------- |\n| `name`        | human-readable label (Title Case is fine)                                             |\n| `description` | one-sentence catalogue blurb — what the skill does, not when (the body covers when)   |\n| `appliesTo`   | array; default to `[\"ask\", \"operate\"]` unless the brief obviously narrows the surface |\n\n`triggers` and `version` are optional — omit unless the brief calls for them.\n\nBody structure (use these section headings verbatim — keeps user skills consistent and easy to scan):\n\n```\n# \u003CDisplay name>\n\n## When to use\n…short list of scenarios, written from the user's perspective.\n\n## How to apply\n…step-by-step \u002F checklist \u002F decision rules. Be concrete.\n\n## Examples\n…minimal, copy-pasteable. Optional but very valuable.\n```\n\nBody length: keep it tight. Every byte ends up in someone's prompt later; aim for ≤ 60 lines.\n\n## Write it\n\nUse `fs_write` exactly once:\n\n```json\n{\n  \"path\": \"skills\u002F\u003Cid>\u002FSKILL.md\",\n  \"mode\": \"overwrite\",\n  \"rationale\": \"\u003C≥ 20 chars explaining why no existing skill fits>\",\n  \"body\": \"---\\nname: \\\"…\\\"\\ndescription: \\\"…\\\"\\nappliesTo: [\\\"ask\\\", \\\"operate\\\"]\\n---\\n\\n# …\\n\\n## When to use\\n\\n…\\n\"\n}\n```\n\n`rationale` is **required** by `fs_write` because this is a skill-create on a path that doesn't yet exist. Make it substantive — \"the user explicitly requested this skill via \u002Fcreate-skill: \u003Cbrief>\" is the minimum bar; better if you can name a near-miss skill from the catalogue you considered and explain why it didn't fit.\n\n## After writing\n\n- Briefly confirm to the user: skill id, one-line summary of what it does, and a reminder that they can now invoke it via `\u002F\u003Cid>`.\n- Do **not** make Space changes in the same turn; this slash skill is write-the-skill-and-stop.\n",{"name":5,"appliesTo":37,"description":7,"userInvokable":38},[28],true,"main","14822a92c9739f08579ddf2426c56e84909b4ab1","apps\u002Fserver\u002Fsrc\u002Fprompt\u002Fskills\u002Fcreate-skill",23,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FHuabu","https:\u002F\u002Fmicrosoft.github.io\u002FHuabu\u002F","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-11 23:54:56",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":38},[51,54,57],{"tool":52,"command":53},"npx","npx skills add microsoft\u002FHuabu --skill \"Create a user skill\"",{"tool":55,"command":56},"bunx","bunx skills add microsoft\u002FHuabu --skill \"Create a user skill\"",{"tool":58,"command":59},"pnpm","pnpm dlx skills add microsoft\u002FHuabu --skill \"Create a user skill\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FHuabu\u002Fblob\u002Fmain\u002Fapps\u002Fserver\u002Fsrc\u002Fprompt\u002Fskills\u002Fcreate-skill\u002FSKILL.md",[],[63,72,83,96,115,142],{"skillNo":64,"name":65,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":32},"01M6X0GC24XV5DQ6NB454JTJQG","web-search","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FHuabu\u002Fblob\u002Fmain\u002Fapps\u002Fserver\u002Fsrc\u002Fservices\u002Fweb-search\u002FSKILL.md",[],[69,70,71],"web search","search","web",{"skillNo":73,"name":74,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":80,"publishedAt":32},"01M6X0GA59Q0BTYZ2SZYFDR0RC","image-gen","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FHuabu\u002Fblob\u002Fmain\u002Fapps\u002Fserver\u002Fsrc\u002Fservices\u002Fimage-gen\u002FSKILL.md",[77],{"categoryNo":78,"categoryName":79,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[81,82],"image","image gen",{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":90,"publishedAt":32},"01M6X0G47PN7FY6JK9N6KJSKQX","Update a user skill","Find an existing user skill and apply the requested change to its SKILL.md.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FHuabu\u002Fblob\u002Fmain\u002Fapps\u002Fserver\u002Fsrc\u002Fprompt\u002Fskills\u002Fupdate-skill\u002FSKILL.md",[89],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[91,25,26,85,29,92,93,94,28,95],"update","change","find","apply","Existing",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":32},"01M6X0FX0FRE3QJK1JC1MB9JHM","space","Space mental model (the infinite work surface), tool boundaries, and command reference. The single entry point for any agent operating on a Huabu Space.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FHuabu\u002Fblob\u002Fmain\u002Fapps\u002Fserver\u002Fsrc\u002Fprompt\u002Fskills\u002Fspace\u002FSKILL.md",[],[98,103,104,105,106,107,108,109,110,28,111,112,113,114],"mental model","tool","model","work","ask","command","reference","operating","for","entry","single","point",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":124,"publishedAt":32},"01M6X0FGBPBEV3ZRSKHYPJM3CQ","paper-scout","Find related academic work and compare it with a research idea using arXiv, OpenAlex, Crossref, and core HCI venues. Use when the user asks whether an idea overlaps with prior work or requests a quick literature scout. Do not use for reviewing one supplied paper or claiming an exhaustive systematic review.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FHuabu\u002Fblob\u002Fmain\u002Fagent-teams\u002Fpaper-scout\u002FSKILL.md",[121],{"categoryNo":122,"categoryName":123,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",[125,126,127,128,129,130,131,132,106,93,133,134,135,136,137,138,139,140,141,111],"paper scout","paper","scout","when","requests","research","systematic review","core","use","arxiv","do","hci","systematic","literature","it","with","quick",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":149,"publishedAt":32},"01M6X0FCXNZMT3FGJCT5STRM3K","paper-reviewer","Review academic papers, discuss their claims, and draft bilingual review responses grounded in the paper. Use when the user asks to summarize, critique, or prepare a review of a supplied paper. Do not use for broad literature discovery or novelty searches without a paper to review.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FHuabu\u002Fblob\u002Fmain\u002Fagent-teams\u002Fpaper-reviewer\u002FSKILL.md",[148],{"categoryNo":122,"categoryName":123,"taxonomyType":21,"taxonomyTypeDesc":22},[150,126,151,152,153,154,155,25,133,135,156,157,158,138,159,160,111,128,161],"paper reviewer","reviewer","summarize","prepare","discovery","critique","draft","Academic","bilingual","papers","claims","review"]