{"version":"2.1.280","anchor":"skill-delivery-prompt-now-conditions-the-save-instructions-o","canonical_anchor":"skill-delivery-prompt-now-conditions-the-save-instructions-o","heading":"Claude no longer tells users outright to save a file as a skill","tier":"internal","area":"Skills","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/skill-delivery-prompt-now-conditions-the-save-instructions-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Claude no longer tells users outright to save a file as a skill\n\nSystem prompt now says skill-saving depends on org settings Claude can't see, and to never instruct users to save\n\n**What**\n\nWhen Claude hands a file to the user that they might want to keep as a skill (a reusable, packaged set of instructions), rather than saving or proposing it directly, the system prompt's guidance now explains that whether the user can save it as a skill (from the file card, or by uploading it themselves) depends on their organization's settings, which Claude cannot see. Claude is told never to instruct the user outright to save the file as a skill.\n\n**Why**\n\nSince organizations can restrict skill-saving in ways Claude has no visibility into, this keeps Claude from confidently giving instructions that might not apply to a given user's setup.\n\n- Area: Skills\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}