›_ Claude Code Issues
Claude Code Issues / #68071

[FEATURE] Claude Code sessions cannot publish/update skills to the account Skills store - expose the Chat surface's "Save skill" flow

Open 💬 2 comments Opened Jun 12, 2026 by dannybyrnes

Problem

Custom skills now live in the account-level cloud Skills store, and the Chat/Cowork surface has a first-class publish loop: the agent edits a skill, the chat renders a skill card, and the user clicks Save skill -> Upload and replace. Done.

Claude Code desktop sessions have no equivalent. The model can READ materialized cloud skills (skills-plugin cache) and prepare an updated SKILL.md, but has no path to publish it:

  • No present_files / skill-card tool in the Claude Code toolset, so the desktop client never renders a Save-skill card.
  • The Skills page upload dialog requires the OS file picker (not automatable, by design).
  • Driving claude.ai/customize/skills via Claude-in-Chrome reaches the page's file input, but file_upload (correctly) only accepts user-attached files - agent-staged paths are rejected.
  • Filesystem skills don't appear on the Skills page at all (#43095), so there's no "promote local skill to cloud" path either.

Net effect: a Claude Code session that learns something worth folding into a skill must hand off to a separate Chat conversation (e.g. via the skill's "Edit with Claude") just for the final publish click - a full context switch, and the Chat agent re-does an edit the Code session already made, for what is one click on the other surface.

User story

A heavy Claude Code user maintains ~12 custom skills (consulting dev workflows) in the cloud store so colleagues receive live-updated shares. Standing instruction to Claude: every "remember this" should also update the matching skill. Today that means: Claude Code drafts the new SKILL.md -> stages a file -> user opens Chat -> pastes a hand-off prompt -> Chat re-applies the edit -> user clicks Save skill -> confirms replace. Two agents, two contexts, one edit.

Request

Expose the skill publish/update primitive to Claude Code desktop sessions - any of:

  1. present_files (or a dedicated save_skill tool) wired to the same Save-skill card the Chat client already renders, or
  2. a "Save as skill / Replace existing skill" affordance on .skill files produced inside a Claude Code session, or
  3. an authenticated local-harness API to upsert an account skill, keeping the same replace-confirmation UX.

Related

#43095 (filesystem skills invisible on the Skills page), #46836 / #46844 (Save-and-Replace staleness), #50041 (present_files file access).

Environment: Claude Code desktop app, macOS, account-level skills (2026-06-12).

🤖 Generated with Claude Code

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗