[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74XCC2266EX2XACDFW4SM2K":3,"skill-same:01M74XCC2266EX2XACDFW4SM2K":43},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M74XCC2266EX2XACDFW4SM2K","declarative-hook-rules-inert-without-dispatcher",null,"A compliance report or workflow recommends \"promote this to a hook,\" and the obvious move is to write a declarative hook-rule file (e.g. .claude\u002Fhookify.*.local.md) in whatever format a rule-authoring skill defines — but if nothing in the settings stack (project settings.json, global settings, every installed plugin's hooks.json) actually reads that rule-file glob, the file is inert: it silently does nothing, and the failure mode only shows up much later as \"the hook didn't fire,\" with no error anywhere. Use before authoring any hook-rule-file content, or when auditing why a hook that \"should\" be firing per a rule file never actually runs.","abhijitbansal\u002Fclaude-skills","abhijitbansal","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F271802621?v=4","01M74XA5M33XYNJ2D2TJDS7W9E","01M74XA5MQ8GMWJW10ZJ4V0NVG",1,"MIT","https:\u002F\u002Fgithub.com\u002Fabhijitbansal\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fcore-workflow\u002Fskills\u002Fdeclarative-hook-rules-inert-without-dispatcher\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: declarative-hook-rules-inert-without-dispatcher\ndescription: \"A compliance report or workflow recommends \\\"promote this to a hook,\\\" and the obvious move is to write a declarative hook-rule file (e.g. .claude\u002Fhookify.*.local.md) in whatever format a rule-authoring skill defines — but if nothing in the settings stack (project settings.json, global settings, every installed plugin's hooks.json) actually reads that rule-file glob, the file is inert: it silently does nothing, and the failure mode only shows up much later as \\\"the hook didn't fire,\\\" with no error anywhere. Use before authoring any hook-rule-file content, or when auditing why a hook that \\\"should\\\" be firing per a rule file never actually runs.\"\n---\n\n# Verify a Hook-Rule-File Mechanism Has a Dispatcher Before Authoring Rules\n\n## Symptom\n\nA compliance report recommends \"promote to hooks\" for a failing workflow\nstep. The obvious move is to write a declarative rule file (e.g.\n`.claude\u002Fhookify.*.local.md`) in the format a rule-authoring skill defines.\nThe rule file gets written, looks correct, and nothing happens — the\nbehavior it describes never fires, with no error, no warning, nothing in any\nlog pointing at the rule file at all.\n\n## Root cause\n\nA skill that defines a rule-file **format** is not the same as a mechanism\nthat **loads and dispatches** that format at runtime. Native Claude Code\nhooks are wired through `PreToolUse`\u002F`Stop`\u002F`SessionStart` entries in\n`settings.json` (project or global) or a plugin's `hooks.json` — a\ndeclarative rule-file convention is a separate, optional layer that only\nworks if something in that settings stack was specifically built to glob for\nthe rule-file pattern and read it. If no such loader exists, the rule-file\nskill only defines a *format*, not working automation, and authoring content\nin that format produces a file that looks configured but is functionally\ndead weight.\n\n## Fix\n\n**Before authoring any hook-rule-file content, grep the whole settings\nstack** for a reference to the rule-file glob\u002Floader:\n\n```bash\ngrep -ln '\u003Crule-glob>' .claude\u002Fsettings*.json ~\u002F.claude\u002Fsettings*.json 2>\u002Fdev\u002Fnull\ngrep -rln '\u003Crule-glob>' ~\u002F.claude\u002Fplugins --include='*.json' --include='*.py' --include='*.sh' --include='*.mjs'\n```\n\n(Or drop `--include` entirely.) A real dispatcher (e.g. hookify) keeps the\nrule glob in its Python hook scripts, not in `hooks.json`, so a search\nlimited to `hooks.json` reports \"no dispatcher\" wrongly.\n\nUse two commands: `--include` also filters the explicit `settings*.json`\narguments (verified on BSD grep), so a single combined command never reads\nthe settings files. zsh aborts on an unmatched glob (\"no matches found\"):\nrun the first command in bash, or `setopt nullglob` first.\n\n(Plugin hooks live at\n`~\u002F.claude\u002Fplugins\u002Fcache\u002F\u003Cmarketplace>\u002F\u003Cplugin>\u002F\u003Cversion>\u002Fhooks\u002Fhooks.json`,\nso a shallow `~\u002F.claude\u002Fplugins\u002F*\u002Fhooks.json` glob matches nothing and always\nreports \"no dispatcher\".)\n\nAlso confirm the plugin is listed under `enabledPlugins` in settings, and\ncount a hit only in the active version directory (cache keeps old\nversions).\n\n- If nothing loads the rule-file pattern, **do not author rule-file\n  content** expecting it to run. Implement the behavior as a native\n  `PreToolUse`\u002F`Stop`\u002F`SessionStart` entry in `settings.json` instead — the\n  pattern any working `guard-*.sh`-style hook script in the repo already\n  uses.\n- If a dispatcher *is* found, confirm it's actually wired into the active\n  settings (not just present in an example\u002Ftemplate file) before trusting\n  the rule-file format for anything that matters.\n\n## Evidence\n\nSession 0010: \"hookify rule-files (`.claude\u002Fhookify.*.local.md`) are inert in\nthis repo — no dispatcher is wired in project settings, global settings, or\nthe ecc plugin's `hooks.json` to read them (grepped; zero refs). So the\nreport's 'promote to hooks' recommendation was implemented as native\n`.claude\u002Fsettings.json` hooks.\"\n\n## Related skills\n\n- `hook-merge-base-diff-command-regex-anchoring` — a different hook-reliability\n  failure mode in the same neighborhood: hooks that DO fire but compute the\n  wrong result (diff range, command regex), rather than hooks that never fire\n  at all.\n","# Verify a Hook-Rule-File Mechanism Has a Dispatcher Before Authoring Rules\n\n## Symptom\n\nA compliance report recommends \"promote to hooks\" for a failing workflow\nstep. The obvious move is to write a declarative rule file (e.g.\n`.claude\u002Fhookify.*.local.md`) in the format a rule-authoring skill defines.\nThe rule file gets written, looks correct, and nothing happens — the\nbehavior it describes never fires, with no error, no warning, nothing in any\nlog pointing at the rule file at all.\n\n## Root cause\n\nA skill that defines a rule-file **format** is not the same as a mechanism\nthat **loads and dispatches** that format at runtime. Native Claude Code\nhooks are wired through `PreToolUse`\u002F`Stop`\u002F`SessionStart` entries in\n`settings.json` (project or global) or a plugin's `hooks.json` — a\ndeclarative rule-file convention is a separate, optional layer that only\nworks if something in that settings stack was specifically built to glob for\nthe rule-file pattern and read it. If no such loader exists, the rule-file\nskill only defines a *format*, not working automation, and authoring content\nin that format produces a file that looks configured but is functionally\ndead weight.\n\n## Fix\n\n**Before authoring any hook-rule-file content, grep the whole settings\nstack** for a reference to the rule-file glob\u002Floader:\n\n```bash\ngrep -ln '\u003Crule-glob>' .claude\u002Fsettings*.json ~\u002F.claude\u002Fsettings*.json 2>\u002Fdev\u002Fnull\ngrep -rln '\u003Crule-glob>' ~\u002F.claude\u002Fplugins --include='*.json' --include='*.py' --include='*.sh' --include='*.mjs'\n```\n\n(Or drop `--include` entirely.) A real dispatcher (e.g. hookify) keeps the\nrule glob in its Python hook scripts, not in `hooks.json`, so a search\nlimited to `hooks.json` reports \"no dispatcher\" wrongly.\n\nUse two commands: `--include` also filters the explicit `settings*.json`\narguments (verified on BSD grep), so a single combined command never reads\nthe settings files. zsh aborts on an unmatched glob (\"no matches found\"):\nrun the first command in bash, or `setopt nullglob` first.\n\n(Plugin hooks live at\n`~\u002F.claude\u002Fplugins\u002Fcache\u002F\u003Cmarketplace>\u002F\u003Cplugin>\u002F\u003Cversion>\u002Fhooks\u002Fhooks.json`,\nso a shallow `~\u002F.claude\u002Fplugins\u002F*\u002Fhooks.json` glob matches nothing and always\nreports \"no dispatcher\".)\n\nAlso confirm the plugin is listed under `enabledPlugins` in settings, and\ncount a hit only in the active version directory (cache keeps old\nversions).\n\n- If nothing loads the rule-file pattern, **do not author rule-file\n  content** expecting it to run. Implement the behavior as a native\n  `PreToolUse`\u002F`Stop`\u002F`SessionStart` entry in `settings.json` instead — the\n  pattern any working `guard-*.sh`-style hook script in the repo already\n  uses.\n- If a dispatcher *is* found, confirm it's actually wired into the active\n  settings (not just present in an example\u002Ftemplate file) before trusting\n  the rule-file format for anything that matters.\n\n## Evidence\n\nSession 0010: \"hookify rule-files (`.claude\u002Fhookify.*.local.md`) are inert in\nthis repo — no dispatcher is wired in project settings, global settings, or\nthe ecc plugin's `hooks.json` to read them (grepped; zero refs). So the\nreport's 'promote to hooks' recommendation was implemented as native\n`.claude\u002Fsettings.json` hooks.\"\n\n## Related skills\n\n- `hook-merge-base-diff-command-regex-anchoring` — a different hook-reliability\n  failure mode in the same neighborhood: hooks that DO fire but compute the\n  wrong result (diff range, command regex), rather than hooks that never fire\n  at all.\n",{"name":5,"description":7},"main","153711dd9432743d97f0b33b080ada5798ea623c","plugins\u002Fcore-workflow\u002Fskills\u002Fdeclarative-hook-rules-inert-without-dispatcher","https:\u002F\u002Fgithub.com\u002Fabhijitbansal\u002Fclaude-skills","https:\u002F\u002Fgithub.com\u002Fabhijitbansal","2026-11-07 12:59:51",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add abhijitbansal\u002Fclaude-skills --skill declarative-hook-rules-inert-without-dispatcher",{"tool":35,"command":36},"bunx","bunx skills add abhijitbansal\u002Fclaude-skills --skill declarative-hook-rules-inert-without-dispatcher",{"tool":38,"command":39},"pnpm","pnpm dlx skills add abhijitbansal\u002Fclaude-skills --skill declarative-hook-rules-inert-without-dispatcher","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fabhijitbansal\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fcore-workflow\u002Fskills\u002Fdeclarative-hook-rules-inert-without-dispatcher\u002FSKILL.md",true,[],[44,51,58,65,72,79],{"skillNo":45,"name":46,"nameZh":6,"description":47,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":48,"categories":49,"keywords":50,"publishedAt":18},"01M74XTV2V7GZM8FDBXQZZ74VX","second-wind","Orchestrate long unattended Claude Code runs across multiple repos with the wind CLI. Use when the user wants to run Claude Code overnight, resume sessions after the 5-hour usage limit, run Claude in many repos at once via tmux, or says \"set up second wind\", \"wind up\", \"overnight run\", \"resume after limit\", \"usage limit orchestrator\".","https:\u002F\u002Fgithub.com\u002Fabhijitbansal\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fsecond-wind\u002Fskills\u002Fsecond-wind\u002FSKILL.md",[],[],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":18},"01M74XTPGN1HDQSKGCZZX0AZPC","structured-output-adaptive-thinking-token-bloat","A Claude API call using output_config.format (json_schema structured outputs) with thinking:{type:\"adaptive\"} burns most of its output budget on thinking (observed ~21k of ~24k tokens) without improving JSON quality, making the run up to ~5x more expensive than the same call with thinking omitted — use when calling the Messages API with a json_schema output format for extraction, ranking, classification, or summarization tasks, or when a schema-constrained call's usage.output_tokens is far larger than the returned JSON.","https:\u002F\u002Fgithub.com\u002Fabhijitbansal\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprompt-craft\u002Fskills\u002Fstructured-output-adaptive-thinking-token-bloat\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M74XTKTRHAMC2JFHQ1P1E6GR","review","Apply a code-review lens to a diff, branch, or file — find correctness bugs, security issues, and quality problems, ranked by severity, with a concrete fix for each. Use when the user says \"review this\", \"review my diff\", \"check this PR\", \"look this over before I commit\", or \"is this safe\". Skip when the user wants the code written, not reviewed.","https:\u002F\u002Fgithub.com\u002Fabhijitbansal\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprompt-craft\u002Fskills\u002Freview\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M74XTGGCW7GWDDHPEMJQC7Y1","refresh","Rebuild the prompt-craft command registry and usage profile, and print a summary of installed commands and your personalized recommendations. Use when you install or update plugins and want the advisor to pick them up immediately, or say \"refresh prompt-craft\", \"rebuild the command registry\".","https:\u002F\u002Fgithub.com\u002Fabhijitbansal\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprompt-craft\u002Fskills\u002Frefresh\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M74XTCNGNR4G19P3Z95KTHQJ","refactor","Apply a refactoring lens — restructure code without changing behavior, guarded by tests that pass before and after. Use when the user says \"refactor\", \"clean this up\", \"extract this\", \"simplify this\", \"reduce duplication\", or \"make this readable\" on existing working code. Skip when the change is meant to alter behavior (that's a feature or a fix).","https:\u002F\u002Fgithub.com\u002Fabhijitbansal\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprompt-craft\u002Fskills\u002Frefactor\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M74XT9FKXN3N106G7Q3X56XR","plan","Decompose a non-trivial task into an explicit, tracked plan with goals and per-step acceptance criteria before writing code. Use when the user says \"plan this\", \"break this down\", \"what's the plan\", or asks for a multi-step feature\u002Frefactor that touches more than one file. Pairs with plan mode. Skip for single-edit changes that need no decomposition.","https:\u002F\u002Fgithub.com\u002Fabhijitbansal\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprompt-craft\u002Fskills\u002Fplan\u002FSKILL.md",[],[]]