[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FZHRS7ADQWCEFRW57ACD2R":3,"skill-same:01M6FZHRS7ADQWCEFRW57ACD2R":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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M6FZHRS7ADQWCEFRW57ACD2R","skill-interview",null,"Interview the user to define the characteristics of a skill they want created","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\u002Fskill-dev\u002Fcodex\u002Fskill-interview\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38],"interview","skill interview","planning","page","user","v0","alignment","deep","define","name","2026-11-10 10:12:30",false,"---\nname: skill-interview\ndescription: Interview the user to define the characteristics of a skill they want created\ntype: planning\nversion: v0.3\nrequired_conventions: [alignment-page]\nargument-hint: \"[skill-name-or-topic]\"\ncontext_intake: deep\n---\n\n# Skill Interview\n\nInvoke as `$skill-interview`.\n\nUse this skill when the user wants to create or substantially redesign a skill but the desired behavior, scope, triggers, outputs, validation, or agent compatibility is not yet clear. This skill interrogates the user and turns the answers into a creation-ready skill brief. It does not create the skill itself. After the brief is complete: for a personal project-local skill route to `$create-local-skill`; for a repo-managed skill in the `agentic-skills` repo, hand the brief to an agent working in that repo to implement following the skill conventions (`docs\u002Fskill-anatomy.md`, CLAUDE.md skill-versioning); for a change to an existing shared skill route to `$session-triage`, which emits a managing-layer handoff payload for the fix.\n\n## Process\n\n1. **Identify the target skill idea.**\n   - Treat the user's initial request as a draft, not a complete requirement.\n   - Resolve the likely skill name in kebab-case when possible.\n   - If the request is a correction to an existing shared skill or workflow gap, route to `$session-triage` after the interview instead of scaffolding a new skill.\n   - If the user wants an experimental personal skill under `~\u002F.codex\u002Fskills`, plan for `$create-local-skill`; otherwise default to a repo-managed skill implemented directly in the `agentic-skills` repo.\n\n2. **Gather local evidence before probing.**\n   - Search for overlapping skills in the active skill list and repository paths such as `base\u002Fcodex\u002F`, `base\u002Fclaude\u002F`, and `packs\u002F*\u002F{codex,claude}\u002F`.\n   - Read the closest existing skill contracts and any relevant `tasks\u002Flessons.md` entries before asking detailed questions.\n   - If an existing skill already covers the request, explain the overlap and ask whether the user wants an update, alias, narrower variant, or new skill.\n\n3. **Surface a lightweight assumptions checkpoint.**\n   - Before deep probing, present 3 to 7 assumptions most likely to affect the skill contract.\n   - Tag each assumption:\n     - `[from request]` — explicitly stated by the user\n     - `[from existing skill]` — derived from a current skill contract\n     - `[from lessons]` — derived from `tasks\u002Flessons.md`\n     - `[from codebase]` — derived from repository conventions or test harnesses\n     - `[inferred]` — a default judgment that needs confirmation\n   - Bias toward assumptions that affect trigger rules, allowed side effects, deliverables, verification, benchmarkability, and next-step routing.\n   - Deliver the checkpoint inline as the final message text of its own turn — never only as mid-turn text in a turn that ends with a tool or command call. In the next turn, ask the user to confirm or correct it together with one focused interview question so momentum is kept.\n   - If an `[inferred]` assumption is corrected, preserve the correction in the interview log and final brief.\n\n4. **Interview one material decision at a time.**\n   - Codex cadence: ask one primary decision question per turn by default. Use short follow-up bullets only when they clarify the same decision.\n   - If already in Plan mode, `request_user_input` may present 2 to 3 real options for the current material decision. Otherwise ask one concise direct question in plain text.\n   - Research and recommend by default: use local codebase evidence and, when the user requests current external facts, web evidence before asking the user to choose.\n   - For each material choice, explain the options, recommend one, and ask the user to approve, adjust, or override.\n\n5. **Cover the skill characteristics completely.**\n   - Continue until the brief captures:\n     - Skill name and one-line description\n     - Target location: repo-managed, local-only, pack-local, Codex-only, Claude-only, or mirrored\n     - Trigger rules and explicit non-triggers\n     - Inputs and argument syntax\n     - Required evidence gathering before questions or edits\n     - Interview cadence or execution workflow\n     - Deliverables and file paths\n     - Side-effect permissions and safety constraints\n     - Verification and benchmark coverage strategy\n     - Next-step routing after successful completion\n     - Relationship to overlapping skills\n   - For mutation-capable skills, explicitly define whether the skill should commit and push by default.\n   - For repo-managed skills, include benchmark coverage expectations in the brief.\n\n6. **Coverage checkpoint.**\n   - Before concluding, summarize each covered area with the decision made and source evidence, delivered inline as the final message text of its own turn.\n   - In the next turn, ask: \"Does this cover the skill you want, or is there any behavior, boundary, or output we should revisit?\"\n   - Do not write final deliverables until the user confirms the checkpoint or provides final corrections.\n\n7. **Write deliverables.**\n   - Create `specs\u002F[skill-name]-skill-brief.md` with:\n     - `## Overview`\n     - `## Goals`\n     - `## Non-Goals`\n     - `## Skill Contract`\n     - `## Workflow`\n     - `## Inputs and Outputs`\n     - `## Safety and Side Effects`\n     - `## Verification and Benchmark Coverage`\n     - `## Related Skills`\n     - `## Open Questions`\n     - `## Assumptions & Risks`\n     - `## Recommended Creation Route`\n   - Create `specs\u002F[skill-name]-skill-interview.md` with:\n     - Assumptions checkpoint and corrections\n     - Questions asked\n     - Options and recommendations presented\n     - User responses and decisions\n     - Deviations from the initial request\n   - If the repository uses another canonical specification directory, use that directory and note the path.\n\n## Next-Step Routing\n\nAfter writing the brief and interview log, recommend exactly one next command:\n\n- Implement a repo-managed skill directly in the `agentic-skills` repo, following `docs\u002Fskill-anatomy.md` and CLAUDE.md skill-versioning, using the brief as the spec.\n- `$create-local-skill \u003Cskill-name>` for personal local-only skills.\n- `$session-triage \u003Cexisting-skill> \u003Cgap>` when the interview found that an existing shared skill should be updated instead of creating a new skill — it emits a managing-layer handoff payload for the fix.\n- `$init-agentic-skills` (guided pack setup) or a pack-local creation route when the skill belongs inside a project-local pack rather than base skills.\n\nOutput exactly two lines beyond the normal report:\n\n- **Next work:** \u003Cspecific skill creation or update task>\n- **Recommended next command:** \u003Cone command>\n\n## Alignment Page\n\nFollow the shared alignment-page convention via the packaged convention resolver; output path is `alignment\u002Fskill-interview-{topic}.html`.\n\n## Constraints\n\n- Do not create or edit the final `SKILL.md` during the interview unless the user explicitly asks to skip the brief and create the skill now.\n- Do not assume a new skill is needed when an existing skill update would satisfy the workflow gap.\n- Do not batch unrelated interview questions.\n- Do not invent benchmark coverage; if deterministic local coverage is unsafe or impractical, mark the coverage plan as blocked with a reason and next command.\n- Keep the final brief implementation-ready enough that an agent implementing in the `agentic-skills` repo, or `$create-local-skill`, can execute without re-interviewing the same decisions.\n\n## Default Shipping Contract\n\nFollow the shared shipping contract convention in CLAUDE.md.\n\n","# Skill Interview\n\nInvoke as `$skill-interview`.\n\nUse this skill when the user wants to create or substantially redesign a skill but the desired behavior, scope, triggers, outputs, validation, or agent compatibility is not yet clear. This skill interrogates the user and turns the answers into a creation-ready skill brief. It does not create the skill itself. After the brief is complete: for a personal project-local skill route to `$create-local-skill`; for a repo-managed skill in the `agentic-skills` repo, hand the brief to an agent working in that repo to implement following the skill conventions (`docs\u002Fskill-anatomy.md`, CLAUDE.md skill-versioning); for a change to an existing shared skill route to `$session-triage`, which emits a managing-layer handoff payload for the fix.\n\n## Process\n\n1. **Identify the target skill idea.**\n   - Treat the user's initial request as a draft, not a complete requirement.\n   - Resolve the likely skill name in kebab-case when possible.\n   - If the request is a correction to an existing shared skill or workflow gap, route to `$session-triage` after the interview instead of scaffolding a new skill.\n   - If the user wants an experimental personal skill under `~\u002F.codex\u002Fskills`, plan for `$create-local-skill`; otherwise default to a repo-managed skill implemented directly in the `agentic-skills` repo.\n\n2. **Gather local evidence before probing.**\n   - Search for overlapping skills in the active skill list and repository paths such as `base\u002Fcodex\u002F`, `base\u002Fclaude\u002F`, and `packs\u002F*\u002F{codex,claude}\u002F`.\n   - Read the closest existing skill contracts and any relevant `tasks\u002Flessons.md` entries before asking detailed questions.\n   - If an existing skill already covers the request, explain the overlap and ask whether the user wants an update, alias, narrower variant, or new skill.\n\n3. **Surface a lightweight assumptions checkpoint.**\n   - Before deep probing, present 3 to 7 assumptions most likely to affect the skill contract.\n   - Tag each assumption:\n     - `[from request]` — explicitly stated by the user\n     - `[from existing skill]` — derived from a current skill contract\n     - `[from lessons]` — derived from `tasks\u002Flessons.md`\n     - `[from codebase]` — derived from repository conventions or test harnesses\n     - `[inferred]` — a default judgment that needs confirmation\n   - Bias toward assumptions that affect trigger rules, allowed side effects, deliverables, verification, benchmarkability, and next-step routing.\n   - Deliver the checkpoint inline as the final message text of its own turn — never only as mid-turn text in a turn that ends with a tool or command call. In the next turn, ask the user to confirm or correct it together with one focused interview question so momentum is kept.\n   - If an `[inferred]` assumption is corrected, preserve the correction in the interview log and final brief.\n\n4. **Interview one material decision at a time.**\n   - Codex cadence: ask one primary decision question per turn by default. Use short follow-up bullets only when they clarify the same decision.\n   - If already in Plan mode, `request_user_input` may present 2 to 3 real options for the current material decision. Otherwise ask one concise direct question in plain text.\n   - Research and recommend by default: use local codebase evidence and, when the user requests current external facts, web evidence before asking the user to choose.\n   - For each material choice, explain the options, recommend one, and ask the user to approve, adjust, or override.\n\n5. **Cover the skill characteristics completely.**\n   - Continue until the brief captures:\n     - Skill name and one-line description\n     - Target location: repo-managed, local-only, pack-local, Codex-only, Claude-only, or mirrored\n     - Trigger rules and explicit non-triggers\n     - Inputs and argument syntax\n     - Required evidence gathering before questions or edits\n     - Interview cadence or execution workflow\n     - Deliverables and file paths\n     - Side-effect permissions and safety constraints\n     - Verification and benchmark coverage strategy\n     - Next-step routing after successful completion\n     - Relationship to overlapping skills\n   - For mutation-capable skills, explicitly define whether the skill should commit and push by default.\n   - For repo-managed skills, include benchmark coverage expectations in the brief.\n\n6. **Coverage checkpoint.**\n   - Before concluding, summarize each covered area with the decision made and source evidence, delivered inline as the final message text of its own turn.\n   - In the next turn, ask: \"Does this cover the skill you want, or is there any behavior, boundary, or output we should revisit?\"\n   - Do not write final deliverables until the user confirms the checkpoint or provides final corrections.\n\n7. **Write deliverables.**\n   - Create `specs\u002F[skill-name]-skill-brief.md` with:\n     - `## Overview`\n     - `## Goals`\n     - `## Non-Goals`\n     - `## Skill Contract`\n     - `## Workflow`\n     - `## Inputs and Outputs`\n     - `## Safety and Side Effects`\n     - `## Verification and Benchmark Coverage`\n     - `## Related Skills`\n     - `## Open Questions`\n     - `## Assumptions & Risks`\n     - `## Recommended Creation Route`\n   - Create `specs\u002F[skill-name]-skill-interview.md` with:\n     - Assumptions checkpoint and corrections\n     - Questions asked\n     - Options and recommendations presented\n     - User responses and decisions\n     - Deviations from the initial request\n   - If the repository uses another canonical specification directory, use that directory and note the path.\n\n## Next-Step Routing\n\nAfter writing the brief and interview log, recommend exactly one next command:\n\n- Implement a repo-managed skill directly in the `agentic-skills` repo, following `docs\u002Fskill-anatomy.md` and CLAUDE.md skill-versioning, using the brief as the spec.\n- `$create-local-skill \u003Cskill-name>` for personal local-only skills.\n- `$session-triage \u003Cexisting-skill> \u003Cgap>` when the interview found that an existing shared skill should be updated instead of creating a new skill — it emits a managing-layer handoff payload for the fix.\n- `$init-agentic-skills` (guided pack setup) or a pack-local creation route when the skill belongs inside a project-local pack rather than base skills.\n\nOutput exactly two lines beyond the normal report:\n\n- **Next work:** \u003Cspecific skill creation or update task>\n- **Recommended next command:** \u003Cone command>\n\n## Alignment Page\n\nFollow the shared alignment-page convention via the packaged convention resolver; output path is `alignment\u002Fskill-interview-{topic}.html`.\n\n## Constraints\n\n- Do not create or edit the final `SKILL.md` during the interview unless the user explicitly asks to skip the brief and create the skill now.\n- Do not assume a new skill is needed when an existing skill update would satisfy the workflow gap.\n- Do not batch unrelated interview questions.\n- Do not invent benchmark coverage; if deterministic local coverage is unsafe or impractical, mark the coverage plan as blocked with a reason and next command.\n- Keep the final brief implementation-ready enough that an agent implementing in the `agentic-skills` repo, or `$create-local-skill`, can execute without re-interviewing the same decisions.\n\n## Default Shipping Contract\n\nFollow the shared shipping contract convention in CLAUDE.md.\n\n",{"name":5,"type":31,"version":44,"description":7,"argument-hint":45,"context_intake":36,"required_conventions":46},"v0.3","[skill-name-or-topic]",[47],"alignment-page","master","96e2912af886dd1606b1b97df707715aef062b02","packs\u002Fskill-dev\u002Fcodex\u002Fskill-interview",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":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add GeorgeQLe\u002Fagentic-skills --skill skill-interview",{"tool":64,"command":65},"bunx","bunx skills add GeorgeQLe\u002Fagentic-skills --skill skill-interview",{"tool":67,"command":68},"pnpm","pnpm dlx skills add GeorgeQLe\u002Fagentic-skills --skill skill-interview","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fskill-dev\u002Fcodex\u002Fskill-interview\u002FSKILL.md",true,[72,78],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"ALIGNMENT-PAGE.md","REFERENCE","参考文档",52725,"https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fskill-dev\u002Fcodex\u002Fskill-interview\u002FALIGNMENT-PAGE.md",{"path":79,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":80,"sourceHtmlUrl":81},"CHANGELOG.md",1058,"https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fskill-dev\u002Fcodex\u002Fskill-interview\u002FCHANGELOG.md",[83,95,105,117,128,139],{"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":39},"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,34,94],"source checkout allowed","checkout","fixture","only","valid",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":39},"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",[],[102,103,104,94,92,34],"deck install valid","deck","install",{"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":111,"publishedAt":39},"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",[],[112,113,114,94,115,116,92,34],"codex pack guard valid","pack","guard","codex","availability",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":124,"publishedAt":39},"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",[123],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[125,126,94,115,34,127,92],"codex missing skill valid","missing","fallback",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":135,"publishedAt":39},"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",[134],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[94,115,127,136,137,138,34,92],"base skill","codex base skill fallback valid","base",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":39},"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",[],[94,114,113,146,116,34,92],"claude pack guard valid"]