Feature: Better skill management and skill usability in OpenGUI

[touch2be]

Feature Request

Skills in OpenGUI should not only be displayed, but should be much easier to manage and use directly inside the GUI.

Requested Improvements

1. Create skills directly in OpenGUI

Users should be able to create new skills from within OpenGUI without having to leave the app or edit files manually.

2. View skill details

It should be possible to open and inspect existing skills directly in the UI, including their content, purpose, and configuration.

3. Edit existing skills

Users should be able to modify skills directly in OpenGUI, for example to improve prompts, instructions, descriptions, or behavior.

4. Select skills directly in chat

For usability, it would be very helpful if skills could be selected directly inside the chat UI instead of always having to type them manually.

For example:

• skill picker in the chat input area
• quick-select menu
• attach/activate skill with one click

Why

• Makes skills much more accessible for non-technical users
• Reduces friction compared to manual editing or remembering command syntax
• Encourages more frequent use of skills
• Makes OpenGUI feel more like a complete workspace instead of just a viewer for existing skills

Expected Behavior

• Skills can be created, viewed, and edited from within OpenGUI
• Skills can be selected or attached in the chat with minimal typing
• The overall workflow for using skills becomes faster and more intuitive

Possible UX Ideas

• Dedicated Skills section in settings or sidebar
• Skill editor modal or panel
• Inline skill picker in the chat composer
• Recently used or favorite skills for faster access

Environment

• OpenGUI Desktop Interface

[touch2be]

Additional Idea: Default Skills & First-Launch Setup

Building on the skill creator concept above — it's worth discussing whether a Skill Creator skill should be a built-in default skill that ships with OpenGUI.

Proposal: First-Launch Skill Selection

On the first start of the app, OpenGUI could present a setup screen where users can choose which standard skills to install:

• A curated list of pre-built skills is shown (e.g. Skill Creator, Code Reviewer, Writing Assistant, etc.)
• The user selects the ones they want with a checkbox
• Selected skills are installed/activated automatically
• This can be skipped and done later via Settings

Why Make Skill Creator a Default Skill?

• New users often don't know skills exist or how to create them
• Bundling a Skill Creator skill lowers the barrier significantly — users can create their own skills without leaving the app
• It makes the skill ecosystem self-sustaining from day one

UX Sketch

┌──────────────────────────────────────────┐
│  Welcome to OpenGUI!                     │
│  Choose your starter skills:             │
│                                          │
│  ☑ Skill Creator    – Create new skills  │
│  ☑ Code Reviewer    – Review your code   │
│  ☐ Writing Assistant – Improve writing   │
│  ☐ SEO Optimizer    – Optimize content   │
│                                          │
│  [Skip]              [Install & Start →] │
└──────────────────────────────────────────┘

This approach is similar to how VS Code handles extension recommendations or how apps like Notion suggest templates on first launch.

[akemmanuel]

Implemented in newest version.