"Save skill" button does nothing when clicking a packaged .skill file card

Status Open
Maintainer reply None cached
Activity 0 comments · opened Sep 17, 2026

Environment:

  • OS: Windows 11 Home (10.0.26200)
  • Claude Code / Claude desktop app, Cowork-adjacent build (paths reference local-agent-mode-sessions)

Steps to reproduce:

  1. In a Claude Code session, use the skill-creator skill to build and package a new skill (python -m scripts.package_skill <skill-folder>), producing a .skill file.
  2. Send the resulting .skill file to the user as a file attachment.
  3. In the chat UI, click the Save skill button on that file card.

Expected behavior: The skill installs into the user's profile and becomes available in future conversations (per skill-creator's own documented behavior: "The presented .skill file card shows a Save skill button... clicking it installs the skill into their profile").

Actual behavior: Clicking "Save skill" produces no visible effect -- no confirmation, no error, and the skill does not appear in the available-skills list in a new conversation.

Additional detail that may be related: During the same session, the assistant manually extracted the packaged .skill file directly into the local skills directory as a workaround:
C:\Users\<user>\AppData\Roaming\Claude\local-agent-mode-sessions\skills-plugin\<org-id>\<user-id>\skills\<skill-name>\
This worked temporarily, but the entire directory was silently wiped/reset back to only the pre-existing bundled skills at least twice over the course of the session, with no user action in between. This suggests something is periodically resyncing or resetting that directory from a different source of truth, which may be the same underlying issue causing "Save skill" to silently fail.

Impact: Users cannot reliably persist custom skills created via skill-creator across sessions.

View original on GitHub ↗