Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.274 ·

Artifact and skill publishing can now set a content type per file

Artifact and skill file entries can now be an object specifying a source path and content type, not just a plain path string

Group of 2 Use it now New Features
JSON All of v2.1.274
Use it nowTier: how much it should matter to you
3Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
New FeaturesKind: in v2.1.274,
What probably matters to youSection of the release

What

When creating or publishing an Artifact or Skill, the files map used to only accept a plain path string for each file. It now also accepts an object with a from field (the source path) and a contentType field, letting a publish call specify a MIME/content type per uploaded file instead of only where it comes from.

The internal handler that admits these files, checking things like path traversal and size limits, was updated to read the source path from from when a file entry uses this new object form, rather than assuming it's always a bare string.

Why

This lets publishers control the content type of individual uploaded files (for example, forcing a file to be treated as plain text or a specific format) rather than relying on automatic detection.

Read from
Names in the bundlecontentType
What the documentation says
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up contentType, on skills-guide. .contentType("text/markdown") build-with-claude/skills-guide see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up contentType, on skills-guide.

See this entry in the whole of v2.1.274 →

Feedback