[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DMAZCAANEZGW8ADJX9KA2B":3,"skill-same:01M6DMAZCAANEZGW8ADJX9KA2B":82},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":30,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M6DMAZCAANEZGW8ADJX9KA2B","ub-vuejs",null,"Use this skill for Vue component and composable authoring. Apply it when the task involves SFCs, reactivity, watchers, props or emits contracts, template patterns, SSR or hydration primitives, or Vue-core architecture in Vite projects and in Nuxt projects when the main issue is Vue authoring rather than Nuxt runtime behavior.","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-vuejs\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"ub vuejs","use","watchers","authoring","runtime","patterns","main","task","issue","vite","component","behavior","nuxt","template","projects","vue","core","composable","ssr","architecture","2026-11-10 10:12:30",false,"---\nname: ub-vuejs\ndescription: Use this skill for Vue component and composable authoring. Apply it when the task involves SFCs, reactivity, watchers, props or emits contracts, template patterns, SSR or hydration primitives, or Vue-core architecture in Vite projects and in Nuxt projects when the main issue is Vue authoring rather than Nuxt runtime behavior.\n---\n\n# UB VueJS\n\n## Overview\n\nUse this skill to enforce Vue core best practices for the latest stable release with strict TypeScript and migration-aware legacy handling. Generate only modern patterns for new code and refactor existing legacy patterns incrementally.\n\nImplement against the detected project and runtime truth, but bias component\ndesign toward forward-compatible migration rather than retaining legacy\npatterns or outdated guidance by default.\n\n## Load References On Demand\n\n- Read `..\u002Fub-authoring\u002Freferences\u002Fauthoring-conventions.md` when adjusting routing\n  guidance or cross-skill authoring conventions.\n- Read `references\u002Fvue-modern-patterns.md` for the canonical modern Vue recipes and API usage patterns.\n- Read `references\u002Fvue-legacy-to-modern-migration.md` for migration mapping, compatibility exceptions, and modernization sequence.\n\n## When Not To Use\n\n- Do not use this skill when the task depends primarily on Nuxt runtime\n  behavior, app-directory policy, server routes, or Nitro concerns; co-load or\n  defer that to `ub-nuxt` depending on whether Vue authoring remains a\n  first-class concern.\n- Do not use this skill when the main issue is Tailwind integration or plain\n  CSS architecture rather than Vue component logic.\n\n## Core Workflow\n\n1. Detect Vue version family and tooling from `package.json`, lockfiles, `vite.config.*`, `vue.config.*`, and TypeScript config.\n2. Confirm the task is Vue core scope (SFCs, reactivity, watchers, SSR and hydration, component contracts). If the task is Nuxt-specific, co-load or defer framework rules to `.agents\u002Fskills\u002Fub-nuxt\u002FSKILL.md`.\n3. Compare official guidance, repo truth, and observed code reality for\n   non-trivial or version-sensitive recommendations.\n4. Surface `OFFICIAL_CONFLICT` when authoritative sources, repo truth, or live\n   code reality materially disagree on a non-trivial recommendation.\n5. Surface `UNVERIFIED` when a non-trivial claim could not be confirmed in\n   official sources after targeted research.\n6. Implement with strict TypeScript and SFC default `script setup` plus `lang=\"ts\"`.\n7. Apply modern Vue patterns from `references\u002Fvue-modern-patterns.md`.\n8. Reject legacy output and apply migration mapping from `references\u002Fvue-legacy-to-modern-migration.md` when updating existing code.\n9. Validate behavior with typecheck, lint, and tests available in the target project.\n\n## Version & Research Policy\n\n- Target the latest stable release of Vue.\n- Detect the project's actual Vue version from `package.json` and lockfiles.\n- Use web search to verify current best practices, API availability, and migration guidance against official Vue documentation.\n- Treat repo truth as the gold implementation standard when deciding what can\n  actually ship safely in the current project.\n- Treat official Vue docs as the preferred guidance baseline for\n  forward-looking design and migration-ready patterns.\n- If official guidance and repo truth diverge materially on a non-trivial\n  recommendation, surface `OFFICIAL_CONFLICT`, implement the repo-safe path,\n  and explain the migration path.\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  version-sensitive, or contested guidance rather than trivial edits.\n- When the project's installed version is behind latest stable, note the version gap and recommend an upgrade path.\n- Do not use pre-release or beta features unless explicitly requested.\n- Inspect the host repository's `AGENTS.md` or equivalent instructions when\n  present for project-specific version policy and tooling; do not assume it\n  contains this catalog's defaults.\n- Do not hardcode version numbers in generated guidance — keep recommendations evergreen.\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: Vue core API additions, hydration or watcher semantics changes, new migration guidance, or repo toolchain changes affecting Vue authoring.\n- Enforcement: advisory only; stale Vue guidance should prompt review rather than create automatic blockers.\n- Stable core: Composition API, strict TypeScript, and disciplined watcher patterns remain the stable baseline even when ergonomic details change.\n\n## Implementation Rules\n\n### Core Vue and SFC\n\n- Require TypeScript in generated code.\n- Default to `script setup` plus `lang=\"ts\"` for SFC authoring.\n- Use Composition API and compiler macros for new code.\n- Prefer `defineModel()` for component `v-model` contracts in new code.\n- Prefer `useTemplateRef()` for string-based template refs.\n\n### Reactivity and Watchers\n\n- Use reactive props destructure in script setup where it improves clarity.\n- Watch destructured props with getter sources, never pass the value directly as a watch source.\n- Use `MaybeRefOrGetter\u003CT>` and `toValue()` for composables that accept value, ref, or getter inputs.\n- Consider `VueUse` (`vueuse.org`, especially `@vueuse\u002Fcore`) before writing\n  bespoke generic composables for browser APIs, events, timers, storage,\n  sensors, or async state helpers.\n- Register `onWatcherCleanup()` synchronously before any `await` boundary in watcher callbacks.\n- Prefer precise getters for watch sources; use numeric `deep` only when necessary.\n\n### SSR and Hydration\n\n- Use `useId()` for SSR-safe ID generation.\n- Use lazy hydration strategies for async components when rendering heavy below-the-fold islands.\n- Use `data-allow-mismatch` narrowly and document justification for each mismatch type.\n- Use `Teleport defer` when the target is created later in the same render tick.\n\n### Performance and Build Hygiene\n\n- Prioritize high-leverage optimizations: stable props, code splitting, large-list virtualization, and controlled deep reactivity.\n- Keep compile-time flags intentional and explicit in build configuration.\n- Avoid premature micro-optimizations that are not backed by measurements.\n\n## Legacy-Avoidance Guardrails\n\n- Do not generate Options API for new code.\n- Do not generate class-style components, mixins, filters, or `this`-centric component logic for new code.\n- Do not generate manual `modelValue` and `update:modelValue` boilerplate when `defineModel()` is viable.\n- Do not generate `ref(null)` template-ref patterns when `useTemplateRef()` is available and suitable.\n- Do not generate watcher code that registers cleanup after an async boundary.\n\nMigration-aware exception policy (see `references\u002Fvue-legacy-to-modern-migration.md`):\n\n- Allow temporary legacy retention only when required for bounded compatibility in existing codebases.\n- Document each retained legacy pattern, why it is retained, and the exact follow-up modernization path.\n\nNon-goals:\n\n- Do not encode Nuxt-specific directory\u002Fruntime policy in this skill; defer to `ub-nuxt`.\n- Do not provide deep Tailwind implementation guidance in this skill; defer to `ub-tailwind`.\n\n## Output Requirements\n\nWhen generating or reviewing code, always include:\n\n1. Environment note: Vue version family, TypeScript state, and key tooling detected.\n2. Source truth note: detected project version and toolchain reality, plus any\n   material gap versus latest stable guidance.\n3. Version note: detected Vue version and whether any pre-release behavior is intentionally excluded.\n4. Pattern note: which modern APIs were selected and why.\n5. Legacy note: what legacy patterns were removed or intentionally retained with compatibility rationale.\n6. Validation note: what checks were run (typecheck, lint, tests, build) and outcomes.\n7. Conflict note when relevant: `OFFICIAL_CONFLICT` or `UNVERIFIED` with a\n   concise explanation and the implementation consequence.\n\n## Completion Checklist\n\n- Latest stable Vue baseline and TypeScript requirement are enforced.\n- New code uses Composition API and script setup with lang ts.\n- `defineModel`, `useTemplateRef`, and modern watcher patterns are used where relevant.\n- SSR and hydration primitives are used correctly when SSR is in scope.\n- No new legacy output is introduced.\n- Any retained legacy is explicitly justified with an incremental migration path.\n- Nuxt and Tailwind concerns are delegated to their dedicated skills when applicable.\n- Any material official-source conflict or unverified non-trivial guidance is\n  disclosed explicitly when relevant.\n","# UB VueJS\n\n## Overview\n\nUse this skill to enforce Vue core best practices for the latest stable release with strict TypeScript and migration-aware legacy handling. Generate only modern patterns for new code and refactor existing legacy patterns incrementally.\n\nImplement against the detected project and runtime truth, but bias component\ndesign toward forward-compatible migration rather than retaining legacy\npatterns or outdated guidance by default.\n\n## Load References On Demand\n\n- Read `..\u002Fub-authoring\u002Freferences\u002Fauthoring-conventions.md` when adjusting routing\n  guidance or cross-skill authoring conventions.\n- Read `references\u002Fvue-modern-patterns.md` for the canonical modern Vue recipes and API usage patterns.\n- Read `references\u002Fvue-legacy-to-modern-migration.md` for migration mapping, compatibility exceptions, and modernization sequence.\n\n## When Not To Use\n\n- Do not use this skill when the task depends primarily on Nuxt runtime\n  behavior, app-directory policy, server routes, or Nitro concerns; co-load or\n  defer that to `ub-nuxt` depending on whether Vue authoring remains a\n  first-class concern.\n- Do not use this skill when the main issue is Tailwind integration or plain\n  CSS architecture rather than Vue component logic.\n\n## Core Workflow\n\n1. Detect Vue version family and tooling from `package.json`, lockfiles, `vite.config.*`, `vue.config.*`, and TypeScript config.\n2. Confirm the task is Vue core scope (SFCs, reactivity, watchers, SSR and hydration, component contracts). If the task is Nuxt-specific, co-load or defer framework rules to `.agents\u002Fskills\u002Fub-nuxt\u002FSKILL.md`.\n3. Compare official guidance, repo truth, and observed code reality for\n   non-trivial or version-sensitive recommendations.\n4. Surface `OFFICIAL_CONFLICT` when authoritative sources, repo truth, or live\n   code reality materially disagree on a non-trivial recommendation.\n5. Surface `UNVERIFIED` when a non-trivial claim could not be confirmed in\n   official sources after targeted research.\n6. Implement with strict TypeScript and SFC default `script setup` plus `lang=\"ts\"`.\n7. Apply modern Vue patterns from `references\u002Fvue-modern-patterns.md`.\n8. Reject legacy output and apply migration mapping from `references\u002Fvue-legacy-to-modern-migration.md` when updating existing code.\n9. Validate behavior with typecheck, lint, and tests available in the target project.\n\n## Version & Research Policy\n\n- Target the latest stable release of Vue.\n- Detect the project's actual Vue version from `package.json` and lockfiles.\n- Use web search to verify current best practices, API availability, and migration guidance against official Vue documentation.\n- Treat repo truth as the gold implementation standard when deciding what can\n  actually ship safely in the current project.\n- Treat official Vue docs as the preferred guidance baseline for\n  forward-looking design and migration-ready patterns.\n- If official guidance and repo truth diverge materially on a non-trivial\n  recommendation, surface `OFFICIAL_CONFLICT`, implement the repo-safe path,\n  and explain the migration path.\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  version-sensitive, or contested guidance rather than trivial edits.\n- When the project's installed version is behind latest stable, note the version gap and recommend an upgrade path.\n- Do not use pre-release or beta features unless explicitly requested.\n- Inspect the host repository's `AGENTS.md` or equivalent instructions when\n  present for project-specific version policy and tooling; do not assume it\n  contains this catalog's defaults.\n- Do not hardcode version numbers in generated guidance — keep recommendations evergreen.\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: Vue core API additions, hydration or watcher semantics changes, new migration guidance, or repo toolchain changes affecting Vue authoring.\n- Enforcement: advisory only; stale Vue guidance should prompt review rather than create automatic blockers.\n- Stable core: Composition API, strict TypeScript, and disciplined watcher patterns remain the stable baseline even when ergonomic details change.\n\n## Implementation Rules\n\n### Core Vue and SFC\n\n- Require TypeScript in generated code.\n- Default to `script setup` plus `lang=\"ts\"` for SFC authoring.\n- Use Composition API and compiler macros for new code.\n- Prefer `defineModel()` for component `v-model` contracts in new code.\n- Prefer `useTemplateRef()` for string-based template refs.\n\n### Reactivity and Watchers\n\n- Use reactive props destructure in script setup where it improves clarity.\n- Watch destructured props with getter sources, never pass the value directly as a watch source.\n- Use `MaybeRefOrGetter\u003CT>` and `toValue()` for composables that accept value, ref, or getter inputs.\n- Consider `VueUse` (`vueuse.org`, especially `@vueuse\u002Fcore`) before writing\n  bespoke generic composables for browser APIs, events, timers, storage,\n  sensors, or async state helpers.\n- Register `onWatcherCleanup()` synchronously before any `await` boundary in watcher callbacks.\n- Prefer precise getters for watch sources; use numeric `deep` only when necessary.\n\n### SSR and Hydration\n\n- Use `useId()` for SSR-safe ID generation.\n- Use lazy hydration strategies for async components when rendering heavy below-the-fold islands.\n- Use `data-allow-mismatch` narrowly and document justification for each mismatch type.\n- Use `Teleport defer` when the target is created later in the same render tick.\n\n### Performance and Build Hygiene\n\n- Prioritize high-leverage optimizations: stable props, code splitting, large-list virtualization, and controlled deep reactivity.\n- Keep compile-time flags intentional and explicit in build configuration.\n- Avoid premature micro-optimizations that are not backed by measurements.\n\n## Legacy-Avoidance Guardrails\n\n- Do not generate Options API for new code.\n- Do not generate class-style components, mixins, filters, or `this`-centric component logic for new code.\n- Do not generate manual `modelValue` and `update:modelValue` boilerplate when `defineModel()` is viable.\n- Do not generate `ref(null)` template-ref patterns when `useTemplateRef()` is available and suitable.\n- Do not generate watcher code that registers cleanup after an async boundary.\n\nMigration-aware exception policy (see `references\u002Fvue-legacy-to-modern-migration.md`):\n\n- Allow temporary legacy retention only when required for bounded compatibility in existing codebases.\n- Document each retained legacy pattern, why it is retained, and the exact follow-up modernization path.\n\nNon-goals:\n\n- Do not encode Nuxt-specific directory\u002Fruntime policy in this skill; defer to `ub-nuxt`.\n- Do not provide deep Tailwind implementation guidance in this skill; defer to `ub-tailwind`.\n\n## Output Requirements\n\nWhen generating or reviewing code, always include:\n\n1. Environment note: Vue version family, TypeScript state, and key tooling detected.\n2. Source truth note: detected project version and toolchain reality, plus any\n   material gap versus latest stable guidance.\n3. Version note: detected Vue version and whether any pre-release behavior is intentionally excluded.\n4. Pattern note: which modern APIs were selected and why.\n5. Legacy note: what legacy patterns were removed or intentionally retained with compatibility rationale.\n6. Validation note: what checks were run (typecheck, lint, tests, build) and outcomes.\n7. Conflict note when relevant: `OFFICIAL_CONFLICT` or `UNVERIFIED` with a\n   concise explanation and the implementation consequence.\n\n## Completion Checklist\n\n- Latest stable Vue baseline and TypeScript requirement are enforced.\n- New code uses Composition API and script setup with lang ts.\n- `defineModel`, `useTemplateRef`, and modern watcher patterns are used where relevant.\n- SSR and hydration primitives are used correctly when SSR is in scope.\n- No new legacy output is introduced.\n- Any retained legacy is explicitly justified with an incremental migration path.\n- Nuxt and Tailwind concerns are delegated to their dedicated skills when applicable.\n- Any material official-source conflict or unverified non-trivial guidance is\n  disclosed explicitly when relevant.\n",{"name":5,"description":7},"3185d182c8d358d17a62485cb20f13024a81e429",".agents\u002Fskills\u002Fub-vuejs",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":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add robert-hoffmann\u002Funcle-bob --skill ub-vuejs",{"tool":64,"command":65},"bunx","bunx skills add robert-hoffmann\u002Funcle-bob --skill ub-vuejs",{"tool":67,"command":68},"pnpm","pnpm dlx skills add robert-hoffmann\u002Funcle-bob --skill ub-vuejs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frobert-hoffmann\u002Funcle-bob\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fub-vuejs\u002FSKILL.md",true,[72,78],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fvue-legacy-to-modern-migration.md","REFERENCE","参考文档",3612,"https:\u002F\u002Fgithub.com\u002Frobert-hoffmann\u002Funcle-bob\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fub-vuejs\u002Freferences\u002Fvue-legacy-to-modern-migration.md",{"path":79,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fvue-modern-patterns.md",4024,"https:\u002F\u002Fgithub.com\u002Frobert-hoffmann\u002Funcle-bob\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fub-vuejs\u002Freferences\u002Fvue-modern-patterns.md",[83,96,106,112,117,123],{"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":92,"publishedAt":44},"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",[89],{"categoryNo":90,"categoryName":91,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[93,94,95],"beta skill","beta","test",{"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":103,"publishedAt":44},"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",[102],{"categoryNo":90,"categoryName":91,"taxonomyType":21,"taxonomyTypeDesc":22},[104,105,95],"alpha skill","alpha",{"skillNo":107,"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":108,"categories":109,"keywords":111,"publishedAt":44},"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",[110],{"categoryNo":90,"categoryName":91,"taxonomyType":21,"taxonomyTypeDesc":22},[93,94,95],{"skillNo":113,"name":98,"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":114,"categories":115,"keywords":116,"publishedAt":44},"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",[],[104,105],{"skillNo":118,"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":119,"categories":120,"keywords":122,"publishedAt":44},"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",[121],{"categoryNo":90,"categoryName":91,"taxonomyType":21,"taxonomyTypeDesc":22},[93,94,95],{"skillNo":124,"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":125,"categories":126,"keywords":128,"publishedAt":44},"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",[127],{"categoryNo":90,"categoryName":91,"taxonomyType":21,"taxonomyTypeDesc":22},[105,104,95]]