Detailed Analysis
A Reddit user's question about why custom Claude skills built in Claude Code fail to appear on the Claude iPhone app highlights a meaningful gap in Anthropic's cross-platform skill portability infrastructure. The user built custom skills within Claude Code — Anthropic's CLI-based development environment — and found that those skills were not discoverable or executable when switching to the mobile app. The attached image suggests the user is encountering a straightforward "skill not found" error, a symptom of the underlying architectural reality that skill environments in Claude Code and Claude.ai (including the mobile client) are not yet automatically synchronized.
The root cause lies in how Claude skills are currently stored and invoked. Skills built in Claude Code live locally as folders containing YAML frontmatter, markdown instructions, and scripts on the developer's machine. The Claude.ai platform — including its iPhone app — operates as a cloud-based interface that draws from a separate skills registry configured through the web dashboard under **Customize > Skills**. Because these two ecosystems do not yet share a live sync layer, a skill that exists on a local desktop environment is effectively invisible to any session initiated through the mobile or web client. A GitHub feature request specifically targeting bidirectional syncing between Claude.ai's web interface and Claude Code confirms this is a known, unresolved limitation, not a user error.
The practical workaround available to this user involves manually porting the custom skill to the Claude.ai platform. This requires packaging the skill as a ZIP archive — preserving the proper folder structure with its YAML and markdown files — and uploading it through the **Customize > Skills > + Create skill > Upload a skill** pathway in the Claude.ai web interface. Once uploaded to the cloud-side registry, the skill becomes accessible to Claude across web and mobile sessions. Community-developed tools, such as the "Skill Sync Claude Skill" script, offer a more automated approach for users managing large skill inventories, enabling scanning, diffing, and merging between local Code repositories and cloud skill-vaults in a structured workflow.
Anthropic announced Agent Skills as an open standard for cross-platform portability in December 2025, explicitly framing the feature around dynamic skill discovery, loading, and usage across Claude.ai, Claude Code, the Agent SDK, and the Developer Platform. However, the announcement also acknowledged that full lifecycle management — including creating, editing, sharing, and syncing — represents upcoming rather than currently shipped functionality. This gap between the stated vision and the present user experience is consequential: developers investing time in building sophisticated local skill libraries reasonably expect those assets to travel with them across devices and interfaces, and the current manual portability requirement creates friction that undermines that expectation.
The broader trend at play is the industry-wide challenge of making AI agent capabilities genuinely portable across fragmented execution environments. As AI tooling matures, the boundary between local developer environments and cloud-hosted consumer interfaces is becoming a critical UX fault line. Anthropic's open standard framing for Agent Skills signals an intent to treat skills as first-class, platform-agnostic resources — analogous to how browser extensions or mobile apps are distributed through centralized stores — but the infrastructure to fully realize that vision remains in progress. Until automatic bidirectional syncing ships, users bridging Claude Code and the mobile app should treat the Claude.ai web dashboard as the canonical skills registry and upload any locally developed skills there to ensure consistent cross-platform availability.
Read original article →