[DOCS] "Skills" is a confusing and potentially incorrect term for what are essentially plugins/tools

Documentation Type

Unclear/confusing documentation

Documentation Location

https://code.claude.com/docs/en/skills

Section/Topic

Skills page — terminology / naming

Current Documentation

The docs use the word "skills" to describe user-created files that extend Claude Code's capabilities. For example: "Skills extend what Claude can do. Create a SKILL.md file with instructions, and Claude adds it to its toolkit."

What's Wrong or Missing?

The term "skill" is misleading. In everyday English, a "skill" is a human talent — something a person has learned to do well. This conflicts with the developer-facing meaning intended here, which is a user-created plugin or extension that adds new capabilities to Claude Code.

This creates confusion for new users who may not immediately understand that a "skill" is an external file/plugin they create, not something Claude intrinsically knows how to do. The term also conflicts with how "skills" is used in other AI contexts (e.g., Alexa Skills, which are third-party voice app integrations — a closer analogy, but still potentially confusing).

Terms like "plugin," "extension," "integration," or "tool" would be clearer and more aligned with developer expectations.

Suggested Improvement

Consider renaming "skills" to a less ambiguous term such as "plugins," "extensions," or "tools." If renaming is not feasible, the introduction of the Skills page should explicitly clarify the concept upfront with an analogy, e.g.:

"Skills are plugins that extend what Claude can do — think of them like browser extensions or IDE plugins, not human talents."

This one-sentence framing at the top of the page would significantly reduce confusion for new users.

Impact

Medium - Makes feature difficult to understand

Additional Context

_No response_