[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DM960C0SBYFSXQ1W6B9GNF":3,"skill-same:01M6DM960C0SBYFSXQ1W6B9GNF":105},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":61,"ownerHtmlUrl":62,"ownerBlogUrl":63,"ownerDescription":64,"updatedAt":65,"install":66,"resources":78},"01M6DM960C0SBYFSXQ1W6B9GNF","ub-customizations",null,"Create, update, review, or refactor VS Code Copilot skills, hooks, and MCP configs. Use when the user wants to build or maintain reusable skills, lifecycle hooks, MCP integrations, or the supporting references and validation flow around those artifacts, or needs help deciding between a skill, hook, or MCP config.","robert-hoffmann\u002Funcle-bob","robert-hoffmann","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F5472296?v=4","01M6DM8QYHW65WRHBE8H2WC9JK","Robert Hoffmann","01M6DM8R3MX0HR6MQFDZVH98NQ",28,"MIT","https:\u002F\u002Fgithub.com\u002Frobert-hoffmann\u002Funcle-bob\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fub-customizations\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"ub customizations","lifecycle","copilot skills","false","maintain","references","reusable","hooks","use","integrations","MCP","refactor","flow","artifacts","code","update","create","copilot","config","review","2026-11-10 10:12:30",false,"---\nname: ub-customizations\ndescription: >-\n  Create, update, review, or refactor VS Code Copilot skills, hooks, and MCP\n  configs. Use when the user wants to build or maintain reusable skills,\n  lifecycle hooks, MCP integrations, or the supporting references and\n  validation flow around those artifacts, or needs help deciding between a\n  skill, hook, or MCP config.\nargument-hint: \"[what to build] [constraints]\"\nuser-invocable: true\ndisable-model-invocation: false\n---\n\n# UB Customizations — VS Code Copilot Customization Builder\n\n## Mission\n\nRoute the user to the correct VS Code Copilot artifact within this skill's\nscope, generate safe and valid skills, hooks, or MCP configs, validate output,\nand recommend companion artifacts only when they materially improve the\nworkflow.\n\nImplement against the target host and tool reality, but bias the generated\ncustomization toward current official guidance and forward-compatible artifact\nchoices instead of preserving deprecated or legacy customization surfaces by\ndefault.\n\n## When Not To Use\n\n- Do not use this skill for general repository workflow planning; defer that to\n  `ub-workflow`.\n- Do not use this skill for governance-only policy or evidence questions;\n  defer those to `ub-governance`.\n- Do not use this skill as the owner of reusable cross-skill authoring\n  conventions; defer those to `ub-authoring`.\n- Do not use this skill when the user only needs normal code implementation in\n  an existing stack rather than skill, hook, or MCP artifacts.\n\n## Coordination\n\n- Use `ub-customizations` as the default builder workflow for skills, hooks,\n  and MCP configs.\n- Use `ub-authoring` when the task is about reusable cross-skill conventions\n  such as routing-quality descriptions, non-use boundaries, naming, or shared\n  authoring structure.\n- Use both only when a customization task also changes the shared installable\n  authoring contract.\n\n## Artifact Selection Matrix\n\nClassify the request BEFORE generating anything.\n\n| User Need | Primary Artifact | Common Companions | Why |\n| --- | --- | --- | --- |\n| Reusable multi-step capability with scripts\u002Fresources | Skill | Optional MCP config | On-demand domain workflow with bundled references, scripts, or assets |\n| Deterministic lifecycle automation | Hook | Optional helper script | Guaranteed execution at agent lifecycle points; not soft guidance |\n| External systems, APIs, databases, browsers | MCP config | Optional skill | Real new capabilities via tools\u002Fresources and authenticated external access |\n| Everything else | Out of scope here | See other customization primitives directly | Instructions, prompt files, custom agents, and plugin packaging are no longer first-class scope for this skill |\n\n## Rules of Thumb\n\n1. If it is a **reusable multi-step capability** with references, scripts, or\n  assets → skill.\n2. If it must **run deterministically** before or after lifecycle events →\n  hook.\n3. If it needs **real external capabilities, tools, or data** outside the\n  workspace → MCP.\n4. If a skill depends on external systems, pair the skill with MCP instead of\n  overloading the skill alone.\n5. Always choose the smallest sufficient artifact inside this skill's scope.\n6. Do not use MCP where a local script is enough.\n7. Do not use a hook for soft guidance when a skill is the real fit.\n\n**Always choose the smallest sufficient artifact inside this skill's scope.**\n\n## Deep Classification Interview\n\nBefore generating anything, interview the user with targeted questions. Use\n`askQuestions` when available, and follow the shared `ub-authoring`\nchoice-question contract for any multiple-choice prompts. Skip questions whose\nanswers are already clear from context.\n\n### Core Questions (always ask)\n\n1. **What do you want to build or change?** Describe the behavior, workflow,\n  automation, or integration you need.\n2. **Is this a reusable on-demand workflow, a deterministic lifecycle action,\n  or an external integration?**\n3. **Does it need to run automatically at specific lifecycle points?** If yes,\n  which events matter?\n4. **Does it need access to external systems, APIs, databases, browsers, or\n  remote data sources?**\n5. **Does it need bundled references, scripts, or assets to guide repeated\n  use?**\n\n### Conditional Deep-Dive Questions (ask when relevant)\n\n1. **Which lifecycle events matter?** Use the VS Code hook events when a hook\n  is in scope.\n2. **Which external systems, credentials, transports, or trust boundaries\n  matter?** Use this when MCP is in scope.\n3. **Would a companion artifact materially improve the workflow?** Recommend\n  Skill + MCP when the skill depends on external systems.\n\nAfter classification, state the recommendation, assumptions, and rationale before generating.\n\n## Platform & Research Policy\n\n- Treat the latest stable VS Code and GitHub Copilot customization guidance as\n  the preferred baseline for artifact choice, file structure, and capability\n  recommendations.\n- Detect workspace and host truth before generating: repository structure,\n  existing customization artifacts, target host, available tools, and\n  portability requirements.\n- Treat repo and host truth as the gold implementation standard when deciding\n  what can actually ship safely in the target environment.\n- Use web search to verify current official customization guidance against\n  primary VS Code and GitHub documentation before making non-trivial or\n  platform-sensitive recommendations.\n- If official guidance and repo or host truth diverge materially on a\n  non-trivial recommendation, surface `OFFICIAL_CONFLICT`, implement the\n  host-safe path, and explain the migration or portability consequence.\n- If official sources disagree with each other on a non-trivial\n  recommendation, also surface `OFFICIAL_CONFLICT` instead of silently\n  collapsing the disagreement.\n- If a non-trivial claim cannot be confirmed in official sources after\n  targeted research, mark it `UNVERIFIED` or avoid presenting it as settled\n  guidance.\n- Keep conflict and uncertainty disclosure scoped to non-trivial,\n  platform-sensitive, or contested guidance rather than simple artifact\n  generation.\n\n## Bundle Recommendations\n\nMany workflows need multiple artifacts working together. Actively recommend these bundles during classification:\n\n| Bundle | Components | When to Recommend |\n| --- | --- | --- |\n| **A** | Skill + MCP | The workflow is reusable but depends on external systems, authenticated tools, or remote data |\n| **B** | Hook + helper script | Deterministic lifecycle automation needs logic that should live outside inline shell |\n\nFor detailed bundle guidance and example scenarios, read [references\u002Fbundles.md](references\u002Fbundles.md).\n\n## Generation Workflow\n\nFollow these steps in order:\n\n### 1. Classify\n\nParse the request. Identify the artifact type(s) needed using the selection matrix above.\n\n### 2. Interview\n\nAsk classification questions. Confirm the chosen artifact type(s) with the user.\n\n### 3. Plan\n\nState assumptions, file tree, and rationale. For the artifact type being generated, load the appropriate reference:\n\n| Artifact Type | Reference to Load |\n| --- | --- |\n| Skills | [references\u002Fskills.md](references\u002Fskills.md) |\n| Hooks | [references\u002Fhooks.md](references\u002Fhooks.md) |\n| MCP configs | [references\u002Fmcp.md](references\u002Fmcp.md) |\n\nFor customization-artifact writing guidance, read\n[references\u002Fprompt-engineering.md](references\u002Fprompt-engineering.md).\nFor reusable cross-skill authoring conventions, read\n[`..\u002Fub-authoring\u002Freferences\u002Fauthoring-conventions.md`](..\u002Fub-authoring\u002Freferences\u002Fauthoring-conventions.md).\n\nBefore generating non-trivial or platform-sensitive customizations, compare\nofficial guidance, repo truth, and target host reality and surface\n`OFFICIAL_CONFLICT` or `UNVERIFIED` when relevant.\n\n### 4. Generate\n\nCreate the files following the loaded reference. Apply these defaults:\n\n- **Shared authoring contract**: rely on `ub-authoring` for reusable naming,\n  routing, and shared structure conventions.\n- **Least privilege**: expose only necessary tools; minimize dangerous defaults.\n- **No hardcoded secrets**: use MCP `inputs`, environment variables, or `.env` references.\n- **Concise descriptions**: optimize for triggering and discovery, not marketing.\n\n### 5. Validate\n\nRun the validation checklist from [references\u002Fvalidation.md](references\u002Fvalidation.md) for each generated artifact. Produce:\n\n- Validation checklist (pass\u002Ffail per item)\n- Smoke-test prompts (how to test the artifact)\n- Portability notes (VS Code-only vs Copilot-compatible vs broadly portable)\n\n### 6. Iterate\n\nPresent the output for review. Refine based on user feedback. Re-validate after changes.\n\n## Output Contract\n\nTreat this section as the stable output expectation for non-trivial\ncustomization work in this catalog.\n\nStructure every generation response as:\n\n1. **Recommendation** — what to generate and why\n2. **Source truth note** — detected host, repo artifact reality, and any\n   material gap versus latest official guidance\n3. **Assumptions** — defaults chosen, unresolved ambiguities\n4. **File tree** — directories and files to create or update\n5. **Generated content** — file-by-file output\n6. **Validation checklist** — human review items + technical checks\n7. **Smoke-test prompts** — how to verify the artifact works\n8. **Portability notes** — which pieces are VS Code-only, Copilot-compatible, or broadly portable\n9. **Risks \u002F follow-up** — preview features, secrets, trust, unsupported host features\n10. **Conflict note when relevant** — `OFFICIAL_CONFLICT` or `UNVERIFIED`\n    with a concise explanation and the implementation consequence\n\n## Completion Checklist\n\n- Artifact choice is the smallest sufficient primitive for the request.\n- Any recommended multi-artifact bundle is explained and justified.\n- Generated files are valid for the chosen customization type.\n- Tool access is least-privilege rather than broad by default.\n- Validation and smoke-test guidance is explicit.\n- VS Code-only versus Agent-Skills-portable behavior is called out.\n- Secret handling, trust, or preview-feature risks are surfaced when relevant.\n- Any material official-source conflict or unverified non-trivial guidance is\n  disclosed explicitly when relevant.\n\n## Safety Defaults\n\n- Default to **read-only planning** where possible.\n- Default to **minimal scopes** for generated hooks and MCP servers.\n- **Never hardcode** API keys, tokens, or secrets.\n- Gate destructive actions behind **approval hooks** or confirmation.\n- Include **review warnings** for hooks and MCP configs.\n- Warn about **trust and security** when suggesting third-party skills or MCP servers.\n\n## Anti-Patterns to Avoid\n\n- Do NOT default to a skill when a hook or MCP config is the real fit.\n- Do NOT treat this skill as the owner of cross-catalog authoring conventions\n  now that `ub-authoring` exists.\n- Do NOT generate giant monolithic files — use progressive disclosure and references.\n- Do NOT use hooks for soft guidance — hooks are for deterministic lifecycle actions.\n- Do NOT use MCP for trivial local tasks — MCP is for real external capabilities.\n- Do NOT grant broad tool or secret access by default — use least privilege and explicit inputs.\n\n## Freshness Review\n\n- Volatility: high\n- Review recommendation: review on touch and during periodic maintenance, targeting a quarterly rhythm when practical.\n- Trigger signals: VS Code Copilot skill, hook, or MCP surface changes; Agent Skills spec changes; MCP schema changes; lifecycle-event changes; or portability guidance changes tied to the official Agent Skills spec.\n- Enforcement: advisory only; freshness warnings should not block unrelated customization work by default.\n- Stable core: smallest-sufficient artifact choice, least privilege, explicit\n  validation, and the builder-versus-authoring ownership split remain the\n  durable guidance.\n","# UB Customizations — VS Code Copilot Customization Builder\n\n## Mission\n\nRoute the user to the correct VS Code Copilot artifact within this skill's\nscope, generate safe and valid skills, hooks, or MCP configs, validate output,\nand recommend companion artifacts only when they materially improve the\nworkflow.\n\nImplement against the target host and tool reality, but bias the generated\ncustomization toward current official guidance and forward-compatible artifact\nchoices instead of preserving deprecated or legacy customization surfaces by\ndefault.\n\n## When Not To Use\n\n- Do not use this skill for general repository workflow planning; defer that to\n  `ub-workflow`.\n- Do not use this skill for governance-only policy or evidence questions;\n  defer those to `ub-governance`.\n- Do not use this skill as the owner of reusable cross-skill authoring\n  conventions; defer those to `ub-authoring`.\n- Do not use this skill when the user only needs normal code implementation in\n  an existing stack rather than skill, hook, or MCP artifacts.\n\n## Coordination\n\n- Use `ub-customizations` as the default builder workflow for skills, hooks,\n  and MCP configs.\n- Use `ub-authoring` when the task is about reusable cross-skill conventions\n  such as routing-quality descriptions, non-use boundaries, naming, or shared\n  authoring structure.\n- Use both only when a customization task also changes the shared installable\n  authoring contract.\n\n## Artifact Selection Matrix\n\nClassify the request BEFORE generating anything.\n\n| User Need | Primary Artifact | Common Companions | Why |\n| --- | --- | --- | --- |\n| Reusable multi-step capability with scripts\u002Fresources | Skill | Optional MCP config | On-demand domain workflow with bundled references, scripts, or assets |\n| Deterministic lifecycle automation | Hook | Optional helper script | Guaranteed execution at agent lifecycle points; not soft guidance |\n| External systems, APIs, databases, browsers | MCP config | Optional skill | Real new capabilities via tools\u002Fresources and authenticated external access |\n| Everything else | Out of scope here | See other customization primitives directly | Instructions, prompt files, custom agents, and plugin packaging are no longer first-class scope for this skill |\n\n## Rules of Thumb\n\n1. If it is a **reusable multi-step capability** with references, scripts, or\n  assets → skill.\n2. If it must **run deterministically** before or after lifecycle events →\n  hook.\n3. If it needs **real external capabilities, tools, or data** outside the\n  workspace → MCP.\n4. If a skill depends on external systems, pair the skill with MCP instead of\n  overloading the skill alone.\n5. Always choose the smallest sufficient artifact inside this skill's scope.\n6. Do not use MCP where a local script is enough.\n7. Do not use a hook for soft guidance when a skill is the real fit.\n\n**Always choose the smallest sufficient artifact inside this skill's scope.**\n\n## Deep Classification Interview\n\nBefore generating anything, interview the user with targeted questions. Use\n`askQuestions` when available, and follow the shared `ub-authoring`\nchoice-question contract for any multiple-choice prompts. Skip questions whose\nanswers are already clear from context.\n\n### Core Questions (always ask)\n\n1. **What do you want to build or change?** Describe the behavior, workflow,\n  automation, or integration you need.\n2. **Is this a reusable on-demand workflow, a deterministic lifecycle action,\n  or an external integration?**\n3. **Does it need to run automatically at specific lifecycle points?** If yes,\n  which events matter?\n4. **Does it need access to external systems, APIs, databases, browsers, or\n  remote data sources?**\n5. **Does it need bundled references, scripts, or assets to guide repeated\n  use?**\n\n### Conditional Deep-Dive Questions (ask when relevant)\n\n1. **Which lifecycle events matter?** Use the VS Code hook events when a hook\n  is in scope.\n2. **Which external systems, credentials, transports, or trust boundaries\n  matter?** Use this when MCP is in scope.\n3. **Would a companion artifact materially improve the workflow?** Recommend\n  Skill + MCP when the skill depends on external systems.\n\nAfter classification, state the recommendation, assumptions, and rationale before generating.\n\n## Platform & Research Policy\n\n- Treat the latest stable VS Code and GitHub Copilot customization guidance as\n  the preferred baseline for artifact choice, file structure, and capability\n  recommendations.\n- Detect workspace and host truth before generating: repository structure,\n  existing customization artifacts, target host, available tools, and\n  portability requirements.\n- Treat repo and host truth as the gold implementation standard when deciding\n  what can actually ship safely in the target environment.\n- Use web search to verify current official customization guidance against\n  primary VS Code and GitHub documentation before making non-trivial or\n  platform-sensitive recommendations.\n- If official guidance and repo or host truth diverge materially on a\n  non-trivial recommendation, surface `OFFICIAL_CONFLICT`, implement the\n  host-safe path, and explain the migration or portability consequence.\n- If official sources disagree with each other on a non-trivial\n  recommendation, also surface `OFFICIAL_CONFLICT` instead of silently\n  collapsing the disagreement.\n- If a non-trivial claim cannot be confirmed in official sources after\n  targeted research, mark it `UNVERIFIED` or avoid presenting it as settled\n  guidance.\n- Keep conflict and uncertainty disclosure scoped to non-trivial,\n  platform-sensitive, or contested guidance rather than simple artifact\n  generation.\n\n## Bundle Recommendations\n\nMany workflows need multiple artifacts working together. Actively recommend these bundles during classification:\n\n| Bundle | Components | When to Recommend |\n| --- | --- | --- |\n| **A** | Skill + MCP | The workflow is reusable but depends on external systems, authenticated tools, or remote data |\n| **B** | Hook + helper script | Deterministic lifecycle automation needs logic that should live outside inline shell |\n\nFor detailed bundle guidance and example scenarios, read [references\u002Fbundles.md](references\u002Fbundles.md).\n\n## Generation Workflow\n\nFollow these steps in order:\n\n### 1. Classify\n\nParse the request. Identify the artifact type(s) needed using the selection matrix above.\n\n### 2. Interview\n\nAsk classification questions. Confirm the chosen artifact type(s) with the user.\n\n### 3. Plan\n\nState assumptions, file tree, and rationale. For the artifact type being generated, load the appropriate reference:\n\n| Artifact Type | Reference to Load |\n| --- | --- |\n| Skills | [references\u002Fskills.md](references\u002Fskills.md) |\n| Hooks | [references\u002Fhooks.md](references\u002Fhooks.md) |\n| MCP configs | [references\u002Fmcp.md](references\u002Fmcp.md) |\n\nFor customization-artifact writing guidance, read\n[references\u002Fprompt-engineering.md](references\u002Fprompt-engineering.md).\nFor reusable cross-skill authoring conventions, read\n[`..\u002Fub-authoring\u002Freferences\u002Fauthoring-conventions.md`](..\u002Fub-authoring\u002Freferences\u002Fauthoring-conventions.md).\n\nBefore generating non-trivial or platform-sensitive customizations, compare\nofficial guidance, repo truth, and target host reality and surface\n`OFFICIAL_CONFLICT` or `UNVERIFIED` when relevant.\n\n### 4. Generate\n\nCreate the files following the loaded reference. Apply these defaults:\n\n- **Shared authoring contract**: rely on `ub-authoring` for reusable naming,\n  routing, and shared structure conventions.\n- **Least privilege**: expose only necessary tools; minimize dangerous defaults.\n- **No hardcoded secrets**: use MCP `inputs`, environment variables, or `.env` references.\n- **Concise descriptions**: optimize for triggering and discovery, not marketing.\n\n### 5. Validate\n\nRun the validation checklist from [references\u002Fvalidation.md](references\u002Fvalidation.md) for each generated artifact. Produce:\n\n- Validation checklist (pass\u002Ffail per item)\n- Smoke-test prompts (how to test the artifact)\n- Portability notes (VS Code-only vs Copilot-compatible vs broadly portable)\n\n### 6. Iterate\n\nPresent the output for review. Refine based on user feedback. Re-validate after changes.\n\n## Output Contract\n\nTreat this section as the stable output expectation for non-trivial\ncustomization work in this catalog.\n\nStructure every generation response as:\n\n1. **Recommendation** — what to generate and why\n2. **Source truth note** — detected host, repo artifact reality, and any\n   material gap versus latest official guidance\n3. **Assumptions** — defaults chosen, unresolved ambiguities\n4. **File tree** — directories and files to create or update\n5. **Generated content** — file-by-file output\n6. **Validation checklist** — human review items + technical checks\n7. **Smoke-test prompts** — how to verify the artifact works\n8. **Portability notes** — which pieces are VS Code-only, Copilot-compatible, or broadly portable\n9. **Risks \u002F follow-up** — preview features, secrets, trust, unsupported host features\n10. **Conflict note when relevant** — `OFFICIAL_CONFLICT` or `UNVERIFIED`\n    with a concise explanation and the implementation consequence\n\n## Completion Checklist\n\n- Artifact choice is the smallest sufficient primitive for the request.\n- Any recommended multi-artifact bundle is explained and justified.\n- Generated files are valid for the chosen customization type.\n- Tool access is least-privilege rather than broad by default.\n- Validation and smoke-test guidance is explicit.\n- VS Code-only versus Agent-Skills-portable behavior is called out.\n- Secret handling, trust, or preview-feature risks are surfaced when relevant.\n- Any material official-source conflict or unverified non-trivial guidance is\n  disclosed explicitly when relevant.\n\n## Safety Defaults\n\n- Default to **read-only planning** where possible.\n- Default to **minimal scopes** for generated hooks and MCP servers.\n- **Never hardcode** API keys, tokens, or secrets.\n- Gate destructive actions behind **approval hooks** or confirmation.\n- Include **review warnings** for hooks and MCP configs.\n- Warn about **trust and security** when suggesting third-party skills or MCP servers.\n\n## Anti-Patterns to Avoid\n\n- Do NOT default to a skill when a hook or MCP config is the real fit.\n- Do NOT treat this skill as the owner of cross-catalog authoring conventions\n  now that `ub-authoring` exists.\n- Do NOT generate giant monolithic files — use progressive disclosure and references.\n- Do NOT use hooks for soft guidance — hooks are for deterministic lifecycle actions.\n- Do NOT use MCP for trivial local tasks — MCP is for real external capabilities.\n- Do NOT grant broad tool or secret access by default — use least privilege and explicit inputs.\n\n## Freshness Review\n\n- Volatility: high\n- Review recommendation: review on touch and during periodic maintenance, targeting a quarterly rhythm when practical.\n- Trigger signals: VS Code Copilot skill, hook, or MCP surface changes; Agent Skills spec changes; MCP schema changes; lifecycle-event changes; or portability guidance changes tied to the official Agent Skills spec.\n- Enforcement: advisory only; freshness warnings should not block unrelated customization work by default.\n- Stable core: smallest-sufficient artifact choice, least privilege, explicit\n  validation, and the builder-versus-authoring ownership split remain the\n  durable guidance.\n",{"name":5,"description":7,"argument-hint":54,"user-invocable":55,"disable-model-invocation":50},"[what to build] [constraints]",true,"main","3185d182c8d358d17a62485cb20f13024a81e429",".agents\u002Fskills\u002Fub-customizations",6,"https:\u002F\u002Fgithub.com\u002Frobert-hoffmann\u002Funcle-bob","https:\u002F\u002Frobert-hoffmann.github.io\u002Funcle-bob\u002F","https:\u002F\u002Fgithub.com\u002Frobert-hoffmann","https:\u002F\u002Fi-technology.net","Tech geek (Psychology, Marketing, Biotech, AI)\r\n\r\n+25 years of experience (Software Engineering, Marketing, B2B\u002FB2C, R&D)","2026-09-23 06:57:44",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":55},[68,71,74],{"tool":69,"command":70},"npx","npx skills add robert-hoffmann\u002Funcle-bob --skill ub-customizations",{"tool":72,"command":73},"bunx","bunx skills add robert-hoffmann\u002Funcle-bob --skill ub-customizations",{"tool":75,"command":76},"pnpm","pnpm dlx skills add robert-hoffmann\u002Funcle-bob --skill ub-customizations","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frobert-hoffmann\u002Funcle-bob\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fub-customizations\u002FSKILL.md",[79,85,89,93,97,101],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fbundles.md","REFERENCE","参考文档",2044,"https:\u002F\u002Fgithub.com\u002Frobert-hoffmann\u002Funcle-bob\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fub-customizations\u002Freferences\u002Fbundles.md",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fhooks.md",5536,"https:\u002F\u002Fgithub.com\u002Frobert-hoffmann\u002Funcle-bob\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fub-customizations\u002Freferences\u002Fhooks.md",{"path":90,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fmcp.md",5254,"https:\u002F\u002Fgithub.com\u002Frobert-hoffmann\u002Funcle-bob\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fub-customizations\u002Freferences\u002Fmcp.md",{"path":94,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fprompt-engineering.md",5156,"https:\u002F\u002Fgithub.com\u002Frobert-hoffmann\u002Funcle-bob\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fub-customizations\u002Freferences\u002Fprompt-engineering.md",{"path":98,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fskills.md",8393,"https:\u002F\u002Fgithub.com\u002Frobert-hoffmann\u002Funcle-bob\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fub-customizations\u002Freferences\u002Fskills.md",{"path":102,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fvalidation.md",4273,"https:\u002F\u002Fgithub.com\u002Frobert-hoffmann\u002Funcle-bob\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fub-customizations\u002Freferences\u002Fvalidation.md",[106,117,127,133,138,144],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":113,"publishedAt":49},"01M6DMC7SMYB87B35SJ9E0TPHQ","beta-skill","Test description for beta-skill","https:\u002F\u002Fgithub.com\u002Frobert-hoffmann\u002Funcle-bob\u002Fblob\u002Fmain\u002Ftests\u002Fskills\u002Fub-governance\u002Ffixtures\u002Frepo_integrity\u002Fpass\u002F.agents\u002Fskills\u002Fbeta-skill\u002FSKILL.md",[112],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[114,115,116],"beta skill","beta","test",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":124,"publishedAt":49},"01M6DMC5730XA703CT93CNYRG1","alpha-skill","Test description for alpha-skill","https:\u002F\u002Fgithub.com\u002Frobert-hoffmann\u002Funcle-bob\u002Fblob\u002Fmain\u002Ftests\u002Fskills\u002Fub-governance\u002Ffixtures\u002Frepo_integrity\u002Fpass\u002F.agents\u002Fskills\u002Falpha-skill\u002FSKILL.md",[123],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[125,126,116],"alpha skill","alpha",{"skillNo":128,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":132,"publishedAt":49},"01M6DMC20EVS4GM93CHNQ6DE54","https:\u002F\u002Fgithub.com\u002Frobert-hoffmann\u002Funcle-bob\u002Fblob\u002Fmain\u002Ftests\u002Fskills\u002Fub-governance\u002Ffixtures\u002Frepo_integrity\u002Ffail-skill-schema\u002F.agents\u002Fskills\u002Fbeta-skill\u002FSKILL.md",[131],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[114,115,116],{"skillNo":134,"name":119,"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":135,"categories":136,"keywords":137,"publishedAt":49},"01M6DMBZBDXQ076Y50Q6Q98V8B","https:\u002F\u002Fgithub.com\u002Frobert-hoffmann\u002Funcle-bob\u002Fblob\u002Fmain\u002Ftests\u002Fskills\u002Fub-governance\u002Ffixtures\u002Frepo_integrity\u002Ffail-skill-schema\u002F.agents\u002Fskills\u002Falpha-skill\u002FSKILL.md",[],[125,126],{"skillNo":139,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":143,"publishedAt":49},"01M6DMBT9Y0TX70ZWH2M9NR0XN","https:\u002F\u002Fgithub.com\u002Frobert-hoffmann\u002Funcle-bob\u002Fblob\u002Fmain\u002Ftests\u002Fskills\u002Fub-governance\u002Ffixtures\u002Frepo_integrity\u002Ffail-readme-agent-drift\u002F.agents\u002Fskills\u002Fbeta-skill\u002FSKILL.md",[142],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[114,115,116],{"skillNo":145,"name":119,"nameZh":6,"description":120,"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":49},"01M6DMBQ4YH9MJ3P9W7CJ148P4","https:\u002F\u002Fgithub.com\u002Frobert-hoffmann\u002Funcle-bob\u002Fblob\u002Fmain\u002Ftests\u002Fskills\u002Fub-governance\u002Ffixtures\u002Frepo_integrity\u002Ffail-readme-agent-drift\u002F.agents\u002Fskills\u002Falpha-skill\u002FSKILL.md",[148],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[126,125,116]]