SR-10 remove legacy /settings/agent-config Skills tab + scope-ladder UI components #878

Closed
opened 2026-05-05 10:30:35 +00:00 by claude-desktop · 0 comments
Collaborator

User story

As a platform engineer, I want the cross-cutting /settings/agent-config Skills tab and its scope-ladder UI components removed, so that there is exactly one path to view and edit a skill (the anchored agent page) and no parallel surface to keep in sync.

Acceptance criteria

Web app

  • Remove the Skills tab (and System prompts tab if not used by other artifacts) from apps/web/src/routes/settings.agent-config.tsx. The route can keep tabs for the other kinds (plugins, mcp-servers, marketplaces) — only the skill kind is dropped.
  • Remove apps/web/src/features/agent-config/scope-ladder.tsx (or any equivalent ScopeLadder component) when it has no remaining consumers. Keep it if other kinds still use it.
  • Remove apps/web/src/features/agent-config/anchored-inherited-row.tsx if its only consumer was the deleted SkillsTab.

Server

  • GET /agents/skills (the legacy filesystem dump) is removed. The new GET /agents/skills/library (SR-6) replaces it.
  • /agent-config/list?kind=skills and the matching /agent-config/row/:id, /agent-config/upsert, /agent-config/fork, /agent-config/:id paths are removed for kind=skills. Other kinds keep working.

Tests

  • Delete apps/web/src/features/agent-config/skills-tab.test.tsx if not already replaced in SR-8.
  • Update settings.agent-config.test.tsx to assert the Skills tab is no longer rendered.

Out of scope

  • Removing the Drizzle store for the legacy skill table (covered in SR-11).
  • Other artifact kinds (system-prompts, plugins, mcp-servers, marketplaces) — they keep the scope-ladder UI.

References

  • Spec: specs/skills-rework.md §CRUD UI ("the cross-cutting /settings/agent-config Skills tab is removed").
  • Files: apps/web/src/routes/settings.agent-config.tsx, apps/web/src/features/agent-config/skills-tab.tsx, apps/server/src/main.ts (legacy route registration).
  • Depends on SR-8.
## User story As a platform engineer, I want the cross-cutting `/settings/agent-config` Skills tab and its scope-ladder UI components removed, so that there is exactly one path to view and edit a skill (the anchored agent page) and no parallel surface to keep in sync. ## Acceptance criteria ### Web app - [ ] Remove the Skills tab (and System prompts tab if not used by other artifacts) from `apps/web/src/routes/settings.agent-config.tsx`. The route can keep tabs for the other kinds (`plugins`, `mcp-servers`, `marketplaces`) — only the skill kind is dropped. - [ ] Remove `apps/web/src/features/agent-config/scope-ladder.tsx` (or any equivalent ScopeLadder component) when it has no remaining consumers. Keep it if other kinds still use it. - [ ] Remove `apps/web/src/features/agent-config/anchored-inherited-row.tsx` if its only consumer was the deleted SkillsTab. ### Server - [ ] `GET /agents/skills` (the legacy filesystem dump) is removed. The new `GET /agents/skills/library` (SR-6) replaces it. - [ ] `/agent-config/list?kind=skills` and the matching `/agent-config/row/:id`, `/agent-config/upsert`, `/agent-config/fork`, `/agent-config/:id` paths are removed for `kind=skills`. Other kinds keep working. ### Tests - [ ] Delete `apps/web/src/features/agent-config/skills-tab.test.tsx` if not already replaced in SR-8. - [ ] Update `settings.agent-config.test.tsx` to assert the Skills tab is no longer rendered. ## Out of scope - Removing the Drizzle store for the legacy `skill` table (covered in SR-11). - Other artifact kinds (`system-prompts`, `plugins`, `mcp-servers`, `marketplaces`) — they keep the scope-ladder UI. ## References - Spec: `specs/skills-rework.md` §CRUD UI ("the cross-cutting `/settings/agent-config` Skills tab is removed"). - Files: `apps/web/src/routes/settings.agent-config.tsx`, `apps/web/src/features/agent-config/skills-tab.tsx`, `apps/server/src/main.ts` (legacy route registration). - Depends on **SR-8**.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
charles/claude-hooks#878
No description provided.