claude-code - 💡(How to fix) Fix Feature Request: API for syncing skills between Claude Code and Claude Chat/Projects [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#47968Fetched 2026-04-15 06:37:11
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
Participants
Timeline (top)
labeled ×3

Error Message

There is no programmatic way to keep these in sync. When a skill is updated in the git repo, the only way to update the Claude Chat version is to manually copy-paste through the UI. This is error-prone and doesn't scale for teams managing multiple skills.

RAW_BUFFERClick to expand / collapse

Problem

Teams that use both Claude Code and Claude Chat/Projects (e.g., technical writing teams) currently maintain duplicate copies of skills — one as SKILL.md files in a git repo for Claude Code, and another manually managed through the Claude.ai web UI for Claude Chat/Projects.

There is no programmatic way to keep these in sync. When a skill is updated in the git repo, the only way to update the Claude Chat version is to manually copy-paste through the UI. This is error-prone and doesn't scale for teams managing multiple skills.

Proposed Solution

Provide an API (or extend the existing API) to:

  1. List/read/update Project custom instructions and knowledge files — so skills maintained in git can be pushed to Claude Projects programmatically
  2. Sync skills between Claude Code and Claude Chat — a shared skill format or registry that both surfaces can read from, so a skill defined once works everywhere
  3. At minimum, a Projects API for CRUD operations — allowing tools like Claude Code, CI/CD pipelines, or custom scripts to update Project contents

Use Case

Technical writers and other semi-technical teams often:

  • Use Claude Code for repo-based work (documentation linting, style guides, review personas)
  • Use Claude Chat/Projects for ad-hoc work with the same skills
  • Maintain skills in a shared git repo that the whole team pulls from

Today, the Claude Code → Claude Chat direction has no automation path. An MCP server can partially bridge Claude Desktop, but Claude.ai Projects remain completely manual.

Who Benefits

  • Technical writing teams straddling code and content workflows
  • Teams using Claude across multiple interfaces who want consistent behavior
  • Anyone maintaining reusable prompts/skills across Claude surfaces

extent analysis

TL;DR

Implementing an API to sync skills between Claude Code and Claude Chat/Projects is the most likely fix to address the issue of maintaining duplicate copies of skills.

Guidance

  • Identify the specific API endpoints required to list, read, and update Project custom instructions and knowledge files, as well as sync skills between Claude Code and Claude Chat.
  • Determine the feasibility of creating a shared skill format or registry that both surfaces can read from, to enable a skill defined once to work everywhere.
  • Explore the possibility of using existing tools like CI/CD pipelines or custom scripts to update Project contents programmatically, if a Projects API for CRUD operations is not available.
  • Consider the potential benefits of integrating an MCP server to bridge the gap between Claude Desktop and Claude.ai Projects.

Example

No code snippet is provided as the issue does not contain specific technical details or code references.

Notes

The proposed solution requires significant development and API changes, which may take time to implement. Additionally, the issue highlights the need for a programmatic way to keep skills in sync, but does not provide information on the current technical infrastructure or constraints.

Recommendation

Apply a workaround by exploring existing tools and scripts that can automate the process of updating Project contents, until a formal API is developed to sync skills between Claude Code and Claude Chat/Projects. This is because the issue emphasizes the need for automation, and using existing tools can provide a temporary solution.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING