{"version":"2.1.248","anchor":"skill-saving-guidance-split-into-three-session-specific-form","canonical_anchor":"skill-saving-guidance-split-into-three-session-specific-form","heading":"Skill-saving guidance split into three session-specific forms","tier":"notice","area":"Skills","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/skill-saving-guidance-split-into-three-session-specific-form","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Skill-saving guidance split into three session-specific forms\n\nSaving a skill now varies by session: save tool, propose only, or delivered as a file.\n\n**What**\n\nThe instructions Claude follows when you ask it to save a skill now come in three variants: one pointing at a save tool, one saying skills cannot be created in this session and to propose one instead, and one saying to deliver the skill as a `.skill` zip or a single `SKILL.md` file, with an explicit note that Claude never learns whether you saved it and must report the skill as delivered rather than saved.\n\n**Details**\n\n- All three state that skill files on disk, including synced copies of your account skills, are a read-only cache and must not be edited in place.\n- A fourth fragment carves out skills owned by plugins.\n\n**Evidence**\n\n`You get no signal whether they saved it: report the skill as delivered, never as saved.`\n\n- Area: Skills\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}