Feature Request: API for syncing skills between Claude Code and Claude Chat/Projects

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