{"version":"2.1.323","anchor":"forked-skill-failures-now-surface-as-errors","canonical_anchor":"forked-skill-failures-now-surface-as-errors","heading":"Failed forked skills are now reported as failures","tier":"notice","area":"Skills","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/forked-skill-failures-now-surface-as-errors","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Failed forked skills are now reported as failures\n\nWhen a skill run in a separate forked process ends in an error, Claude Code now reports it as failed with an error message instead of a success\n\n**What**\n\nA skill is a packaged set of instructions Claude Code can run, and a forked skill runs separately from the main conversation. Previously, a forked skill was always reported to the model as successful, even when it ended in an error. Now, when it ends in an error state, the result is marked as failed and carries an error message describing what went wrong.\n\n**Why**\n\nThe model no longer treats a broken skill run as if it worked, so it can notice the failure and react to it.\n\n- Area: Skills\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}