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

Aberta
  • Algo errado?
#8,018 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
52/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
react, typescript
Domínio
frontend

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.
Linguagem predominante
TypeScript
Estrelas
29.8k
Forks
3.9k
Merge médio
1h 44min
PRs com merge (30d)
841

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de simstudioai/sim

Todas as issues de simstudioai/sim

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.