[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DMACV25QNQC2G0Q5BSQQ1A":3,"skill-same:01M6DMACV25QNQC2G0Q5BSQQ1A":122},{"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":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M6DMACV25QNQC2G0Q5BSQQ1A","ub-tailwind",null,"Use this skill for Tailwind setup, migration, integration, and utility-first styling. Apply it when the task mentions Tailwind directives or utilities, @import \"tailwindcss\", @theme, plugin wiring, legacy-to-modern migration, token bridging with CSS variables, or framework-specific Tailwind build issues.","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-tailwind\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],"ub tailwind","Tailwind","use","css variables","token","bridging","task","build","Legacy","migration","styling","css","first","integration","framework","issues","plugin","setup","tailwindcss","2026-11-10 10:12:30",false,"---\nname: ub-tailwind\ndescription: Use this skill for Tailwind setup, migration, integration, and utility-first styling. Apply it when the task mentions Tailwind directives or utilities, @import \"tailwindcss\", @theme, plugin wiring, legacy-to-modern migration, token bridging with CSS variables, or framework-specific Tailwind build issues.\n---\n\n# UB Tailwind\n\n## Overview\n\nUse this skill to keep Tailwind usage current and correct across different environments and avoid outdated patterns. This skill targets the latest stable Tailwind CSS: enforce CSS-first setup, apply official framework recipes, and replace legacy defaults in generated guidance.\n\nImplement against the detected project and tooling truth, but bias setup and\nmigration guidance toward modern CSS-first Tailwind rather than retaining\nlegacy configuration habits or compatibility layers 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\u002Ftailwind-guardrails.md` for strict do\u002Fdon't rules, deprecated syntax traps, and review checklists.\n- Read `references\u002Fframework-recipes.md` for environment-specific setup paths (standalone HTML\u002FCDN, Vue + Vite, Nuxt).\n- Read `references\u002Ftailwind-legacy-to-modern-migration.md` for migration matrix, upgrade replacements, and compatibility caveats.\n\n## When Not To Use\n\n- Do not use this skill when the task is plain CSS architecture, selector\n  strategy, or token-driven styling without Tailwind as the primary surface;\n  co-load or defer to `ub-css` when Tailwind and CSS architecture overlap.\n- Do not use this skill when the main issue is framework runtime behavior\n  rather than Tailwind integration or utility-class authoring.\n\n## Core Workflow\n\n1. Identify the target environment before writing any Tailwind setup.\n2. Run required detection checks: `nuxt.config.*`, `vite.config.*`, `package.json` dependencies, CSS entrypoints, and Nuxt app stylesheet placement (for modern Nuxt, expect `app\u002Fassets\u002Fcss\u002Fmain.css`).\n3. Choose the matching recipe from `references\u002Fframework-recipes.md`.\n4. Compare official guidance, repo truth, and observed code reality for\n   non-trivial or version-sensitive recommendations.\n5. Surface `OFFICIAL_CONFLICT` when authoritative sources, repo truth, or live\n   code reality materially disagree on a non-trivial recommendation.\n6. Surface `UNVERIFIED` when a non-trivial claim could not be confirmed in\n   official sources after targeted research.\n7. Apply modern Tailwind CSS-first rules from `references\u002Ftailwind-guardrails.md`.\n8. Apply upgrade-safe replacements from `references\u002Ftailwind-legacy-to-modern-migration.md`.\n9. Run the environment-specific validation checklist.\n10. Reject and replace deprecated or legacy syntax.\n\n## Environment Selection\n\n- Use the **Standalone HTML\u002FCDN** recipe for plain HTML pages without a build tool.\n- Use the **Vue + Vite** recipe for Vue projects with Vite bundling.\n- Use the **Nuxt** recipe for Nuxt apps where integration details differ from plain Vite.\n- For Nuxt, default to the official setup path (`@tailwindcss\u002Fvite` wired in `nuxt.config.*`), not legacy module defaults.\n\nIf the environment is unclear, inspect project markers first (`package.json`, framework config, build plugins) and do not guess.\n\n## Non-Negotiable Guardrails\n\n### Tailwind Version and Syntax\n\n- Use modern Tailwind CSS-first patterns and current docs semantics.\n- Prefer CSS entrypoint `@import \"tailwindcss\"`.\n- Prefer CSS directives like `@theme`, `@utility`, `@variant`, `@custom-variant`, `@source`, and `@reference` as needed.\n- Treat `@config` and `@plugin` as legacy paths unless explicitly required for compatibility.\n- Prefer compatibility only as a bounded layer with a documented migration back to CSS-first defaults.\n\n### Build Strategy\n\n- Do not assume PostCSS is required for modern Tailwind.\n- Use Vite plugin integration where applicable (`@tailwindcss\u002Fvite`) for Vue + Vite workflows.\n- For Nuxt, use the official Nuxt framework-guide flow and configure the Vite plugin under Nuxt config instead of creating Vue-only `vite.config.*` instructions.\n- Keep setup minimal and environment-native.\n\n### Vue\u002FNuxt Style Context\n\n- For Vue\u002FNuxt component-scoped styles using `@apply` or `@variant`, include `@reference` to the main stylesheet or app stylesheet context.\n- Avoid duplicating imported CSS just to expose theme values in component-local styles.\n\n### Design Tokens\n\n- Keep Tailwind tokens centralized in `@theme`.\n- Reuse existing token primitives and avoid ad-hoc hardcoded drift.\n\n### Do Not Generate\n\n- Do not generate `@tailwind base;`, `@tailwind components;`, `@tailwind utilities;` as the default modern entrypoint.\n- Do not assume PostCSS setup is mandatory for modern Tailwind.\n- Do not default to `@nuxtjs\u002Ftailwindcss` as the first-line setup for fresh Nuxt guidance.\n\n## Output Requirements\n\nWhen generating or modifying code, always provide:\n\n1. A short environment detection note.\n2. A source truth note: detected project version, environment markers, and any\n   material gap versus latest stable guidance.\n3. The selected setup path (CDN, Vue + Vite, or Nuxt).\n4. Exact deprecated-to-modern replacements applied (syntax\u002Ftooling\u002Futility changes).\n5. A quick validation checklist confirming modern Tailwind setup.\n6. Compatibility notes when legacy directives (`@config`\u002F`@plugin`) are retained.\n7. Conflict note when relevant: `OFFICIAL_CONFLICT` or `UNVERIFIED` with a\n   concise explanation and the implementation consequence.\n\n## Version & Research Policy\n\n- Target the latest stable release of Tailwind CSS.\n- Detect the project's actual Tailwind version from `package.json` and lockfiles.\n- Use web search to verify current best practices, directive availability, and migration guidance against official Tailwind CSS 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 Tailwind 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- 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: official migration changes, deprecated directives, major Tailwind releases, or repo toolchain changes that affect setup recipes.\n- Enforcement: advisory only; stale Tailwind guidance is a review signal, not a blocking gate by itself.\n- Stable core: environment detection, official recipe selection, and deprecated-syntax avoidance should remain useful even when exact setup details evolve.\n\n## Completion Checklist\n\n- Environment explicitly identified before setup.\n- Tailwind entrypoint and directives align with modern guidance.\n- No deprecated\u002Flegacy syntax remains without explicit compatibility reason.\n- Framework-specific differences are handled (CDN vs Vite vs Nuxt).\n- Nuxt guidance uses the official framework path and does not drift into Vue-only `vite.config.*` steps.\n- Token usage is centralized and consistent.\n- Generated instructions are concise, deterministic, and current-version oriented.\n- Any material official-source conflict or unverified non-trivial guidance is\n  disclosed explicitly when relevant.\n","# UB Tailwind\n\n## Overview\n\nUse this skill to keep Tailwind usage current and correct across different environments and avoid outdated patterns. This skill targets the latest stable Tailwind CSS: enforce CSS-first setup, apply official framework recipes, and replace legacy defaults in generated guidance.\n\nImplement against the detected project and tooling truth, but bias setup and\nmigration guidance toward modern CSS-first Tailwind rather than retaining\nlegacy configuration habits or compatibility layers 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\u002Ftailwind-guardrails.md` for strict do\u002Fdon't rules, deprecated syntax traps, and review checklists.\n- Read `references\u002Fframework-recipes.md` for environment-specific setup paths (standalone HTML\u002FCDN, Vue + Vite, Nuxt).\n- Read `references\u002Ftailwind-legacy-to-modern-migration.md` for migration matrix, upgrade replacements, and compatibility caveats.\n\n## When Not To Use\n\n- Do not use this skill when the task is plain CSS architecture, selector\n  strategy, or token-driven styling without Tailwind as the primary surface;\n  co-load or defer to `ub-css` when Tailwind and CSS architecture overlap.\n- Do not use this skill when the main issue is framework runtime behavior\n  rather than Tailwind integration or utility-class authoring.\n\n## Core Workflow\n\n1. Identify the target environment before writing any Tailwind setup.\n2. Run required detection checks: `nuxt.config.*`, `vite.config.*`, `package.json` dependencies, CSS entrypoints, and Nuxt app stylesheet placement (for modern Nuxt, expect `app\u002Fassets\u002Fcss\u002Fmain.css`).\n3. Choose the matching recipe from `references\u002Fframework-recipes.md`.\n4. Compare official guidance, repo truth, and observed code reality for\n   non-trivial or version-sensitive recommendations.\n5. Surface `OFFICIAL_CONFLICT` when authoritative sources, repo truth, or live\n   code reality materially disagree on a non-trivial recommendation.\n6. Surface `UNVERIFIED` when a non-trivial claim could not be confirmed in\n   official sources after targeted research.\n7. Apply modern Tailwind CSS-first rules from `references\u002Ftailwind-guardrails.md`.\n8. Apply upgrade-safe replacements from `references\u002Ftailwind-legacy-to-modern-migration.md`.\n9. Run the environment-specific validation checklist.\n10. Reject and replace deprecated or legacy syntax.\n\n## Environment Selection\n\n- Use the **Standalone HTML\u002FCDN** recipe for plain HTML pages without a build tool.\n- Use the **Vue + Vite** recipe for Vue projects with Vite bundling.\n- Use the **Nuxt** recipe for Nuxt apps where integration details differ from plain Vite.\n- For Nuxt, default to the official setup path (`@tailwindcss\u002Fvite` wired in `nuxt.config.*`), not legacy module defaults.\n\nIf the environment is unclear, inspect project markers first (`package.json`, framework config, build plugins) and do not guess.\n\n## Non-Negotiable Guardrails\n\n### Tailwind Version and Syntax\n\n- Use modern Tailwind CSS-first patterns and current docs semantics.\n- Prefer CSS entrypoint `@import \"tailwindcss\"`.\n- Prefer CSS directives like `@theme`, `@utility`, `@variant`, `@custom-variant`, `@source`, and `@reference` as needed.\n- Treat `@config` and `@plugin` as legacy paths unless explicitly required for compatibility.\n- Prefer compatibility only as a bounded layer with a documented migration back to CSS-first defaults.\n\n### Build Strategy\n\n- Do not assume PostCSS is required for modern Tailwind.\n- Use Vite plugin integration where applicable (`@tailwindcss\u002Fvite`) for Vue + Vite workflows.\n- For Nuxt, use the official Nuxt framework-guide flow and configure the Vite plugin under Nuxt config instead of creating Vue-only `vite.config.*` instructions.\n- Keep setup minimal and environment-native.\n\n### Vue\u002FNuxt Style Context\n\n- For Vue\u002FNuxt component-scoped styles using `@apply` or `@variant`, include `@reference` to the main stylesheet or app stylesheet context.\n- Avoid duplicating imported CSS just to expose theme values in component-local styles.\n\n### Design Tokens\n\n- Keep Tailwind tokens centralized in `@theme`.\n- Reuse existing token primitives and avoid ad-hoc hardcoded drift.\n\n### Do Not Generate\n\n- Do not generate `@tailwind base;`, `@tailwind components;`, `@tailwind utilities;` as the default modern entrypoint.\n- Do not assume PostCSS setup is mandatory for modern Tailwind.\n- Do not default to `@nuxtjs\u002Ftailwindcss` as the first-line setup for fresh Nuxt guidance.\n\n## Output Requirements\n\nWhen generating or modifying code, always provide:\n\n1. A short environment detection note.\n2. A source truth note: detected project version, environment markers, and any\n   material gap versus latest stable guidance.\n3. The selected setup path (CDN, Vue + Vite, or Nuxt).\n4. Exact deprecated-to-modern replacements applied (syntax\u002Ftooling\u002Futility changes).\n5. A quick validation checklist confirming modern Tailwind setup.\n6. Compatibility notes when legacy directives (`@config`\u002F`@plugin`) are retained.\n7. Conflict note when relevant: `OFFICIAL_CONFLICT` or `UNVERIFIED` with a\n   concise explanation and the implementation consequence.\n\n## Version & Research Policy\n\n- Target the latest stable release of Tailwind CSS.\n- Detect the project's actual Tailwind version from `package.json` and lockfiles.\n- Use web search to verify current best practices, directive availability, and migration guidance against official Tailwind CSS 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 Tailwind 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- 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: official migration changes, deprecated directives, major Tailwind releases, or repo toolchain changes that affect setup recipes.\n- Enforcement: advisory only; stale Tailwind guidance is a review signal, not a blocking gate by itself.\n- Stable core: environment detection, official recipe selection, and deprecated-syntax avoidance should remain useful even when exact setup details evolve.\n\n## Completion Checklist\n\n- Environment explicitly identified before setup.\n- Tailwind entrypoint and directives align with modern guidance.\n- No deprecated\u002Flegacy syntax remains without explicit compatibility reason.\n- Framework-specific differences are handled (CDN vs Vite vs Nuxt).\n- Nuxt guidance uses the official framework path and does not drift into Vue-only `vite.config.*` steps.\n- Token usage is centralized and consistent.\n- Generated instructions are concise, deterministic, and current-version oriented.\n- Any material official-source conflict or unverified non-trivial guidance is\n  disclosed explicitly when relevant.\n",{"name":5,"description":7},"main","3185d182c8d358d17a62485cb20f13024a81e429",".agents\u002Fskills\u002Fub-tailwind",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-tailwind",{"tool":64,"command":65},"bunx","bunx skills add robert-hoffmann\u002Funcle-bob --skill ub-tailwind",{"tool":67,"command":68},"pnpm","pnpm dlx skills add robert-hoffmann\u002Funcle-bob --skill ub-tailwind","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frobert-hoffmann\u002Funcle-bob\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fub-tailwind\u002FSKILL.md",true,[72,78,82,86,90,94,98,102,106,110,114,118],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"README.md","REFERENCE","参考文档",3893,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsecurity-compliance-risk\u002Fsecurity-reference\u002Fconstant-time-analysis\u002FREADME.md",{"path":79,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fcompiled.md",4108,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsecurity-compliance-risk\u002Fsecurity-reference\u002Fconstant-time-analysis\u002Freferences\u002Fcompiled.md",{"path":83,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fframework-recipes.md",3117,"https:\u002F\u002Fgithub.com\u002Frobert-hoffmann\u002Funcle-bob\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fub-tailwind\u002Freferences\u002Fframework-recipes.md",{"path":87,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fjavascript.md",4449,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsecurity-compliance-risk\u002Fsecurity-reference\u002Fconstant-time-analysis\u002Freferences\u002Fjavascript.md",{"path":91,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fkotlin.md",6784,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsecurity-compliance-risk\u002Fsecurity-reference\u002Fconstant-time-analysis\u002Freferences\u002Fkotlin.md",{"path":95,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fphp.md",4831,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsecurity-compliance-risk\u002Fsecurity-reference\u002Fconstant-time-analysis\u002Freferences\u002Fphp.md",{"path":99,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fpython.md",5261,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsecurity-compliance-risk\u002Fsecurity-reference\u002Fconstant-time-analysis\u002Freferences\u002Fpython.md",{"path":103,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fruby.md",5391,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsecurity-compliance-risk\u002Fsecurity-reference\u002Fconstant-time-analysis\u002Freferences\u002Fruby.md",{"path":107,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Fswift.md",8194,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsecurity-compliance-risk\u002Fsecurity-reference\u002Fconstant-time-analysis\u002Freferences\u002Fswift.md",{"path":111,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":112,"sourceHtmlUrl":113},"references\u002Ftailwind-guardrails.md",3710,"https:\u002F\u002Fgithub.com\u002Frobert-hoffmann\u002Funcle-bob\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fub-tailwind\u002Freferences\u002Ftailwind-guardrails.md",{"path":115,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":116,"sourceHtmlUrl":117},"references\u002Ftailwind-legacy-to-modern-migration.md",3642,"https:\u002F\u002Fgithub.com\u002Frobert-hoffmann\u002Funcle-bob\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fub-tailwind\u002Freferences\u002Ftailwind-legacy-to-modern-migration.md",{"path":119,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":120,"sourceHtmlUrl":121},"references\u002Fvm-compiled.md",10409,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fsecurity-compliance-risk\u002Fsecurity-reference\u002Fconstant-time-analysis\u002Freferences\u002Fvm-compiled.md",[123,136,146,152,157,163],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":132,"publishedAt":43},"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",[129],{"categoryNo":130,"categoryName":131,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[133,134,135],"beta skill","beta","test",{"skillNo":137,"name":138,"nameZh":6,"description":139,"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":43},"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",[142],{"categoryNo":130,"categoryName":131,"taxonomyType":21,"taxonomyTypeDesc":22},[144,145,135],"alpha skill","alpha",{"skillNo":147,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":151,"publishedAt":43},"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",[150],{"categoryNo":130,"categoryName":131,"taxonomyType":21,"taxonomyTypeDesc":22},[133,134,135],{"skillNo":153,"name":138,"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":154,"categories":155,"keywords":156,"publishedAt":43},"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",[],[144,145],{"skillNo":158,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":162,"publishedAt":43},"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",[161],{"categoryNo":130,"categoryName":131,"taxonomyType":21,"taxonomyTypeDesc":22},[133,134,135],{"skillNo":164,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":168,"publishedAt":43},"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",[167],{"categoryNo":130,"categoryName":131,"taxonomyType":21,"taxonomyTypeDesc":22},[145,144,135]]