[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FX705AX9SVEAY1KSWVM6EE":3,"skill-same:01M6FX705AX9SVEAY1KSWVM6EE":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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":63,"ownerHtmlUrl":64,"ownerBlogUrl":65,"ownerDescription":66,"updatedAt":67,"install":68,"resources":81},"01M6FX705AX9SVEAY1KSWVM6EE","design-system",null,"Extract or scan design tokens from a consolidated UI spec or existing codebase and produce a DESIGN.md file following the Google Labs Stitch format — machine-readable YAML frontmatter with prose rationale sections","GeorgeQLe\u002Fagentic-skills","GeorgeQLe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F21134126?v=4","01M6D2JP418S0VGJGF8M93EC3H","George Le","01M6D2JPBAKYD82TA5FS6HKQ3D",1,"MIT","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fproduct-design\u002Fclaude\u002Fdesign-system\u002Farchive\u002Fv0.3\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"design","design system","system","with","machine","tokens","scan","stitch","alignment","design tokens","page","format","yaml","file","produce","planning","update","prototype","spec","google","2026-11-10 10:12:30",false,"---\nname: design-system\ndescription: Extract or scan design tokens from a consolidated UI spec or existing codebase and produce a DESIGN.md file following the Google Labs Stitch format — machine-readable YAML frontmatter with prose rationale sections\ntype: planning\nversion: v0.3\nrequired_conventions: [alignment-page]\nargument-hint: \"[spec path | --scan | --update]\"\nvisual_tier: prototype\n---\n\n# Design System\n\nInvoke as `\u002Fdesign-system`.\n\nUse this skill after `\u002Fconsolidate-prototypes` to lock design decisions into machine-readable tokens before implementation begins. It bridges the gap between prose UI specs and code — without it, agents interpret \"dark surface with primary accent\" differently each session, causing UI consistency drift.\n\nAlso use this skill retroactively on an existing codebase (`--scan`) to generate a DESIGN.md from tokens already in use.\n\n## Modes\n\n- **Default**: reads `specs\u002Fui-final-*.md` or `prototypes\u002F*\u002Fconsolidated\u002F` (or a user-provided spec path) and extracts tokens.\n- **`--scan`**: scans the codebase for CSS custom properties, Tailwind config, theme files, and component patterns to reverse-engineer a DESIGN.md.\n- **`--update`**: reads an existing `DESIGN.md` alongside new spec changes and produces an updated version.\n\n## Process\n\n1. **Resolve context**\n   - Read `.agents\u002Fproject.json`, `README.md`, `AGENTS.md`, `CLAUDE.md` when present.\n   - Locate the input source:\n     - Default: find `specs\u002Fui-final-*.md` or accept a path argument.\n     - `--scan`: find `tailwind.config.*`, `globals.css`, CSS custom property files, theme files, component directories, and any existing design token files.\n     - `--update`: read the existing `DESIGN.md` and the changed spec or codebase files.\n   - If no input can be found, ask the user to point to the source.\n\n2. **Extract raw tokens**\n   - From spec: pull every concrete visual decision — colors (hex, HSL, OKLCH), font families, font sizes, weights, line heights, spacing values, border radii, shadows, elevation layers, and component-level styling.\n   - From codebase (`--scan`): parse Tailwind config extends, CSS custom properties, repeated Tailwind classes, theme provider values, and component prop defaults. Deduplicate and group by semantic role.\n   - Normalize all colors to hex. Record OKLCH or HSL originals as comments when present.\n   - Identify semantic roles: primary, secondary, accent, surface, background, on-primary, on-surface, error, warning, success, info, border, muted.\n\n3. **Interview to confirm tokens**\n   - Present the extracted token inventory grouped by category (Colors, Typography, Spacing, Shapes, Elevation, Components).\n   - For each category, use AskUserQuestion (1–3 questions per turn):\n     - Are these the correct values? Flag any that look like defaults vs intentional choices.\n     - Are there missing semantic roles? (e.g., no error color found, no hover state defined)\n     - For typography: confirm the scale — is this intentional or inherited from a framework default?\n     - For spacing: confirm the scale — 4px base? 8px base? Irregular?\n   - Record user confirmations and adjustments.\n\n4. **Validate accessibility**\n   - Check WCAG 2.1 AA contrast ratios for all foreground\u002Fbackground color pairings:\n     - Normal text: minimum 4.5:1\n     - Large text (≥18px bold or ≥24px): minimum 3:1\n     - UI components and graphical objects: minimum 3:1\n   - Report failures with the specific pairing, current ratio, and minimum required.\n   - Use AskUserQuestion to resolve failures: adjust the color, accept the risk, or mark as decorative-only.\n\n5. **Draft DESIGN.md**\n   - Follow the Google Labs Stitch format. The file has two parts:\n\n   **Part 1 — YAML frontmatter** with machine-readable tokens:\n   ```yaml\n   ---\n   version: \"1.0\"\n   name: \"Project Design System\"\n   colors:\n     primary: \"#1A1C1E\"\n     on-primary: \"#FFFFFF\"\n     secondary: \"#4A6741\"\n     surface: \"#FAFAFA\"\n     background: \"#FFFFFF\"\n     error: \"#BA1A1A\"\n     border: \"#E0E0E0\"\n   typography:\n     h1:\n       fontFamily: \"Inter\"\n       fontSize: \"2.25rem\"\n       fontWeight: 700\n       lineHeight: 1.2\n     body:\n       fontFamily: \"Inter\"\n       fontSize: \"1rem\"\n       fontWeight: 400\n       lineHeight: 1.5\n   spacing:\n     xs: \"4px\"\n     sm: \"8px\"\n     md: \"16px\"\n     lg: \"24px\"\n     xl: \"32px\"\n   rounded:\n     sm: \"4px\"\n     md: \"8px\"\n     lg: \"16px\"\n     full: \"9999px\"\n   elevation:\n     sm: \"0 1px 2px rgba(0,0,0,0.05)\"\n     md: \"0 4px 6px rgba(0,0,0,0.1)\"\n     lg: \"0 10px 15px rgba(0,0,0,0.1)\"\n   components:\n     button:\n       backgroundColor: \"{colors.primary}\"\n       textColor: \"{colors.on-primary}\"\n       rounded: \"{rounded.md}\"\n       paddingX: \"{spacing.lg}\"\n       paddingY: \"{spacing.sm}\"\n     card:\n       backgroundColor: \"{colors.surface}\"\n       border: \"1px solid {colors.border}\"\n       rounded: \"{rounded.lg}\"\n       padding: \"{spacing.lg}\"\n       shadow: \"{elevation.sm}\"\n   ---\n   ```\n\n   **Part 2 — Prose sections** (all optional, must appear in this order if present):\n\n   Each prose section must be written as a Markdown heading, not a bold paragraph label. Use `## Overview`, `## Colors`, `## Typography`, and the other section names below exactly when present.\n\n   1. `## Overview` — brand identity, visual tone, and design philosophy.\n   2. `## Colors` — palette rationale, dark mode strategy, semantic color usage.\n   3. `## Typography` — type scale rationale, heading hierarchy, body text rules.\n   4. `## Layout & Spacing` — grid strategy, spacing scale rationale, container max-widths, content density.\n   5. `## Elevation & Depth` — shadow usage, layering rules, z-index strategy.\n   6. `## Shapes` — corner radius philosophy, form language.\n   7. `## Components` — styling guidance for UI atoms including state variants (hover, active, disabled, focus). Reference tokens using `{token.path}` syntax.\n   8. `## Do's and Don'ts` — concrete guardrails. Include at least: colors to never use, spacing anti-patterns, component misuse patterns observed in prior implementations.\n\n   - Use `{colors.primary}` cross-reference syntax in component definitions and prose.\n   - Present the draft to the user via AskUserQuestion before writing.\n\n6. **Write deliverables**\n   - Write `DESIGN.md` to the project root.\n   - If `--update`: archive the previous version to `docs\u002Fhistory\u002Farchive\u002FYYYY-MM-DD\u002FHHMMSS\u002FDESIGN.md` first.\n\n## Deliverables\n\n- `DESIGN.md` in the project root — the single source of truth for visual identity, consumed by both Claude Code and Codex.\n- Interview log written to `design-system-interview.md` in the project root.\n\n## Constraints\n\n- Do not invent token values. Every value must come from the spec, codebase scan, or explicit user confirmation.\n- Do not skip the accessibility check. Report all contrast failures even if the user is likely to accept them.\n- Do not include tokens for features that don't exist yet — scope to the current spec or codebase.\n- Keep the YAML frontmatter machine-readable. No comments in YAML. Put rationale in prose sections.\n- Token cross-references use curly braces: `{colors.primary}`, `{spacing.md}`, `{rounded.lg}`.\n- When recommending a skill from another pack, verify the pack is installed via `.agents\u002Fproject.json` `enabled_packs`. If not installed, recommend `npx skillpacks install \u003Cpack-name>` from the project shell, before the target skill.\n- When updating an existing DESIGN.md, preserve token names and values that haven't changed. Only modify tokens that the new spec explicitly changes.\n\n## Alignment Page\n\nWhen this skill produces durable deliverables (research, specs, plans, reports, prototypes, or any document output), build a full-depth HTML alignment page following `ALIGNMENT-PAGE.md` in this skill's directory. Output: `alignment\u002Fdesign-system-{topic}.html`.\n\n## Default Shipping Contract\n\nFollow the shared shipping contract convention in CLAUDE.md.\n","# Design System\n\nInvoke as `\u002Fdesign-system`.\n\nUse this skill after `\u002Fconsolidate-prototypes` to lock design decisions into machine-readable tokens before implementation begins. It bridges the gap between prose UI specs and code — without it, agents interpret \"dark surface with primary accent\" differently each session, causing UI consistency drift.\n\nAlso use this skill retroactively on an existing codebase (`--scan`) to generate a DESIGN.md from tokens already in use.\n\n## Modes\n\n- **Default**: reads `specs\u002Fui-final-*.md` or `prototypes\u002F*\u002Fconsolidated\u002F` (or a user-provided spec path) and extracts tokens.\n- **`--scan`**: scans the codebase for CSS custom properties, Tailwind config, theme files, and component patterns to reverse-engineer a DESIGN.md.\n- **`--update`**: reads an existing `DESIGN.md` alongside new spec changes and produces an updated version.\n\n## Process\n\n1. **Resolve context**\n   - Read `.agents\u002Fproject.json`, `README.md`, `AGENTS.md`, `CLAUDE.md` when present.\n   - Locate the input source:\n     - Default: find `specs\u002Fui-final-*.md` or accept a path argument.\n     - `--scan`: find `tailwind.config.*`, `globals.css`, CSS custom property files, theme files, component directories, and any existing design token files.\n     - `--update`: read the existing `DESIGN.md` and the changed spec or codebase files.\n   - If no input can be found, ask the user to point to the source.\n\n2. **Extract raw tokens**\n   - From spec: pull every concrete visual decision — colors (hex, HSL, OKLCH), font families, font sizes, weights, line heights, spacing values, border radii, shadows, elevation layers, and component-level styling.\n   - From codebase (`--scan`): parse Tailwind config extends, CSS custom properties, repeated Tailwind classes, theme provider values, and component prop defaults. Deduplicate and group by semantic role.\n   - Normalize all colors to hex. Record OKLCH or HSL originals as comments when present.\n   - Identify semantic roles: primary, secondary, accent, surface, background, on-primary, on-surface, error, warning, success, info, border, muted.\n\n3. **Interview to confirm tokens**\n   - Present the extracted token inventory grouped by category (Colors, Typography, Spacing, Shapes, Elevation, Components).\n   - For each category, use AskUserQuestion (1–3 questions per turn):\n     - Are these the correct values? Flag any that look like defaults vs intentional choices.\n     - Are there missing semantic roles? (e.g., no error color found, no hover state defined)\n     - For typography: confirm the scale — is this intentional or inherited from a framework default?\n     - For spacing: confirm the scale — 4px base? 8px base? Irregular?\n   - Record user confirmations and adjustments.\n\n4. **Validate accessibility**\n   - Check WCAG 2.1 AA contrast ratios for all foreground\u002Fbackground color pairings:\n     - Normal text: minimum 4.5:1\n     - Large text (≥18px bold or ≥24px): minimum 3:1\n     - UI components and graphical objects: minimum 3:1\n   - Report failures with the specific pairing, current ratio, and minimum required.\n   - Use AskUserQuestion to resolve failures: adjust the color, accept the risk, or mark as decorative-only.\n\n5. **Draft DESIGN.md**\n   - Follow the Google Labs Stitch format. The file has two parts:\n\n   **Part 1 — YAML frontmatter** with machine-readable tokens:\n   ```yaml\n   ---\n   version: \"1.0\"\n   name: \"Project Design System\"\n   colors:\n     primary: \"#1A1C1E\"\n     on-primary: \"#FFFFFF\"\n     secondary: \"#4A6741\"\n     surface: \"#FAFAFA\"\n     background: \"#FFFFFF\"\n     error: \"#BA1A1A\"\n     border: \"#E0E0E0\"\n   typography:\n     h1:\n       fontFamily: \"Inter\"\n       fontSize: \"2.25rem\"\n       fontWeight: 700\n       lineHeight: 1.2\n     body:\n       fontFamily: \"Inter\"\n       fontSize: \"1rem\"\n       fontWeight: 400\n       lineHeight: 1.5\n   spacing:\n     xs: \"4px\"\n     sm: \"8px\"\n     md: \"16px\"\n     lg: \"24px\"\n     xl: \"32px\"\n   rounded:\n     sm: \"4px\"\n     md: \"8px\"\n     lg: \"16px\"\n     full: \"9999px\"\n   elevation:\n     sm: \"0 1px 2px rgba(0,0,0,0.05)\"\n     md: \"0 4px 6px rgba(0,0,0,0.1)\"\n     lg: \"0 10px 15px rgba(0,0,0,0.1)\"\n   components:\n     button:\n       backgroundColor: \"{colors.primary}\"\n       textColor: \"{colors.on-primary}\"\n       rounded: \"{rounded.md}\"\n       paddingX: \"{spacing.lg}\"\n       paddingY: \"{spacing.sm}\"\n     card:\n       backgroundColor: \"{colors.surface}\"\n       border: \"1px solid {colors.border}\"\n       rounded: \"{rounded.lg}\"\n       padding: \"{spacing.lg}\"\n       shadow: \"{elevation.sm}\"\n   ---\n   ```\n\n   **Part 2 — Prose sections** (all optional, must appear in this order if present):\n\n   Each prose section must be written as a Markdown heading, not a bold paragraph label. Use `## Overview`, `## Colors`, `## Typography`, and the other section names below exactly when present.\n\n   1. `## Overview` — brand identity, visual tone, and design philosophy.\n   2. `## Colors` — palette rationale, dark mode strategy, semantic color usage.\n   3. `## Typography` — type scale rationale, heading hierarchy, body text rules.\n   4. `## Layout & Spacing` — grid strategy, spacing scale rationale, container max-widths, content density.\n   5. `## Elevation & Depth` — shadow usage, layering rules, z-index strategy.\n   6. `## Shapes` — corner radius philosophy, form language.\n   7. `## Components` — styling guidance for UI atoms including state variants (hover, active, disabled, focus). Reference tokens using `{token.path}` syntax.\n   8. `## Do's and Don'ts` — concrete guardrails. Include at least: colors to never use, spacing anti-patterns, component misuse patterns observed in prior implementations.\n\n   - Use `{colors.primary}` cross-reference syntax in component definitions and prose.\n   - Present the draft to the user via AskUserQuestion before writing.\n\n6. **Write deliverables**\n   - Write `DESIGN.md` to the project root.\n   - If `--update`: archive the previous version to `docs\u002Fhistory\u002Farchive\u002FYYYY-MM-DD\u002FHHMMSS\u002FDESIGN.md` first.\n\n## Deliverables\n\n- `DESIGN.md` in the project root — the single source of truth for visual identity, consumed by both Claude Code and Codex.\n- Interview log written to `design-system-interview.md` in the project root.\n\n## Constraints\n\n- Do not invent token values. Every value must come from the spec, codebase scan, or explicit user confirmation.\n- Do not skip the accessibility check. Report all contrast failures even if the user is likely to accept them.\n- Do not include tokens for features that don't exist yet — scope to the current spec or codebase.\n- Keep the YAML frontmatter machine-readable. No comments in YAML. Put rationale in prose sections.\n- Token cross-references use curly braces: `{colors.primary}`, `{spacing.md}`, `{rounded.lg}`.\n- When recommending a skill from another pack, verify the pack is installed via `.agents\u002Fproject.json` `enabled_packs`. If not installed, recommend `npx skillpacks install \u003Cpack-name>` from the project shell, before the target skill.\n- When updating an existing DESIGN.md, preserve token names and values that haven't changed. Only modify tokens that the new spec explicitly changes.\n\n## Alignment Page\n\nWhen this skill produces durable deliverables (research, specs, plans, reports, prototypes, or any document output), build a full-depth HTML alignment page following `ALIGNMENT-PAGE.md` in this skill's directory. Output: `alignment\u002Fdesign-system-{topic}.html`.\n\n## Default Shipping Contract\n\nFollow the shared shipping contract convention in CLAUDE.md.\n",{"name":5,"type":44,"version":54,"description":7,"visual_tier":46,"argument-hint":55,"required_conventions":56},"v0.3","[spec path | --scan | --update]",[57],"alignment-page","master","96e2912af886dd1606b1b97df707715aef062b02","packs\u002Fproduct-design\u002Fclaude\u002Fdesign-system\u002Farchive\u002Fv0.3",0,"https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills","https:\u002F\u002Fagentic-skills-blush.vercel.app","https:\u002F\u002Fgithub.com\u002FGeorgeQLe","georgeqle.com","George Le is a futurist and serial tech entrepreneur who wants to work toward a world where humanity is free from robotic tasks.","2026-11-10 04:07:24",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add GeorgeQLe\u002Fagentic-skills --skill design-system",{"tool":74,"command":75},"bunx","bunx skills add GeorgeQLe\u002Fagentic-skills --skill design-system",{"tool":77,"command":78},"pnpm","pnpm dlx skills add GeorgeQLe\u002Fagentic-skills --skill design-system","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fproduct-design\u002Fclaude\u002Fdesign-system\u002Farchive\u002Fv0.3\u002FSKILL.md",true,[],[83,96,106,118,131,142],{"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":89,"publishedAt":49},"01M6G0NJES15RJKZE6YZ0TSYGF","source-checkout-allowed","Valid source-checkout-only fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fsource-checkout-allowed\u002FSKILL.md",[],[90,91,92,93,94,95],"source checkout allowed","checkout","fixture","only","v0","valid",{"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":49},"01M6G0NFZ3R1MNB1E3DVTM0WB7","deck-install-valid","Valid deck install fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fdeck-install\u002FSKILL.md",[],[103,104,105,95,92,94],"deck install valid","deck","install",{"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":112,"publishedAt":49},"01M6G0ND3QZQC4MDZ9NVB97PT2","codex-pack-guard-valid","Valid Codex Pack Availability Guard fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fcodex-pack-guard\u002FSKILL.md",[],[113,114,115,95,116,117,92,94],"codex pack guard valid","pack","guard","codex","availability",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":127,"publishedAt":49},"01M6G0NA9YB3NKGZKD3S96JMNB","codex-missing-skill-valid","Valid Codex missing skill fallback fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fcodex-missing-skill-fallback\u002FSKILL.md",[124],{"categoryNo":125,"categoryName":126,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[128,129,95,116,94,130,92],"codex missing skill valid","missing","fallback",{"skillNo":132,"name":133,"nameZh":6,"description":134,"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":138,"publishedAt":49},"01M6G0N7PC0EKFD40ZWQAXSAQ9","codex-base-skill-fallback-valid","Valid Codex base skill fallback fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fcodex-base-skill-fallback\u002FSKILL.md",[137],{"categoryNo":125,"categoryName":126,"taxonomyType":21,"taxonomyTypeDesc":22},[95,116,130,139,140,141,94,92],"base skill","codex base skill fallback valid","base",{"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":148,"publishedAt":49},"01M6G0N4VRR2YKZQ6N3Y6S2BQA","claude-pack-guard-valid","Valid Claude Pack Availability Guard fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fclaude-pack-guard\u002FSKILL.md",[],[95,115,114,149,117,94,92],"claude pack guard valid"]