{"version":"2.1.282","anchor":"synced-skills-classified-as-anthropic-or-account-from-the-se","canonical_anchor":"synced-skills-classified-as-anthropic-or-account-from-the-se","heading":"Synced skills now use the server's creator type to decide where they came from","tier":"internal","area":"Skills","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/synced-skills-classified-as-anthropic-or-account-from-the-se","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Synced skills now use the server's creator type to decide where they came from\n\nSkills synced from the server now carry creatorType, which decides whether a skill counts as Anthropic's or the account's\n\n**Unclear.** It is not clear where this origin is shown to users.\n\n**What**\n\nSkills are packaged instructions Claude can load for particular tasks. Some are synced from the server rather than stored on your machine. Skill records from the server now carry a creator type.\n\n- The server's `creator_type` is copied to `creatorType`. The value \"anthropic\" stays \"anthropic\", and any other value becomes \"user\".\n\n- Whether a synced skill counts as \"anthropic\" or \"account\" is now decided from this field.\n\n- The older check, which compared the skill's source name against names such as \"anthropic\" and \"anthropic-example\", is now only used when the field is missing.\n\n**Why**\n\nSkills should show the right origin when the server says who made them, so skills written by Anthropic can be told apart from ones created on your account, instead of relying on the name of the place they came from.\n\n- Area: Skills\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}