Issue Station
Sign In
Tools hereToolbox

litellm - 💡(How to fix) Fix [Bug]: Terminology mismatch between "skills" and "plugins" across docs, code, and UI [3 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
BerriAI/litellm#26036•Fetched 2026-04-19 15:06:10
View on GitHub
Comments
3
Participants
2
Timeline
8
Reactions
0
Author
anengineerdudeanengineerdude
Participants
anengineerdudeanengineerdudeishaan-berriishaan-berri
Timeline (top)
commented ×3mentioned ×2subscribed ×2labeled ×1

Root Cause

  • Users can't confidently search docs, file issues, or talk about the feature
  • Onboarding is harder — new users don't know if they're creating a "skill" or a "plugin"
  • The tutorial is literally titled "Claude Code Plugin Marketplace (Managed Skills)" which uses both terms
RAW_BUFFERClick to expand / collapse

Problem

The "Skills Marketplace" feature introduced in v1.83.3 uses wildly inconsistent terminology between "skills" and "plugins" across the entire stack. It's a cool feature but very confusing to use because of this.

Release notes & docs say "skills":

  • "Skills Marketplace" heading in release notes
  • skills_gateway.md doc
  • /public/skill_hub API endpoint
  • UI "Skill Hub" tab in Model Hub

Code, API, DB, and UI say "plugins":

  • API routes: POST /claude-code/plugins, GET /claude-code/plugins
  • DB table: LiteLLM_ClaudeCodePluginTable
  • Types: PluginListItem, ListPluginsResponse
  • UI component: claude_code_plugins.tsx — page title says "Skills" but function names all say "plugin"
  • Tutorial title: "Claude Code Plugin Marketplace (Managed Skills)" — both terms in one title!

Steps to Reproduce

  1. Read the v1.83.3 release notes — everything is called "Skills Marketplace"
  2. Open the Admin UI — the nav item says "Claude Code Plugins"
  3. Look at the API endpoints — they're all /claude-code/plugins
  4. Look at the DB schema — LiteLLM_ClaudeCodePluginTable
  5. Try to figure out if "skills" and "plugins" are the same thing or different things — good luck

What did you expect to happen?

Consistent terminology. Either call everything a "skill" or call everything a "plugin." Don't use both interchangeably.

Why this matters

  • Users can't confidently search docs, file issues, or talk about the feature
  • Onboarding is harder — new users don't know if they're creating a "skill" or a "plugin"
  • The tutorial is literally titled "Claude Code Plugin Marketplace (Managed Skills)" which uses both terms

Specific files with the mismatch

Suggestion

Pick one term and refactor everything to match. Update docs, UI labels, API route naming (or at least aliases), and type names for consistency.

extent analysis

TL;DR

Refactor the codebase to consistently use either "skills" or "plugins" across all components, including documentation, UI, API endpoints, and database schema.

Guidance

  • Identify all instances of inconsistent terminology in the codebase, documentation, and UI, and create a list of files and components that need to be updated.
  • Decide on a single term to use throughout the project, either "skills" or "plugins", and update all instances of the other term to match.
  • Update API endpoint names and aliases to reflect the chosen term, ensuring that the changes are backwards compatible.
  • Review and update documentation, including release notes, tutorials, and UI labels, to ensure consistency and clarity.

Example

For example, if the decision is made to use "plugins" consistently, the public/skill_hub API endpoint could be updated to public/plugin_hub, and the PluginListItem type could be kept as is, while the UI component claude_code_plugins.tsx would not need significant changes, but its heading could be updated to "Plugins" for consistency.

Notes

It's essential to consider the potential impact of renaming API endpoints and database tables on existing integrations and dependencies. A thorough review of the codebase and documentation is necessary to ensure that all instances of the inconsistent terminology are updated correctly.

Recommendation

Apply a workaround by consistently using one term, "plugins", across the entire stack, as it seems to be the term used in the majority of the codebase, including API routes, DB tables, and types. This choice simplifies the refactoring process and minimizes potential conflicts with existing dependencies.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#configuration error#environment variable#network issue#logging issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING