{"version":"2.1.319","anchor":"bridge-uploads-refuse-skillmd-files-claudeai-would-not-sav","canonical_anchor":"bridge-uploads-refuse-skillmd-files-claudeai-would-not-sav","heading":"Skill files claude.ai would not save can be refused before upload","tier":"notice","area":"Skills","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/bridge-uploads-refuse-skillmd-files-claudeai-would-not-sav","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Skill files claude.ai would not save can be refused before upload\n\nBehind tengu_sorted_thimble, SKILL.md or .skill attachments that claude.ai would refuse to save are not sent, with an error saying why\n\n**Unclear.** It is not clear when this check is switched on.\n\n**What**\n\nA skill is a packaged set of instructions Claude can use, stored in a `SKILL.md` or `.skill` file. When Claude Code sends attachments to claude.ai through its bridge (the link between your terminal and claude.ai), it can now hold back a skill file that claude.ai would refuse to save as a skill.\n\n- With the new `refuseUnsaveableSkills` option, such a file is not sent, and the upload error says: \"not sent: claude.ai would refuse to save it as a skill\".\n\n- The option is passed to the attachment and caption flow, and is set only when a helper check returns true and the server switch `tengu_sorted_thimble` is on. The built-in fallback for that switch is false.\n\nNothing has been read about `tengu_sorted_thimble`, so whether it is on for anyone is unknown.\n\n**Why**\n\nWhere the guard is active, a skill file that would have failed on claude.ai is stopped early with a clear reason, instead of being uploaded and then rejected.\n\n- Area: Skills\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}