[REQUEST] UI: Make Skills a top-level sidebar resource, like Knowledge bases

オープン
  • 何か問題がありますか？
#8,018 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
52/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
react, typescript
領域
frontend

調査の方向性

Start by tracing the sidebar's additionalActivePaths, the Skills page's IntegrationTabsHeader, and RESOURCE_MENU_ORDER, then follow the /skills routes and legacy ?skillId= redirect. Check the existing Knowledge bases, Tables, and Files resource flows for the corresponding entry points. Done means Skills has matching sidebar, flyout, list, Chat, search, row-action, permission, and backward-compatibility behavior without Integrations highlighting it.

索引モデルが issue の本文から書いたものです。

説明

feature

Is your feature request related to a problem? Please describe.

Finding and managing skills can be frustrating because they’re hidden as a tab within the Integrations section. Skills are content my team writes to shape how agents behave, so they're much closer to a Knowledge base than to an external service. Because of where they sit today:

  • Hard to find. New builders don't expect Skills under Integrations, and many never learn the feature exists.
  • Wrong mental model. Integrations are services you connect with credentials. Putting Skills next to them suggests a Skill is a kind of connector.
  • Confusing active state. On /skills, the sidebar highlights Integrations, so it's unclear where you are.
  • Missing features other resources have. Tables and Files get rail flyouts and appear in the + / @ resource menus in Chat. Skills get neither.

Describe the solution you'd like

Move Skills into the workspace resources section of the sidebar and give it the same UX as Knowledge bases.

  • Sidebar entry: add a Skills nav item with its own icon, after Knowledge bases: Tables · Files · Knowledge bases · Skills · Logs. It's active on every /skills/* route, and Integrations is no longer highlighted there.
  • Rail flyout: in the collapsed sidebar, hovering Skills shows recent skills and a New skill action, like Tables and Files.
  • Standalone page: /skills gets the same layout as the Knowledge bases list: header, search, New skill / Import, and a resource list. Remove the Skills tab from the Integrations header.
  • Chat and search: add Skills as a family in the + attach, @ mention and resource-tab menus, in sidebar order. Open a skill as a resource tab in Chat, and make individual skills searchable in ⌘K.
  • Row actions: give skill rows the same context menu as other resources: Open, Rename, Duplicate, Copy link, Manage members, then Delete after a separator.
  • Permissions: add a hideSkillsTab permission-group option that works like hideKnowledgeBaseTab.
  • Backward compatibility: keep existing /skills URLs and the legacy ?skillId= redirect. Send any old Integrations → Skills links to /skills.

Describe alternatives you've considered

  • Keep Skills under Integrations and add a sidebar shortcut. This helps people find Skills but keeps the wrong mental model and duplicates the entry point.
  • Put Skills inside Knowledge bases. They're related, but Skills are instructions and Knowledge bases are searchable documents. Merging them would blur two different jobs.
  • Put Skills inside Agents. Skills are shared across agents and workflows, so tying them to one agent's settings would hide their reuse.

Additional context

  • Why it matters: every resource an agent draws on (Tables, Files, Knowledge bases, Skills) should be found, opened and managed the same way. Skills are among the best ways to make agents reliable, so they should be easy to see.
  • Where it lives today: the sidebar sets additionalActivePaths: ['/workspace/{id}/skills'] on the Integrations nav item, the Skills page renders under IntegrationTabsHeader, and RESOURCE_MENU_ORDER has no skills family.
主要言語
TypeScript
スター
29.8k
フォーク
3.9k
平均マージ
1時間 44分
マージ済み PR（30日）
841

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

simstudioai/sim のほかの issue

simstudioai/sim の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。