[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FWR5WCT8JJV5090481F4GV":3,"skill-same:01M6FWR5WCT8JJV5090481F4GV":55},{"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":18,"publishedAt":25,"linkOnly":26,"markdownContent":27,"markdownBody":28,"frontMatter":29,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":34,"repositoryHtmlUrl":35,"repositoryHomepageUrl":36,"ownerHtmlUrl":37,"ownerBlogUrl":38,"ownerDescription":39,"updatedAt":40,"install":41,"resources":54},"01M6FWR5WCT8JJV5090481F4GV","sync",null,"Pull latest changes from remote and report status","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\u002Fgitops\u002Fcodex\u002Fsync\u002Farchive\u002Fv0.3\u002FSKILL.md",[],[5,19,20,21,22,23,24],"status","report","shipping","pull","v0","remote","2026-11-10 10:12:30",false,"---\nname: sync\ndescription: Pull latest changes from remote and report status\ntype: shipping\nversion: v0.3\n---\n\n# Sync\n\nInvoke as `$sync`.\n\nPull the latest changes from the remote repository and report status.\n\n## Workflow\n\n1. Check current state:\n   - Run `git status` to check for uncommitted changes.\n   - If there are uncommitted changes, stash them first, pull, then pop the stash. Warn the user about the stash.\n2. Pull from remote:\n   - Run `git pull --rebase origin \u003Ccurrent-branch>`.\n   - If rebase conflicts occur, abort the rebase, try `git pull --no-rebase` instead, and report any merge conflicts for the user to resolve.\n3. Check for outstanding work:\n   - Check if `tasks\u002Froadmap.md` exists for the full plan, and `tasks\u002Ftodo.md` for the current phase.\n   - If `tasks\u002Ftodo.md` exists, read it and look for unchecked items (`- [ ]`).\n   - If there are incomplete items, summarise: which phase is current, what the next step is, and how many steps\u002Fphases remain.\n   - If `tasks\u002Fmanual-todo.md` exists, count unchecked manual tasks and include in the summary.\n   - If `tasks\u002Frecord-todo.md` or `tasks\u002Frecurring-todo.md` exists, count unchecked advisory items and include those counts separately. Do not treat them as active plan steps.\n   - If all items are checked, report that the plan is complete.\n   - If neither file exists, note that there is no active plan.\n4. Check provisioned agent config:\n   - If `CLAUDE.md` or `AGENTS.md` contains `\u003C!-- provision-agentic-config vX.Y -->`, extract the version.\n   - Read the canonical `provision-agentic-config` skill from the first existing path in this order:\n     1. `~\u002F.codex\u002Fskills\u002Fprovision-agentic-config\u002FSKILL.md`\n     2. `~\u002F.claude\u002Fskills\u002Fprovision-agentic-config\u002FSKILL.md`\n     3. `global\u002Fcodex\u002Fprovision-agentic-config\u002FSKILL.md` in the current repo, when present\n     4. `global\u002Fclaude\u002Fprovision-agentic-config\u002FSKILL.md` in the current repo, when present\n   - Extract the `version:` field from the canonical skill's YAML frontmatter.\n   - Extract the canonical provisioned blocks from the same skill:\n     - `CLAUDE.md`: the fenced block under `Required Claude Block` or the section that says \"The Claude block to insert into `.\u002FCLAUDE.md`\".\n     - `AGENTS.md`: the fenced block under `Required AGENTS Block` or the section that says \"The AGENTS block to insert into `.\u002FAGENTS.md`\".\n   - Compare each existing project file against its corresponding canonical block after normalizing line endings and trimming only leading\u002Ftrailing whitespace around the block. Do not ignore changed bullets, headings, command examples, or policy text.\n   - If the installed skill version is newer than the provisioned version in either file, warn: `⚠ CLAUDE.md provisioned with vX.Y but provision-agentic-config is at vX.Y — consider re-running $provision-agentic-config`\n   - If the version comment is missing from `CLAUDE.md` or `AGENTS.md`, note: `ℹ No provision version found in CLAUDE.md\u002FAGENTS.md — run $provision-agentic-config to add version tracking`\n   - If a project file has the current version comment but the provisioned block content differs from the canonical block, warn: `⚠ CLAUDE.md provisioned block differs from the canonical provision-agentic-config vX.Y block — re-run $provision-agentic-config`\n   - If a canonical block cannot be extracted, fall back to the version-only check and note: `ℹ Could not extract canonical provision-agentic-config block; checked version comment only`\n   - If none of the canonical skill files exists, skip this check silently.\n   - Always report the local canonical source path used and its `version:` field when this check runs.\n5. Resolve GitHub freshness preference:\n   - Use the user-local machine-wide preference file at `~\u002F.agentic-skills\u002Fpreferences.json`.\n   - Read `sync.github_freshness_check`, whose only allowed values are `\"ask\"`, `\"always\"`, and `\"never\"`.\n   - If the file or key is missing, ask the user once which default to remember:\n     - Always check GitHub during sync\n     - Never check GitHub during sync\n     - Ask each time\n   - Create `~\u002F.agentic-skills\u002Fpreferences.json` if needed and save the selected value as:\n     ```json\n     {\n       \"sync\": {\n         \"github_freshness_check\": \"ask\"\n       }\n     }\n     ```\n   - If the value is `\"always\"`, check GitHub remote freshness automatically.\n   - If the value is `\"never\"`, skip GitHub freshness checks and report that local canonical `provision-agentic-config` was used without a GitHub check.\n   - If the value is `\"ask\"`, ask before checking GitHub for this sync.\n   - Treat malformed JSON or an unsupported value as missing preference and ask again before writing one of the allowed values.\n6. Optional GitHub freshness check:\n   - Only run this check when the resolved preference or explicit user approval says to check GitHub.\n   - Compare the local `agentic-skills` checkout against `origin\u002FHEAD` using non-mutating commands such as `git remote get-url origin`, `git rev-parse HEAD`, `git rev-parse origin\u002FHEAD`, and, when remote freshness is explicitly enabled, `git fetch --dry-run` or an equivalent non-mutating freshness probe.\n   - Report the local checkout commit, remote URL, local `origin\u002FHEAD` commit if available, and whether the local checkout appears behind the remote.\n   - Do not pull, fast-forward, rebase, install, or mutate the checkout from plain `$sync`.\n   - If a GitHub check shows the local checkout is stale, recommend `$init-agentic-skills update` for an explicit update.\n7. Report status:\n   - Branch name\n   - Commits pulled (if any) — show short log of new commits\n   - Whether stashed changes were re-applied\n   - Any conflicts that need manual resolution\n   - Current `git status`\n   - **Agent config drift** — provisioning version, local canonical source path\u002Fversion, and canonical block match\u002Fdrift status for `CLAUDE.md` and `AGENTS.md`, if checked\n   - **GitHub freshness** — preference value, whether GitHub was checked, and the local checkout\u002Fremote status; when skipped, say local canonical was used\n   - **Outstanding work** — summary from step 3 (next step, current phase, remaining work, pending manual tasks) or \"No active plan\"\n   - **Advisory tasks** — pending record\u002Frecurring counts, if those files exist\n8. Post-sync actions:\n   a) Check if `sync.md` exists at the project root.\n   b) **If `sync.md` exists** — parse and execute it:\n      - Read `sync.md` and identify sections by H2 headings.\n      - **Dependencies** (aliases: \"Deps\", \"Dependency Management\"): Execute shell commands in fenced code blocks. Report output briefly.\n      - **Conflict Resolution** (aliases: \"Conflicts\"): If the pull introduced merge conflicts (from step 2), apply the guidance in this section. If no conflicts, skip silently.\n      - **Custom** (aliases: \"Project-Specific\", \"Scripts\", \"Setup\"): Execute shell commands in fenced code blocks in order. Report output briefly.\n      - **Notifications** (aliases: \"Awareness\", \"Alerts\", \"Watch\"): For each bullet, check if the mentioned file\u002Fdirectory was modified in pulled commits (`git diff --name-only` against pre-pull HEAD). If any match, print a prominent alert.\n      - Unrecognised headings: skip with a note.\n      - Report a summary of all post-sync actions taken.\n   c) **If `sync.md` does not exist** — suggest creating one:\n      - Analyse the project to detect: package manager (look for lockfiles), common scripts (package.json, Makefile, Justfile), config templates (.env.example, docker-compose.yml).\n      - Present a suggested `sync.md` following the format below.\n      - Ask: \"Would you like me to create this `sync.md`?\"\n      - **Only create the file if the user approves.**\n\n## sync.md format\n\nThe `sync.md` file lives at the project root. H2 sections are categories. Shell commands go in fenced code blocks; prose guidance goes in bullet points.\n\n```markdown\n# Post-Sync Actions\n\n## Dependencies\n\n```sh\nnpm install\n```\n\n## Conflict Resolution\n\n- Always accept theirs for `package-lock.json`\n\n## Custom\n\n```sh\nnpm run codegen\n```\n\n## Notifications\n\n- `.env.example` — check for new environment variables\n- `CLAUDE.md` — review if project conventions were updated\n```\n\n## Constraints\n\n- Do not force-push or rewrite history.\n- Do not auto-resolve merge conflicts — report them and let the user decide. However, if `sync.md` has a Conflict Resolution section, follow its guidance for the specific files\u002Fpatterns it covers.\n- If stash pop fails due to conflicts, leave the stash intact and report it.\n- Post-sync commands from `sync.md` run in the project root directory.\n- If any post-sync command fails, report the error and continue with remaining actions.\n- Never auto-create `sync.md` without explicit user approval.\n- Do not execute commented-out sections (`\u003C!-- ... -->`).\n- Plain `$sync` must not update the `agentic-skills` checkout, pull from GitHub for the local canonical source, or reinstall skills. Only `$init-agentic-skills update` \u002F `$init-agentic-skills latest` may perform that explicit update flow after confirmation.\n\n\n## Default Shipping Contract\n\nFollow the shared shipping contract convention in CLAUDE.md.\n","# Sync\n\nInvoke as `$sync`.\n\nPull the latest changes from the remote repository and report status.\n\n## Workflow\n\n1. Check current state:\n   - Run `git status` to check for uncommitted changes.\n   - If there are uncommitted changes, stash them first, pull, then pop the stash. Warn the user about the stash.\n2. Pull from remote:\n   - Run `git pull --rebase origin \u003Ccurrent-branch>`.\n   - If rebase conflicts occur, abort the rebase, try `git pull --no-rebase` instead, and report any merge conflicts for the user to resolve.\n3. Check for outstanding work:\n   - Check if `tasks\u002Froadmap.md` exists for the full plan, and `tasks\u002Ftodo.md` for the current phase.\n   - If `tasks\u002Ftodo.md` exists, read it and look for unchecked items (`- [ ]`).\n   - If there are incomplete items, summarise: which phase is current, what the next step is, and how many steps\u002Fphases remain.\n   - If `tasks\u002Fmanual-todo.md` exists, count unchecked manual tasks and include in the summary.\n   - If `tasks\u002Frecord-todo.md` or `tasks\u002Frecurring-todo.md` exists, count unchecked advisory items and include those counts separately. Do not treat them as active plan steps.\n   - If all items are checked, report that the plan is complete.\n   - If neither file exists, note that there is no active plan.\n4. Check provisioned agent config:\n   - If `CLAUDE.md` or `AGENTS.md` contains `\u003C!-- provision-agentic-config vX.Y -->`, extract the version.\n   - Read the canonical `provision-agentic-config` skill from the first existing path in this order:\n     1. `~\u002F.codex\u002Fskills\u002Fprovision-agentic-config\u002FSKILL.md`\n     2. `~\u002F.claude\u002Fskills\u002Fprovision-agentic-config\u002FSKILL.md`\n     3. `global\u002Fcodex\u002Fprovision-agentic-config\u002FSKILL.md` in the current repo, when present\n     4. `global\u002Fclaude\u002Fprovision-agentic-config\u002FSKILL.md` in the current repo, when present\n   - Extract the `version:` field from the canonical skill's YAML frontmatter.\n   - Extract the canonical provisioned blocks from the same skill:\n     - `CLAUDE.md`: the fenced block under `Required Claude Block` or the section that says \"The Claude block to insert into `.\u002FCLAUDE.md`\".\n     - `AGENTS.md`: the fenced block under `Required AGENTS Block` or the section that says \"The AGENTS block to insert into `.\u002FAGENTS.md`\".\n   - Compare each existing project file against its corresponding canonical block after normalizing line endings and trimming only leading\u002Ftrailing whitespace around the block. Do not ignore changed bullets, headings, command examples, or policy text.\n   - If the installed skill version is newer than the provisioned version in either file, warn: `⚠ CLAUDE.md provisioned with vX.Y but provision-agentic-config is at vX.Y — consider re-running $provision-agentic-config`\n   - If the version comment is missing from `CLAUDE.md` or `AGENTS.md`, note: `ℹ No provision version found in CLAUDE.md\u002FAGENTS.md — run $provision-agentic-config to add version tracking`\n   - If a project file has the current version comment but the provisioned block content differs from the canonical block, warn: `⚠ CLAUDE.md provisioned block differs from the canonical provision-agentic-config vX.Y block — re-run $provision-agentic-config`\n   - If a canonical block cannot be extracted, fall back to the version-only check and note: `ℹ Could not extract canonical provision-agentic-config block; checked version comment only`\n   - If none of the canonical skill files exists, skip this check silently.\n   - Always report the local canonical source path used and its `version:` field when this check runs.\n5. Resolve GitHub freshness preference:\n   - Use the user-local machine-wide preference file at `~\u002F.agentic-skills\u002Fpreferences.json`.\n   - Read `sync.github_freshness_check`, whose only allowed values are `\"ask\"`, `\"always\"`, and `\"never\"`.\n   - If the file or key is missing, ask the user once which default to remember:\n     - Always check GitHub during sync\n     - Never check GitHub during sync\n     - Ask each time\n   - Create `~\u002F.agentic-skills\u002Fpreferences.json` if needed and save the selected value as:\n     ```json\n     {\n       \"sync\": {\n         \"github_freshness_check\": \"ask\"\n       }\n     }\n     ```\n   - If the value is `\"always\"`, check GitHub remote freshness automatically.\n   - If the value is `\"never\"`, skip GitHub freshness checks and report that local canonical `provision-agentic-config` was used without a GitHub check.\n   - If the value is `\"ask\"`, ask before checking GitHub for this sync.\n   - Treat malformed JSON or an unsupported value as missing preference and ask again before writing one of the allowed values.\n6. Optional GitHub freshness check:\n   - Only run this check when the resolved preference or explicit user approval says to check GitHub.\n   - Compare the local `agentic-skills` checkout against `origin\u002FHEAD` using non-mutating commands such as `git remote get-url origin`, `git rev-parse HEAD`, `git rev-parse origin\u002FHEAD`, and, when remote freshness is explicitly enabled, `git fetch --dry-run` or an equivalent non-mutating freshness probe.\n   - Report the local checkout commit, remote URL, local `origin\u002FHEAD` commit if available, and whether the local checkout appears behind the remote.\n   - Do not pull, fast-forward, rebase, install, or mutate the checkout from plain `$sync`.\n   - If a GitHub check shows the local checkout is stale, recommend `$init-agentic-skills update` for an explicit update.\n7. Report status:\n   - Branch name\n   - Commits pulled (if any) — show short log of new commits\n   - Whether stashed changes were re-applied\n   - Any conflicts that need manual resolution\n   - Current `git status`\n   - **Agent config drift** — provisioning version, local canonical source path\u002Fversion, and canonical block match\u002Fdrift status for `CLAUDE.md` and `AGENTS.md`, if checked\n   - **GitHub freshness** — preference value, whether GitHub was checked, and the local checkout\u002Fremote status; when skipped, say local canonical was used\n   - **Outstanding work** — summary from step 3 (next step, current phase, remaining work, pending manual tasks) or \"No active plan\"\n   - **Advisory tasks** — pending record\u002Frecurring counts, if those files exist\n8. Post-sync actions:\n   a) Check if `sync.md` exists at the project root.\n   b) **If `sync.md` exists** — parse and execute it:\n      - Read `sync.md` and identify sections by H2 headings.\n      - **Dependencies** (aliases: \"Deps\", \"Dependency Management\"): Execute shell commands in fenced code blocks. Report output briefly.\n      - **Conflict Resolution** (aliases: \"Conflicts\"): If the pull introduced merge conflicts (from step 2), apply the guidance in this section. If no conflicts, skip silently.\n      - **Custom** (aliases: \"Project-Specific\", \"Scripts\", \"Setup\"): Execute shell commands in fenced code blocks in order. Report output briefly.\n      - **Notifications** (aliases: \"Awareness\", \"Alerts\", \"Watch\"): For each bullet, check if the mentioned file\u002Fdirectory was modified in pulled commits (`git diff --name-only` against pre-pull HEAD). If any match, print a prominent alert.\n      - Unrecognised headings: skip with a note.\n      - Report a summary of all post-sync actions taken.\n   c) **If `sync.md` does not exist** — suggest creating one:\n      - Analyse the project to detect: package manager (look for lockfiles), common scripts (package.json, Makefile, Justfile), config templates (.env.example, docker-compose.yml).\n      - Present a suggested `sync.md` following the format below.\n      - Ask: \"Would you like me to create this `sync.md`?\"\n      - **Only create the file if the user approves.**\n\n## sync.md format\n\nThe `sync.md` file lives at the project root. H2 sections are categories. Shell commands go in fenced code blocks; prose guidance goes in bullet points.\n\n```markdown\n# Post-Sync Actions\n\n## Dependencies\n\n```sh\nnpm install\n```\n\n## Conflict Resolution\n\n- Always accept theirs for `package-lock.json`\n\n## Custom\n\n```sh\nnpm run codegen\n```\n\n## Notifications\n\n- `.env.example` — check for new environment variables\n- `CLAUDE.md` — review if project conventions were updated\n```\n\n## Constraints\n\n- Do not force-push or rewrite history.\n- Do not auto-resolve merge conflicts — report them and let the user decide. However, if `sync.md` has a Conflict Resolution section, follow its guidance for the specific files\u002Fpatterns it covers.\n- If stash pop fails due to conflicts, leave the stash intact and report it.\n- Post-sync commands from `sync.md` run in the project root directory.\n- If any post-sync command fails, report the error and continue with remaining actions.\n- Never auto-create `sync.md` without explicit user approval.\n- Do not execute commented-out sections (`\u003C!-- ... -->`).\n- Plain `$sync` must not update the `agentic-skills` checkout, pull from GitHub for the local canonical source, or reinstall skills. Only `$init-agentic-skills update` \u002F `$init-agentic-skills latest` may perform that explicit update flow after confirmation.\n\n\n## Default Shipping Contract\n\nFollow the shared shipping contract convention in CLAUDE.md.\n",{"name":5,"type":21,"version":30,"description":7},"v0.3","master","96e2912af886dd1606b1b97df707715aef062b02","packs\u002Fgitops\u002Fcodex\u002Fsync\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":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add GeorgeQLe\u002Fagentic-skills --skill sync",{"tool":47,"command":48},"bunx","bunx skills add GeorgeQLe\u002Fagentic-skills --skill sync",{"tool":50,"command":51},"pnpm","pnpm dlx skills add GeorgeQLe\u002Fagentic-skills --skill sync","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fgitops\u002Fcodex\u002Fsync\u002Farchive\u002Fv0.3\u002FSKILL.md",true,[],[56,68,78,90,105,116],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":25},"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",[],[63,64,65,66,23,67],"source checkout allowed","checkout","fixture","only","valid",{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":25},"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",[],[75,76,77,67,65,23],"deck install valid","deck","install",{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":25},"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",[],[85,86,87,67,88,89,65,23],"codex pack guard valid","pack","guard","codex","availability",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":101,"publishedAt":25},"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",[96],{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[102,103,67,88,23,104,65],"codex missing skill valid","missing","fallback",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":112,"publishedAt":25},"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",[111],{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},[67,88,104,113,114,115,23,65],"base skill","codex base skill fallback valid","base",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":25},"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",[],[67,87,86,123,89,23,65],"claude pack guard valid"]