Org-admin-managed skills (Claude.ai org settings) don't appear in Claude Code CLI

Status Open
Maintainer reply None cached
Activity 0 comments · opened Jul 29, 2026

Description

Skills configured at the Claude.ai organization/admin level are visible and usable in the Claude Desktop app, but do not appear in Claude Code CLI's available-skills list at all, even when logged into the same account on the same machine.

Current CLI skill sources (confirmed working): personal ~/.claude/skills/, project .claude/skills/, plugin-provided skills via enabledPlugins/extraKnownMarketplaces, and manually-configured skillDirectories pointing at a local git checkout.

Gap: none of these map to org-admin-managed skills. Server-managed settings for Claude Code (Admin Settings > Claude Code > Managed settings) currently support permissions, hooks, env vars, and MCP servers — skills aren't part of that distribution mechanism yet.

Impact: teams that centrally manage skills via Claude.ai org settings (e.g. a shared brand/design-system skill, internal conventions) have no way to make those available to engineers using Claude Code CLI, only Desktop/web. The only workaround is manually re-creating the skill as a local SKILL.md in a git repo and having each engineer add it via skillDirectories — which loses the "managed centrally by an org admin" property entirely.

Request: extend server-managed settings (or an equivalent sync mechanism) to distribute org-admin-configured skills to Claude Code CLI, the same way they already reach Claude Desktop.

View original on GitHub ↗