claude-code - 💡(How to fix) Fix [FEATURE] User skill library sync between Claude Desktop and claude.ai web/mobile

Preflight Checklist

• I have searched existing requests and this feature hasn't been requested yet
• This is a single feature request (not multiple features)

Problem Statement

Feature Request Claude Desktop / Web Parity User skill library sync between Claude Desktop and claude.ai web/mobile

Summary

User-defined skills installed via Claude Desktop are not available in claude.ai web or mobile sessions. There is currently no mechanism to sync or register user skills to Anthropic's backend so they persist across environments. This creates a meaningful productivity gap for users who rely on a custom skill library as part of their professional workflow.

User context

I am a professional user with an established Claude Desktop workflow spanning multiple workstreams. I have built a library of user skills that encode organization-specific standards — prompt caching architecture, project governance, pricing methodology, and domain-specific reference data. These skills are installed in Claude Desktop and trigger automatically to enforce consistent practices across all AI-assisted work.

My primary environment is Claude Desktop, but I regularly work on third-party hardware where Desktop is not available. In those sessions — on web or mobile — none of my user skills are present. I must either reconstruct context manually or accept degraded output quality relative to my Desktop sessions.

The gap

Claude Desktop — user skills at /mnt/skills/user/ are available and trigger automatically. Full skill library present.

claude.ai web / mobile — available_skills is populated from Anthropic's backend only. No user skills. No sync mechanism exists.

Requested capability

A mechanism to register user-defined skills to Anthropic's backend so they appear in available_skills across all surfaces — Desktop, web, and mobile — for the authenticated user account.

Acceptable implementation forms, in order of preference:

Automatic sync from Claude Desktop to account-level skill registry on install Manual upload of .skill files via claude.ai settings A skills management page in account settings where skills can be uploaded, toggled, and versioned Current workarounds and their limitations

Claude Project knowledge

SKILL.md files can be uploaded as Project knowledge documents. They are available within that Project but require manual reference — they do not auto-trigger via the available_skills mechanism and must be loaded explicitly per session.

Session primers

Key standards can be pasted into session openers manually. Does not scale across a multi-skill library and reintroduces exactly the context-reconstruction burden that skills are designed to eliminate.

Restricting work to Desktop

Functionally constrains the user to a single device and prevents mobile or third-party hardware use for any skill-dependent work.

Submitted via

Claude Desktop — claude.ai feedback channel — May 2026

Proposed Solution

equested capability

A mechanism to register user-defined skills to Anthropic's backend so they appear in available_skills across all surfaces — Desktop, web, and mobile — for the authenticated user account.

Acceptable implementation forms, in order of preference:

Automatic sync from Claude Desktop to account-level skill registry on install Manual upload of .skill files via claude.ai settings A skills management page in account settings where skills can be uploaded, toggled, and versioned

Alternative Solutions

Current workarounds and their limitations involve restricting work to Claude Desktop, which is limitiing, or creating a Project to house all skills and populate them manually to the web UI when using it. Neither is optimal.

Priority

High - Significant impact on productivity

Feature Category

Other

Use Case Example

I maintain a library of multiple user skills installed in Claude Desktop that encode organization-specific standards designed to optimize efficiency and standardize projects. These skills trigger automatically when relevant work begins, ensuring consistent application of firm standards across all AI-assisted sessions without manual setup. When I travel or work on a client's hardware where Claude Desktop is not installed, I use claude.ai in a browser. In those sessions, none of my skills are present. This places the burden of manually optimizing Claude and standardizing project setup and maintenance on me, rather than on the AI where I intend it to reside. It also renders the skill library less valuable overall since it is not universally accessible.

Additional Context

No response