Claude Skills leaves beta at /v1/skills, and the release discipline stays yours

Versioning by full re-upload is the detail that decides how much a change costs. Creating a skill uploads the complete file set, and a new version means resending all of those files against the existing skill id ^[17]. The write-up describes no patch route, so a one-line clarification in a description ships the same payload as a rewrite, bounded only by the 30 MB uncompressed ceiling on uploaded content ^[9][20].

Identity is the other half of the problem. Versions are first-class resources with their own endpoints, which is what makes a skill addressable from a pipeline at all ^[13]. The readable naming, though, lives on the side you do not control: Anthropic-managed skills use short ids such as pptx, xlsx, docx and pdf, with date-based versions like 20251013 ^[10]. Custom skills are uploaded by you, scoped to your workspace, and handed generated ids of the form skill_01AbCdEfGhIjKlMnOpQrStUv ^[11]. No equivalent convention exists on your own artifacts, so the map from a commit to a skill version is a record your build system keeps or nobody does ^[21].

That is where the recommended tooling pattern gets uncomfortable. The write-up models the flow in Apidog as one folder of six saved requests driven by skill_id and skill_version variables, so moving a version between development and production is a variable change rather than an edit to requests ^[18]. Convenient, and also a reminder that the two environments hold different objects: an identical brand-report folder uploaded into two workspaces is two skills with two ids ^[19][22]. dev.to lists workspace scoping and snapshot versioning among the things general availability did not settle, and a stable endpoint does not change that ^[4].

What did land is worth having. A skill is a folder with SKILL.md at its root, name and description in the frontmatter, scripts and templates around it ^[5]; Claude loads the instructions only when a task calls for them and runs the bundled scripts in its sandbox ^[6]. The frontmatter rules are strict enough to fail a build early: name capped at 64 characters, lowercase letters, digits and hyphens only, no XML tags, and anthropic and claude reserved ^[7], description non-empty and under 1024 characters, optional display_name up to 255 ^[8]. Outputs such as a deck or a filled spreadsheet come back through the Files API, which reached general availability in the same release ^[15]. The same API is also callable through Microsoft Foundry rather than the Claude API alone ^[14].

According to dev.to, that release arrived on 20 August 2026 alongside computer use, a new browser tool and the Files API, positioned as the production stack for building agents on the Claude Platform ^[1][3]. Positioning is not delivery. What shipped is smaller and more useful than the phrase: an endpoint that will not move under a pipeline, and validation that rejects a bad bundle before Claude ever loads it.