[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DEP60A43KNDHDQFFXADKMZ":3,"skill-same:01M7DEP60A43KNDHDQFFXADKMZ":45},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7DEP60A43KNDHDQFFXADKMZ","create-hook",null,"Create Codex hooks. Use when the user wants to run a script or MCP tool at a Codex lifecycle event, write hooks.json, add hook scripts, or debug hook discovery and trust.","odellsallis93\u002Fskills-repo","odellsallis93","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87449759?v=4","01M7DEG0QK6S7ZF5TAZZH1JKT9","ODell Sallis","01M7DEG0R9VYQBMCTWBFXHBZDS",0,"MIT","https:\u002F\u002Fgithub.com\u002Fodellsallis93\u002Fskills-repo\u002Fblob\u002Fmain\u002Fplugins\u002Fodell-codex\u002Fskills\u002Fcreate-hook\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: create-hook\ndescription: >-\n  Create Codex hooks. Use when the user wants to run a script or MCP tool at a\n  Codex lifecycle event, write hooks.json, add hook scripts, or debug hook\n  discovery and trust.\n---\n\n# Create Codex hooks\n\nCreate or update the hook files when the user asks for a hook. Do not stop at a format explanation.\n\n## Choose the scope and location\n\nCodex discovers hooks next to active configuration layers:\n\n- User JSON: `~\u002F.codex\u002Fhooks.json`\n- User TOML: inline `[hooks]` tables in `~\u002F.codex\u002Fconfig.toml`\n- Project JSON: `\u003Crepo>\u002F.codex\u002Fhooks.json`\n- Project TOML: inline `[hooks]` tables in `\u003Crepo>\u002F.codex\u002Fconfig.toml`\n- Plugin: `hooks\u002Fhooks.json` inside the plugin unless its manifest overrides the path\n\nStore related user scripts under `~\u002F.codex\u002Fhooks\u002F`. Store project scripts under `\u003Crepo>\u002F.codex\u002Fhooks\u002F`.\n\nPrefer one representation per config layer. If a layer has both `hooks.json` and inline TOML hooks, Codex merges them and warns.\n\nProject hooks load only for trusted projects. Non-managed hooks must be reviewed and trusted before they run. Use `\u002Fhooks` to inspect sources, review changes, trust a definition, or disable a hook.\n\n## Supported lifecycle events\n\nUse the narrowest event that fits:\n\n- `SessionStart`, `SessionEnd`\n- `UserPromptSubmit`\n- `PreToolUse`, `PermissionRequest`, `PostToolUse`\n- `SubagentStart`, `SubagentStop`\n- `PreCompact`, `PostCompact`\n- `Stop`\n\nEvent names are case-sensitive.\n\n## JSON shape\n\nA hook has an event, a matcher group, and one or more handlers:\n\n```json\n{\n  \"description\": \"Project command review hook.\",\n  \"hooks\": {\n    \"PreToolUse\": [\n      {\n        \"matcher\": \"^Bash$\",\n        \"hooks\": [\n          {\n            \"type\": \"command\",\n            \"command\": \"\u002Fusr\u002Fbin\u002Fpython3 \\\"$(git rev-parse --show-toplevel)\u002F.codex\u002Fhooks\u002Fpre_tool_use.py\\\"\",\n            \"timeout\": 30,\n            \"statusMessage\": \"Checking shell command\"\n          }\n        ]\n      }\n    ]\n  }\n}\n```\n\nDo not add the old Cursor `version: 1` wrapper. Keep existing unrelated hook groups intact.\n\n## Handler types\n\nUse one of the handler types Codex runs:\n\n- `command` executes a local command. It receives the event JSON on stdin and returns its event-specific response on stdout.\n- `mcp_tool` calls a tool on an already-connected MCP server.\n\n`prompt` and `agent` handlers may parse, but Codex currently skips them. Do not create them.\n\nFor command hooks:\n\n- Give scripts a valid shebang and executable permission.\n- Verify every helper binary they call.\n- Parse stdin defensively and emit only fields supported by that event.\n- Use an explicit timeout when a stalled command would disrupt the workflow.\n- Remember that matching command hooks for the same event launch concurrently.\n\nCommands run with the session working directory. A project session may start in a subdirectory, so resolve project scripts from the Git root instead of relying on a relative path such as `.codex\u002Fhooks\u002Fscript.py`.\n\n## MCP tool example\n\n```json\n{\n  \"hooks\": {\n    \"PostToolUse\": [\n      {\n        \"matcher\": \"Write|Edit\",\n        \"hooks\": [\n          {\n            \"type\": \"mcp_tool\",\n            \"server\": \"scanner\",\n            \"tool\": \"scan_patch\",\n            \"input\": {\n              \"path\": \"${tool_input.file_path}\"\n            },\n            \"timeout\": 30\n          }\n        ]\n      }\n    ]\n  }\n}\n```\n\nCodex expands `${field.nested}` placeholders from the hook event.\n\n## Workflow\n\n1. Determine the scope, event, matcher, handler type, and desired effect.\n2. Read the existing hook source and preserve unrelated entries.\n3. Write the hook definition and any required script under the matching `.codex\u002Fhooks\u002F` directory.\n4. Validate JSON or TOML syntax.\n5. Make command scripts executable and verify their dependencies.\n6. Open `\u002Fhooks` and complete the required trust review.\n7. Trigger the real event and check the observed result.\n\nBefore using an unfamiliar event field or response field, consult the current official Codex hooks documentation.\n","# Create Codex hooks\n\nCreate or update the hook files when the user asks for a hook. Do not stop at a format explanation.\n\n## Choose the scope and location\n\nCodex discovers hooks next to active configuration layers:\n\n- User JSON: `~\u002F.codex\u002Fhooks.json`\n- User TOML: inline `[hooks]` tables in `~\u002F.codex\u002Fconfig.toml`\n- Project JSON: `\u003Crepo>\u002F.codex\u002Fhooks.json`\n- Project TOML: inline `[hooks]` tables in `\u003Crepo>\u002F.codex\u002Fconfig.toml`\n- Plugin: `hooks\u002Fhooks.json` inside the plugin unless its manifest overrides the path\n\nStore related user scripts under `~\u002F.codex\u002Fhooks\u002F`. Store project scripts under `\u003Crepo>\u002F.codex\u002Fhooks\u002F`.\n\nPrefer one representation per config layer. If a layer has both `hooks.json` and inline TOML hooks, Codex merges them and warns.\n\nProject hooks load only for trusted projects. Non-managed hooks must be reviewed and trusted before they run. Use `\u002Fhooks` to inspect sources, review changes, trust a definition, or disable a hook.\n\n## Supported lifecycle events\n\nUse the narrowest event that fits:\n\n- `SessionStart`, `SessionEnd`\n- `UserPromptSubmit`\n- `PreToolUse`, `PermissionRequest`, `PostToolUse`\n- `SubagentStart`, `SubagentStop`\n- `PreCompact`, `PostCompact`\n- `Stop`\n\nEvent names are case-sensitive.\n\n## JSON shape\n\nA hook has an event, a matcher group, and one or more handlers:\n\n```json\n{\n  \"description\": \"Project command review hook.\",\n  \"hooks\": {\n    \"PreToolUse\": [\n      {\n        \"matcher\": \"^Bash$\",\n        \"hooks\": [\n          {\n            \"type\": \"command\",\n            \"command\": \"\u002Fusr\u002Fbin\u002Fpython3 \\\"$(git rev-parse --show-toplevel)\u002F.codex\u002Fhooks\u002Fpre_tool_use.py\\\"\",\n            \"timeout\": 30,\n            \"statusMessage\": \"Checking shell command\"\n          }\n        ]\n      }\n    ]\n  }\n}\n```\n\nDo not add the old Cursor `version: 1` wrapper. Keep existing unrelated hook groups intact.\n\n## Handler types\n\nUse one of the handler types Codex runs:\n\n- `command` executes a local command. It receives the event JSON on stdin and returns its event-specific response on stdout.\n- `mcp_tool` calls a tool on an already-connected MCP server.\n\n`prompt` and `agent` handlers may parse, but Codex currently skips them. Do not create them.\n\nFor command hooks:\n\n- Give scripts a valid shebang and executable permission.\n- Verify every helper binary they call.\n- Parse stdin defensively and emit only fields supported by that event.\n- Use an explicit timeout when a stalled command would disrupt the workflow.\n- Remember that matching command hooks for the same event launch concurrently.\n\nCommands run with the session working directory. A project session may start in a subdirectory, so resolve project scripts from the Git root instead of relying on a relative path such as `.codex\u002Fhooks\u002Fscript.py`.\n\n## MCP tool example\n\n```json\n{\n  \"hooks\": {\n    \"PostToolUse\": [\n      {\n        \"matcher\": \"Write|Edit\",\n        \"hooks\": [\n          {\n            \"type\": \"mcp_tool\",\n            \"server\": \"scanner\",\n            \"tool\": \"scan_patch\",\n            \"input\": {\n              \"path\": \"${tool_input.file_path}\"\n            },\n            \"timeout\": 30\n          }\n        ]\n      }\n    ]\n  }\n}\n```\n\nCodex expands `${field.nested}` placeholders from the hook event.\n\n## Workflow\n\n1. Determine the scope, event, matcher, handler type, and desired effect.\n2. Read the existing hook source and preserve unrelated entries.\n3. Write the hook definition and any required script under the matching `.codex\u002Fhooks\u002F` directory.\n4. Validate JSON or TOML syntax.\n5. Make command scripts executable and verify their dependencies.\n6. Open `\u002Fhooks` and complete the required trust review.\n7. Trigger the real event and check the observed result.\n\nBefore using an unfamiliar event field or response field, consult the current official Codex hooks documentation.\n",{"name":5,"description":7},"main","1c9c71cb8682c1f18c7a54bc09a9ddfe2f70b80d","plugins\u002Fodell-codex\u002Fskills\u002Fcreate-hook","https:\u002F\u002Fgithub.com\u002Fodellsallis93\u002Fskills-repo","https:\u002F\u002Fgithub.com\u002Fodellsallis93","SWE: Applied \u002F Agentic AI, Full-stack Web Dev, Mobile, Design | Computer Vision | Automation | Events | Music","2026-11-11 07:05:03",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add odellsallis93\u002Fskills-repo --skill create-hook",{"tool":37,"command":38},"bunx","bunx skills add odellsallis93\u002Fskills-repo --skill create-hook",{"tool":40,"command":41},"pnpm","pnpm dlx skills add odellsallis93\u002Fskills-repo --skill create-hook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fodellsallis93\u002Fskills-repo\u002Fblob\u002Fmain\u002Fplugins\u002Fodell-codex\u002Fskills\u002Fcreate-hook\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7DF09PNHXECAA9M9472985Z","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Fodellsallis93\u002Fskills-repo\u002Fblob\u002Fmain\u002Fskills\u002Fwizard\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7DF06BVP31PP8PB9WQBG6NR","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Fodellsallis93\u002Fskills-repo\u002Fblob\u002Fmain\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7DF03EM39HHEET1C44R50F7","wait-what","Stop. That last message did not land: re-pitch it.","https:\u002F\u002Fgithub.com\u002Fodellsallis93\u002Fskills-repo\u002Fblob\u002Fmain\u002Fskills\u002Fwait-what\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7DF00MVBHP5P88V3A8FR3AW","triage","Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.","https:\u002F\u002Fgithub.com\u002Fodellsallis93\u002Fskills-repo\u002Fblob\u002Fmain\u002Fskills\u002Ftriage\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7DEZWFJTR2K5SGCVE1MQRTZ","to-tickets","Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).","https:\u002F\u002Fgithub.com\u002Fodellsallis93\u002Fskills-repo\u002Fblob\u002Fmain\u002Fskills\u002Fto-tickets\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7DEZSYEBMNAGE02BCYWKMHT","to-spec","Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.","https:\u002F\u002Fgithub.com\u002Fodellsallis93\u002Fskills-repo\u002Fblob\u002Fmain\u002Fskills\u002Fto-spec\u002FSKILL.md",[],[]]