Back to Signal Feed
CodeTracked since May 19, 2026

LibreChat now routes /skills/new directly to skill creation

The PR adds an explicit `skills/new` route and updates `SkillsView` to handle that path with `CreateSkillForm`, so “Create Skill” no longer falls through to `/skills/:skillId`; users without create permission are redirected to `/skills`.

LibreChatClient routesskills/newSkillsView

What Happened

  • The PR adds an explicit `skills/new` route and updates `SkillsView` to handle that path with `CreateSkillForm`, so “Create Skill” no longer falls through to `/skills/:skillId`; users without create permission are redirected to `/skills`.
  • The PR adds an explicit `skills/new` route and updates `SkillsView` to handle that path with `CreateSkillForm`, so “Create Skill” no longer falls through to `/skills/:skillId`; users without create permission are redirected to `/skills`.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Implemented a single concrete routing fix in the Agent Builder frontend: register `skills/new` as a dedicated route and branch `SkillsView` logic for that path to render `CreateSkillForm`, preventing it from being treated as a `:skillId` route; permission behavior is preserved by redirecting unauthorized users to `/skills`.

Why Track This

Why It Matters

Agents using the Create Skill path in LibreChat now land on the correct create form instead of the wrong skill detail view, which reduces user confusion and failed workflow setup when building or editing agents. This is achieved by making `/skills/new` a first-class client route and routing it to `CreateSkillForm` before the parametric `/skills/:skillId` path; continue to watch for regressions in route matching around other skill URLs and verify redirects still behave correctly for users with partial permission sets.

Impact

Agents using the Create Skill path in LibreChat now land on the correct create form instead of the wrong skill detail view, which reduces user confusion and failed workflow setup when building or editing agents. This is achieved by making `/skills/new` a first-class client route and routing it to `CreateSkillForm` before the parametric `/skills/:skillId` path; continue to watch for regressions in route matching around other skill URLs and verify redirects still behave correctly for users with partial permission sets.

What To Watch Next

  • Watch whether LibreChat becomes a repeated pattern.
  • Track follow-up changes around Agent Orchestration Platforms.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: route_shadowing_regression, permission_redirect_misroute.
Open Topic TimelineOpen Technical EventOpen Original Sourceroute_shadowing_regression / permission_redirect_misroute / navigation_flake_in_skill_routes

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

danny-avila/LibreChat PR #13119: fix: add explicit skills/new route

Added an explicit `skills/new` route and dedicated `SkillsView` handling so the create flow opens the create form instead of being matched by the generic skill detail route.