claude-code - 💡(How to fix) Fix [DOCS] skills priorities [1 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
anthropics/claude-code#53288Fetched 2026-04-26 05:19:33
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
labeled ×4
RAW_BUFFERClick to expand / collapse

Documentation Type

Unclear/confusing documentation

Documentation Location

https://code.claude.com/docs/en/skills#extend-claude-with-skills

Section/Topic

Where skills live

Current Documentation

The docs say:

When skills share the same name across levels, higher-priority locations win: enterprise > personal > project.

What's Wrong or Missing?

It is extremely confusing to use > (greater-than) as an arrow. The sentence seems to imply enterprise has highest, project has lowest priority/precedence.

Suggested Improvement

When skills share the same name across levels, the most specific location wins; in order of increasing precedence: enterprise (lowest) -- personal -- project (highest).

Impact

High - Prevents users from using a feature

Additional Context

It can easily be tested that project-specific has higher precedence than personal.

extent analysis

TL;DR

Update the documentation to clarify the precedence order of skills locations using a clear and consistent notation.

Guidance

  • Replace the greater-than symbol (>) with a more intuitive notation, such as a numbered list or a clear description of the precedence order.
  • Verify the change by reviewing the updated documentation and ensuring it accurately reflects the correct precedence order: project (highest) > personal > enterprise (lowest).
  • Test the documentation change with users to ensure it resolves the confusion and allows them to use the feature correctly.
  • Consider adding an example or a table to illustrate the precedence order and make it easier to understand.

Example

The updated documentation could read: "When skills share the same name across levels, the most specific location wins. The precedence order is as follows:

  1. Project
  2. Personal
  3. Enterprise"

Notes

The suggested improvement provided in the issue is a good starting point, but it may be helpful to test the updated documentation with users to ensure it is clear and effective.

Recommendation

Apply the suggested improvement to update the documentation, as it provides a clear and consistent notation for the precedence order of skills locations.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING