{"version":"2.1.312","anchor":"artifact-publish-grant-adds-extra-tools","canonical_anchor":"artifact-publish-grant-adds-extra-tools","heading":"Artifact publishing: a wider tool grant and a stricter design-skill check","tier":"notice","area":"Artifacts","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/artifact-publish-grant-adds-extra-tools","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Artifact publishing: a wider tool grant and a stricter design-skill check\n\nGranting artifact publishing now adds more tools, and publishing now requires the design skill specifically rather than either of two skills\n\n**Unclear.** Which extra tools are allowed is not stated.\n\n**What**\n\nArtifacts are items Claude can publish from a session. Two parts of publishing changed.\n\n- Tool grant: when `artifactPublishGranted` is set, Claude Code used to add one tool to the allowed and permission lists. It now adds that tool plus a further set built from two other lists.\n\n- Skill check: a skill is a packaged set of instructions Claude can load. The publish check that returns `design_skill_not_loaded` now looks only for the design skill. Before, loading either of two skills cleared it, and loading the alternative skill no longer does.\n\n- The message still reads \"Load the ... skill first\".\n\n**Why**\n\nSessions allowed to publish artifacts get more tools to work with. Publishing is refused unless the design skill itself is loaded, so a session that relied on the other skill now has to load the design skill first.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}