[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FZG68B8T0EQQKM53ZARTJS":3,"skill-same:01M6FZG68B8T0EQQKM53ZARTJS":65},{"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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M6FZG68B8T0EQQKM53ZARTJS","session-triage",null,"Investigate one immediate session, correction, repo incident, or skill failure and recommend a verified fix","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\u002Fsession-analytics\u002Fcodex\u002Fsession-triage\u002Farchive\u002Fv0.7\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"triage","session","session triage","file","analysis","investigate","skill name","text","repo","fix","v0","issue","incident","id","name","2026-11-10 10:12:30",false,"---\nname: session-triage\ndescription: Investigate one immediate session, correction, repo incident, or skill failure and recommend a verified fix\ntype: analysis\nversion: v0.7\nargument-hint: \"[session id\u002Ffile, repo path, skill name\u002Fpath, correction text, or issue description]\"\n---\n\n# Session Triage\n\nInvoke as `$session-triage`.\n\nUse this skill when the user wants a focused investigation of one immediate issue: a current conversation problem, one correction, one session, one repo incident, one failed run, or one suspected skill failure. This skill verifies what happened before recommending a durable fix.\n\nUse `$analyze-sessions` instead for informational history questions — single or trend — such as broad cross-session breakdowns, recurring frustration analysis, performance over time, repeated prompt patterns, automation opportunities, finding a past conversation, or checking one run's token spend. This skill owns live incidents that need a verified fix.\n\n## Inputs\n\n- Active conversation context.\n- Optional session ID, session file, or exported log.\n- Optional repository path or current working directory.\n- Optional skill name or `SKILL.md` path.\n- Optional user correction text, error output, test failure, log excerpt, file path, commit, or issue description.\n- Optional `benchmark regression` mode: invoked as `$session-triage \u003Cskill> benchmark regression` by `$benchmark-test-skill` when `agentic-skills-benchmarks\u002Fscripts\u002Fbenchmark-regression-check.mjs` reports a `regression` verdict. The prior-vs-new delta block (passRate, Wilson lower bound, output-quality, status badge, prior and new grade dates) is carried in as evidence; the appended grade rows live in `agentic-skills-benchmarks\u002Fbenchmark\u002Fgrade-history.json`.\n\n## Process\n\n1. Define the investigation scope:\n   - Treat the current conversation and current working directory as the default scope.\n   - Prefer user-provided session IDs, files, repo paths, skill names, exact correction phrases, errors, logs, and test failures over broad history searches.\n   - Resolve named skills from `base\u002Fcodex`, `base\u002Fclaude`, `packs`, project-local `.agents`, `.codex`, `.claude`, and installed `~\u002F.codex\u002Fskills` or `~\u002F.claude\u002Fskills` as read-only fallback evidence.\n   - Do not create an `$analyze-session` alias or route; use this distinct command name to avoid singular\u002Fplural confusion.\n\n2. Gather narrow evidence first:\n   - Read the target skill contract when a skill is named.\n   - Read directly relevant project instructions such as `AGENTS.md`, `CLAUDE.md`, task docs, pack docs, logs, or test output.\n   - Search only the scoped repo\u002Fsession\u002Fhistory for the issue text, skill name, invocation command, relevant file paths, user correction, and nearby agent actions.\n   - Include the active conversation as evidence when the correction is happening now.\n   - Broaden to `$analyze-sessions` only when recurrence, frequency, or trend evidence is needed.\n\n3. Verify the issue before diagnosing:\n   - Separate the **user-identified issue** from the **agent-verified issue**.\n   - Classify the verification verdict as `verified`, `partially verified`, `not verified`, or `inconclusive`.\n   - A verified issue requires evidence for what the agent did, what the skill\u002Frepo\u002Fuser contract required, and why the outcome was wrong or risky.\n   - If evidence shows the skill contract was adequate and the agent ignored it, say that directly.\n\n4. Build a concise timeline:\n   - User request or trigger.\n   - Skill or instruction that should have applied.\n   - Agent action or omission.\n   - Failure, correction, or observed impact.\n   - Relevant repo\u002Fsession state.\n\n5. Diagnose root cause:\n   - Identify whether the cause is a missing trigger, ambiguous trigger, missing evidence gate, insufficient scope resolution, weak output contract, bad next-step routing, missing validation, missing safety constraint, stale mirrored contract, repo instruction conflict, or agent noncompliance with an adequate contract.\n   - Compare Claude and Codex skill versions when both exist and flag mirrored drift.\n   - Check `tasks\u002Flessons.md` when working in `agentic-skills`; reuse existing lessons or recommend a new lesson when the pattern is novel.\n   - For benchmark failures, check recent same-skill `agentic-skills-benchmarks\u002Fbenchmark\u002Ftriage-\u003Cskill>-*.md` reports and `tasks\u002Flessons.md` before recommending a narrow tolerance patch. If two or more recent reports classify the same family of valid outputs as benchmark false negatives, stop patching individual phrasings and route to a generalized rubric, semantic evaluator, fixture-family, or infrastructure-classifier fix that covers the family.\n   - For a `benchmark regression` invocation, the absolute thresholds may still pass — the issue is a *drop relative to the prior grade*. Use the carried delta and `agentic-skills-benchmarks\u002Fbenchmark\u002Fgrade-history.json` to confirm the regression is real (not a one-run sampling artifact: small evaluated-run counts and wide Wilson intervals can move >=10pp by chance — say so and recommend a confirming re-run when the sample is thin). Then classify the cause:\n     - **Real behavioral regression** — the skill contract or a dependency changed and the agent now produces worse output. Route the fix to `$targeted-skill-builder \u003Cskill> benchmark regression` naming the contract section that drifted, and confirm the loop closes by re-running `$benchmark-test-skill \u003Cskill>` to verify the grade recovers in `grade-history.json`.\n     - **Harness \u002F rubric drift** — the skill behavior is unchanged but a setup, fixture, evaluator, or pricing\u002Fthreshold change moved the score. Reuse the false-negative-family logic above (steps 5-6): name the owning harness\u002Fsetup file and the family-level behavior to recognize, rather than patching one phrasing.\n\n6. Recommend the smallest durable fix:\n   - Name exact skill file(s), instruction file(s), or docs to change.\n   - Provide concrete rule text or workflow-step wording when a skill-contract change is justified.\n   - Include validation checks that prove the revised behavior prevents the issue, such as targeted `rg` checks, mirrored contract checks, version checks, replay of the decision path, or the failing test\u002Flog command.\n   - For repeated benchmark false-negative families, the recommended fix must name the owning harness or setup file, the family-level behavior to recognize or reject, positive and negative fixture shapes to add, and a validation command such as focused layer1 setup tests plus `pnpm --dir tests verify --skill \u003Cskill>`.\n   - Route verified skill changes to `$targeted-skill-builder` (skill-dev pack) for a narrow update or `$create-agentic-skill` (skill-dev pack) for a new repo-managed skill.\n\n7. Optionally enrich the persistent insights memory (secondary writer):\n   - When the triaged incident is a verified, generalizable pattern (not a pure one-off), append it to the machine-local `.session-insights\u002Finsights.md` store that `$analyze-sessions` accumulates, so live incidents and cross-session trends share one memory.\n   - The store is gitignored and may not exist yet; create it with the standard keyed table header (`| Insight | Category | First Seen | Last Seen | Occurrences | Status |`) if absent. If a semantically matching row already exists, increment its Occurrences and advance Last Seen instead of adding a duplicate; otherwise add a row with Occurrences `1` and Status `confirmed` (triage incidents are verified).\n   - This is additive memory only — `tasks\u002Flessons.md` remains the authoritative correction log; do not move lessons content into the insights store.\n\n## Pack Availability Guard\n\nBefore recommending another skill, verify the target skill itself is available before relying on pack availability:\n\n- Treat `.agents\u002Fproject.json` `enabled_skills.\u003Cskill-name>` as direct availability, even when the provider pack is not listed in `enabled_packs`.\n- Treat `.agents\u002Fproject.json` `enabled_packs` as availability only when the enabled pack provides the target skill; use `scripts\u002Fpack.sh which \u003Cskill-name>` when available to identify the provider.\n- Treat local or global skill files as direct availability evidence, including `.codex\u002Fskills\u002F\u003Cskill-name>\u002FSKILL.md`, `.claude\u002Fskills\u002F\u003Cskill-name>\u002FSKILL.md`, `~\u002F.codex\u002Fskills\u002F\u003Cskill-name>\u002FSKILL.md`, and `~\u002F.claude\u002Fskills\u002F\u003Cskill-name>\u002FSKILL.md`.\n\nIf the target skill is unavailable, recommend `npx skillpacks install \u003Cpack-or-skill>` from the project shell before the skill invocation. Prefer the provider pack when it is known; otherwise recommend installing the target skill by name. Tell Codex users to start a fresh Codex CLI session if the `$` skill list remains stale after install.\n\nFor benchmark regression loop-closing, treat `$benchmark-test-skill` as owned by `agentic-skills-bench`: check whether `.agents\u002Fproject.json` `enabled_packs` includes `agentic-skills-bench` before recommending or relying on `$benchmark-test-skill \u003Cskill>`. If `agentic-skills-bench` is not enabled, recommend `npx skillpacks install agentic-skills-bench` from the project shell first, then tell Codex users to start a fresh Codex CLI session if the `$` skill list remains stale after install.\n\n## Output\n\nProduce a structured report with:\n\n- Target: session\u002Frepo\u002Fskill scope and evidence sources.\n- User-identified issue: the user's claim in concise terms.\n- Verification verdict: `verified`, `partially verified`, `not verified`, or `inconclusive`, with supporting evidence.\n- Timeline: short sequence from trigger to correction or impact.\n- Root cause: the specific contract gap, repo conflict, or agent noncompliance pattern.\n- Responsible contract gap: skill, project instruction, task doc, or none.\n- Recommended fix: exact file(s), section(s), and proposed wording or behavior change.\n- Validation plan: commands or checks to prove the fix.\n- Confidence and evidence gaps: what is known, what could not be verified, and whether `$analyze-sessions` is needed for recurrence analysis.\n- Recommended next skill: `$targeted-skill-builder` (skill-dev pack), `$create-agentic-skill` (skill-dev pack), `$analyze-sessions`, or `none` when no follow-up is justified. For a confirmed real `benchmark regression`, recommend `$targeted-skill-builder \u003Cskill> benchmark regression` and, after applying the Pack Availability Guard for `agentic-skills-bench`, name re-running `$benchmark-test-skill \u003Cskill>` as the loop-closing verification (see `docs\u002Fbenchmark-improvement-loop.md`).\n\n## Constraints\n\n- Start narrow and evidence-bound; do not scan all local history by default.\n- Do not claim a user-identified issue is agent-verified without independent evidence.\n- Do not modify the target skill during analysis unless the user also asked for implementation and the active workflow permits edits.\n- Do not recommend a skill change when the evidence points only to one-off agent noncompliance and the contract is already clear.\n- Do not create or suggest `$analyze-session`; use `$session-triage`.\n- Do not create or modify GitHub Actions workflows.\n- If a source is missing or unreadable, report that clearly and continue with available evidence instead of guessing.\n- When recommending another skill, apply the Pack Availability Guard: check `enabled_skills`, enabled provider packs, and local\u002Fglobal skill files before recommending the skill directly; if unavailable, prepend `npx skillpacks install \u003Cpack-or-skill>` to the recommendation.\n\n## Default Shipping Contract\n\nFollow the shared shipping contract convention in CLAUDE.md.\n","# Session Triage\n\nInvoke as `$session-triage`.\n\nUse this skill when the user wants a focused investigation of one immediate issue: a current conversation problem, one correction, one session, one repo incident, one failed run, or one suspected skill failure. This skill verifies what happened before recommending a durable fix.\n\nUse `$analyze-sessions` instead for informational history questions — single or trend — such as broad cross-session breakdowns, recurring frustration analysis, performance over time, repeated prompt patterns, automation opportunities, finding a past conversation, or checking one run's token spend. This skill owns live incidents that need a verified fix.\n\n## Inputs\n\n- Active conversation context.\n- Optional session ID, session file, or exported log.\n- Optional repository path or current working directory.\n- Optional skill name or `SKILL.md` path.\n- Optional user correction text, error output, test failure, log excerpt, file path, commit, or issue description.\n- Optional `benchmark regression` mode: invoked as `$session-triage \u003Cskill> benchmark regression` by `$benchmark-test-skill` when `agentic-skills-benchmarks\u002Fscripts\u002Fbenchmark-regression-check.mjs` reports a `regression` verdict. The prior-vs-new delta block (passRate, Wilson lower bound, output-quality, status badge, prior and new grade dates) is carried in as evidence; the appended grade rows live in `agentic-skills-benchmarks\u002Fbenchmark\u002Fgrade-history.json`.\n\n## Process\n\n1. Define the investigation scope:\n   - Treat the current conversation and current working directory as the default scope.\n   - Prefer user-provided session IDs, files, repo paths, skill names, exact correction phrases, errors, logs, and test failures over broad history searches.\n   - Resolve named skills from `base\u002Fcodex`, `base\u002Fclaude`, `packs`, project-local `.agents`, `.codex`, `.claude`, and installed `~\u002F.codex\u002Fskills` or `~\u002F.claude\u002Fskills` as read-only fallback evidence.\n   - Do not create an `$analyze-session` alias or route; use this distinct command name to avoid singular\u002Fplural confusion.\n\n2. Gather narrow evidence first:\n   - Read the target skill contract when a skill is named.\n   - Read directly relevant project instructions such as `AGENTS.md`, `CLAUDE.md`, task docs, pack docs, logs, or test output.\n   - Search only the scoped repo\u002Fsession\u002Fhistory for the issue text, skill name, invocation command, relevant file paths, user correction, and nearby agent actions.\n   - Include the active conversation as evidence when the correction is happening now.\n   - Broaden to `$analyze-sessions` only when recurrence, frequency, or trend evidence is needed.\n\n3. Verify the issue before diagnosing:\n   - Separate the **user-identified issue** from the **agent-verified issue**.\n   - Classify the verification verdict as `verified`, `partially verified`, `not verified`, or `inconclusive`.\n   - A verified issue requires evidence for what the agent did, what the skill\u002Frepo\u002Fuser contract required, and why the outcome was wrong or risky.\n   - If evidence shows the skill contract was adequate and the agent ignored it, say that directly.\n\n4. Build a concise timeline:\n   - User request or trigger.\n   - Skill or instruction that should have applied.\n   - Agent action or omission.\n   - Failure, correction, or observed impact.\n   - Relevant repo\u002Fsession state.\n\n5. Diagnose root cause:\n   - Identify whether the cause is a missing trigger, ambiguous trigger, missing evidence gate, insufficient scope resolution, weak output contract, bad next-step routing, missing validation, missing safety constraint, stale mirrored contract, repo instruction conflict, or agent noncompliance with an adequate contract.\n   - Compare Claude and Codex skill versions when both exist and flag mirrored drift.\n   - Check `tasks\u002Flessons.md` when working in `agentic-skills`; reuse existing lessons or recommend a new lesson when the pattern is novel.\n   - For benchmark failures, check recent same-skill `agentic-skills-benchmarks\u002Fbenchmark\u002Ftriage-\u003Cskill>-*.md` reports and `tasks\u002Flessons.md` before recommending a narrow tolerance patch. If two or more recent reports classify the same family of valid outputs as benchmark false negatives, stop patching individual phrasings and route to a generalized rubric, semantic evaluator, fixture-family, or infrastructure-classifier fix that covers the family.\n   - For a `benchmark regression` invocation, the absolute thresholds may still pass — the issue is a *drop relative to the prior grade*. Use the carried delta and `agentic-skills-benchmarks\u002Fbenchmark\u002Fgrade-history.json` to confirm the regression is real (not a one-run sampling artifact: small evaluated-run counts and wide Wilson intervals can move >=10pp by chance — say so and recommend a confirming re-run when the sample is thin). Then classify the cause:\n     - **Real behavioral regression** — the skill contract or a dependency changed and the agent now produces worse output. Route the fix to `$targeted-skill-builder \u003Cskill> benchmark regression` naming the contract section that drifted, and confirm the loop closes by re-running `$benchmark-test-skill \u003Cskill>` to verify the grade recovers in `grade-history.json`.\n     - **Harness \u002F rubric drift** — the skill behavior is unchanged but a setup, fixture, evaluator, or pricing\u002Fthreshold change moved the score. Reuse the false-negative-family logic above (steps 5-6): name the owning harness\u002Fsetup file and the family-level behavior to recognize, rather than patching one phrasing.\n\n6. Recommend the smallest durable fix:\n   - Name exact skill file(s), instruction file(s), or docs to change.\n   - Provide concrete rule text or workflow-step wording when a skill-contract change is justified.\n   - Include validation checks that prove the revised behavior prevents the issue, such as targeted `rg` checks, mirrored contract checks, version checks, replay of the decision path, or the failing test\u002Flog command.\n   - For repeated benchmark false-negative families, the recommended fix must name the owning harness or setup file, the family-level behavior to recognize or reject, positive and negative fixture shapes to add, and a validation command such as focused layer1 setup tests plus `pnpm --dir tests verify --skill \u003Cskill>`.\n   - Route verified skill changes to `$targeted-skill-builder` (skill-dev pack) for a narrow update or `$create-agentic-skill` (skill-dev pack) for a new repo-managed skill.\n\n7. Optionally enrich the persistent insights memory (secondary writer):\n   - When the triaged incident is a verified, generalizable pattern (not a pure one-off), append it to the machine-local `.session-insights\u002Finsights.md` store that `$analyze-sessions` accumulates, so live incidents and cross-session trends share one memory.\n   - The store is gitignored and may not exist yet; create it with the standard keyed table header (`| Insight | Category | First Seen | Last Seen | Occurrences | Status |`) if absent. If a semantically matching row already exists, increment its Occurrences and advance Last Seen instead of adding a duplicate; otherwise add a row with Occurrences `1` and Status `confirmed` (triage incidents are verified).\n   - This is additive memory only — `tasks\u002Flessons.md` remains the authoritative correction log; do not move lessons content into the insights store.\n\n## Pack Availability Guard\n\nBefore recommending another skill, verify the target skill itself is available before relying on pack availability:\n\n- Treat `.agents\u002Fproject.json` `enabled_skills.\u003Cskill-name>` as direct availability, even when the provider pack is not listed in `enabled_packs`.\n- Treat `.agents\u002Fproject.json` `enabled_packs` as availability only when the enabled pack provides the target skill; use `scripts\u002Fpack.sh which \u003Cskill-name>` when available to identify the provider.\n- Treat local or global skill files as direct availability evidence, including `.codex\u002Fskills\u002F\u003Cskill-name>\u002FSKILL.md`, `.claude\u002Fskills\u002F\u003Cskill-name>\u002FSKILL.md`, `~\u002F.codex\u002Fskills\u002F\u003Cskill-name>\u002FSKILL.md`, and `~\u002F.claude\u002Fskills\u002F\u003Cskill-name>\u002FSKILL.md`.\n\nIf the target skill is unavailable, recommend `npx skillpacks install \u003Cpack-or-skill>` from the project shell before the skill invocation. Prefer the provider pack when it is known; otherwise recommend installing the target skill by name. Tell Codex users to start a fresh Codex CLI session if the `$` skill list remains stale after install.\n\nFor benchmark regression loop-closing, treat `$benchmark-test-skill` as owned by `agentic-skills-bench`: check whether `.agents\u002Fproject.json` `enabled_packs` includes `agentic-skills-bench` before recommending or relying on `$benchmark-test-skill \u003Cskill>`. If `agentic-skills-bench` is not enabled, recommend `npx skillpacks install agentic-skills-bench` from the project shell first, then tell Codex users to start a fresh Codex CLI session if the `$` skill list remains stale after install.\n\n## Output\n\nProduce a structured report with:\n\n- Target: session\u002Frepo\u002Fskill scope and evidence sources.\n- User-identified issue: the user's claim in concise terms.\n- Verification verdict: `verified`, `partially verified`, `not verified`, or `inconclusive`, with supporting evidence.\n- Timeline: short sequence from trigger to correction or impact.\n- Root cause: the specific contract gap, repo conflict, or agent noncompliance pattern.\n- Responsible contract gap: skill, project instruction, task doc, or none.\n- Recommended fix: exact file(s), section(s), and proposed wording or behavior change.\n- Validation plan: commands or checks to prove the fix.\n- Confidence and evidence gaps: what is known, what could not be verified, and whether `$analyze-sessions` is needed for recurrence analysis.\n- Recommended next skill: `$targeted-skill-builder` (skill-dev pack), `$create-agentic-skill` (skill-dev pack), `$analyze-sessions`, or `none` when no follow-up is justified. For a confirmed real `benchmark regression`, recommend `$targeted-skill-builder \u003Cskill> benchmark regression` and, after applying the Pack Availability Guard for `agentic-skills-bench`, name re-running `$benchmark-test-skill \u003Cskill>` as the loop-closing verification (see `docs\u002Fbenchmark-improvement-loop.md`).\n\n## Constraints\n\n- Start narrow and evidence-bound; do not scan all local history by default.\n- Do not claim a user-identified issue is agent-verified without independent evidence.\n- Do not modify the target skill during analysis unless the user also asked for implementation and the active workflow permits edits.\n- Do not recommend a skill change when the evidence points only to one-off agent noncompliance and the contract is already clear.\n- Do not create or suggest `$analyze-session`; use `$session-triage`.\n- Do not create or modify GitHub Actions workflows.\n- If a source is missing or unreadable, report that clearly and continue with available evidence instead of guessing.\n- When recommending another skill, apply the Pack Availability Guard: check `enabled_skills`, enabled provider packs, and local\u002Fglobal skill files before recommending the skill directly; if unavailable, prepend `npx skillpacks install \u003Cpack-or-skill>` to the recommendation.\n\n## Default Shipping Contract\n\nFollow the shared shipping contract convention in CLAUDE.md.\n",{"name":5,"type":23,"version":39,"description":7,"argument-hint":40},"v0.7","[session id\u002Ffile, repo path, skill name\u002Fpath, correction text, or issue description]","master","96e2912af886dd1606b1b97df707715aef062b02","packs\u002Fsession-analytics\u002Fcodex\u002Fsession-triage\u002Farchive\u002Fv0.7",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":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add GeorgeQLe\u002Fagentic-skills --skill session-triage",{"tool":57,"command":58},"bunx","bunx skills add GeorgeQLe\u002Fagentic-skills --skill session-triage",{"tool":60,"command":61},"pnpm","pnpm dlx skills add GeorgeQLe\u002Fagentic-skills --skill session-triage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fsession-analytics\u002Fcodex\u002Fsession-triage\u002Farchive\u002Fv0.7\u002FSKILL.md",true,[],[66,78,88,100,115,126],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":34},"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",[],[73,74,75,76,29,77],"source checkout allowed","checkout","fixture","only","valid",{"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":34},"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",[],[85,86,87,77,75,29],"deck install valid","deck","install",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":34},"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",[],[95,96,97,77,98,99,75,29],"codex pack guard valid","pack","guard","codex","availability",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":111,"publishedAt":34},"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",[106],{"categoryNo":107,"categoryName":108,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[112,113,77,98,29,114,75],"codex missing skill valid","missing","fallback",{"skillNo":116,"name":117,"nameZh":6,"description":118,"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":34},"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",[121],{"categoryNo":107,"categoryName":108,"taxonomyType":109,"taxonomyTypeDesc":110},[77,98,114,123,124,125,29,75],"base skill","codex base skill fallback valid","base",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":34},"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",[],[77,97,96,133,99,29,75],"claude pack guard valid"]