mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-06 02:48:13 -05:00
[GH-ISSUE #21341] feat: skills support #19448
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#19448
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @tjbck on GitHub (Feb 12, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/21341
@Classic298 commented on GitHub (Feb 12, 2026):
@Bickio commented on GitHub (Feb 17, 2026):
Feature request to consider: Attaching tools to skills, so they auto-enable when the skill is loaded
@gaby commented on GitHub (Feb 23, 2026):
Feature Request: Import/sync skills from a Git/HTTP endpoint.
I currently host a local copy of https://github.com/anthropics/skills. It would be nice to be able to import/sync skills in Open-WebUI from a Git or HTTP source.
Currently, each item needs to be created manually. When updates occur, I must manually update each item individually.
@TomTheWise commented on GitHub (Feb 24, 2026):
Small feature request:
Make skills management similar to prompt management - maybe without the history of it’s not seem worth it. Readonly prompts can be opened by users and while they can’t make changes, they can read and select/copy the text.
For skills currently they can’t be opened on the gui if you don’t have write permissions. So users can’t look into it.
@EXONIL commented on GitHub (Mar 13, 2026):
Would love to see multi-file skills with references in a main file!
+1 for import from git, but I feel like sync absolutely should be toggleable, or a deliberate user action, having seen some of the issues with hidden HTML comments in skill MD files, resulting in unexpected or harmful prompt injection.
@Baronco commented on GitHub (Mar 17, 2026):
About "Attaching tools to skills, so they auto-enable when the skill is loaded" Is this being considered for the future? Has anything been developed in the dev branch yet? It would be really interesting to be able to attach the tools to the skills :O
@Simon-Stone commented on GitHub (Mar 20, 2026):
Being able to see the Skill's actual contents would be an important security feature to avoid prompt injection.
@glowzz commented on GitHub (Apr 2, 2026):
complete skills support with folds of scripts template and resources