{"version":"2.1.283","anchor":"function-hooks-authoring-skill-rewritten-as-make-a-mod","canonical_anchor":"function-hooks-authoring-skill-rewritten-as-make-a-mod","heading":"The built-in skill for writing hook plugins is now framed as \"Make a mod\"","tier":"notice","area":"Mods","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/function-hooks-authoring-skill-rewritten-as-make-a-mod","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### The built-in skill for writing hook plugins is now framed as \"Make a mod\"\n\nThe bundled skill for writing function-hook plugins is now described as making mods such as live panes, bands, status lines and toasts, with example files\n\n**Unclear.** What decides whether the \"plugin-authoring\" bundle is available is not known.\n\n**What**\n\nClaude Code ships with a skill for writing plugins made of function hooks. A skill is a packet of instructions that Claude can load when it needs them. A function hook is code that runs inside Claude Code and changes what it shows or does. The skill has a new description and new menu text, and both now talk about \"mods\". Its menu entry reads \"Write a mod: a live pane, view or behaviour change in Claude Code\". Its description covers:\n\n- live panes\n\n- bands\n\n- status lines\n\n- toasts, which are short pop-up notices\n\n- hooks, in the terminal or in the desktop app's Code tab, which reload live in the current session\n\nThe skill also ships with its own files:\n\n- `examples\/pane.tsx`\n\n- `examples\/band.tsx`\n\n- `reference.md`\n\n- generated type declarations\n\nIt now sits in a \"plugin-authoring\" bundle.\n\n**Why**\n\nClaude reads a skill's description to decide when to load it. A new description therefore changes when Claude reaches for this skill, for example when you ask it to build a pane or a status line.\n\n- Area: Mods\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 4\/5"}