I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.
Verify Feature Scope
I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.
Problem Description
I tried setting up a git-sync sidecar to automatically pull skills from our internal repo (structured as Claude Code skills under .claude/skills/) and push them into OpenWebUI via /api/v1/tools/create. It failed because OpenWebUI Tools require a specific Python structure (class Tools with typed methods), while Claude Code skills are regular Python CLI scripts with a completely different structure
Desired Solution you'd like
A compatibility layer or adapter that allows importing Claude Code skills (.claude/skills/ format) directly as OpenWebUI Tools, either by auto-wrapping the scripts into a class Tools structure, or by supporting a looser import format that accepts arbitrary Python scripts.
Alternatives Considered
No response
Additional Context
Teams already using Claude Code skills in their repos shouldn't have to rewrite everything to a different format just to reuse them in OpenWebUI. Supporting this would make it much easier to share tooling across both Claude Code and OpenWebUI workflows.
Originally created by @aimendenche-nw on GitHub (Mar 30, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/23221
### Check Existing Issues
- [x] I have searched for all existing **open AND closed** issues and discussions for similar requests. I have found none that is comparable to my request.
### Verify Feature Scope
- [x] I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.
### Problem Description
I tried setting up a git-sync sidecar to automatically pull skills from our internal repo (structured as Claude Code skills under .claude/skills/) and push them into OpenWebUI via /api/v1/tools/create. It failed because OpenWebUI Tools require a specific Python structure (class Tools with typed methods), while Claude Code skills are regular Python CLI scripts with a completely different structure
### Desired Solution you'd like
A compatibility layer or adapter that allows importing Claude Code skills (.claude/skills/ format) directly as OpenWebUI Tools, either by auto-wrapping the scripts into a class Tools structure, or by supporting a looser import format that accepts arbitrary Python scripts.
### Alternatives Considered
_No response_
### Additional Context
Teams already using Claude Code skills in their repos shouldn't have to rewrite everything to a different format just to reuse them in OpenWebUI. Supporting this would make it much easier to share tooling across both Claude Code and OpenWebUI workflows.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @aimendenche-nw on GitHub (Mar 30, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/23221
Check Existing Issues
Verify Feature Scope
Problem Description
I tried setting up a git-sync sidecar to automatically pull skills from our internal repo (structured as Claude Code skills under .claude/skills/) and push them into OpenWebUI via /api/v1/tools/create. It failed because OpenWebUI Tools require a specific Python structure (class Tools with typed methods), while Claude Code skills are regular Python CLI scripts with a completely different structure
Desired Solution you'd like
A compatibility layer or adapter that allows importing Claude Code skills (.claude/skills/ format) directly as OpenWebUI Tools, either by auto-wrapping the scripts into a class Tools structure, or by supporting a looser import format that accepts arbitrary Python scripts.
Alternatives Considered
No response
Additional Context
Teams already using Claude Code skills in their repos shouldn't have to rewrite everything to a different format just to reuse them in OpenWebUI. Supporting this would make it much easier to share tooling across both Claude Code and OpenWebUI workflows.