跪拜 Guibai
← Back to the summary

Skill Overload Makes AI Go Blind: Claude Code and Codex Handle Overflow Differently

Installing skill (skill packages) for AI programming tools has become a daily habit for many developers. A skill is a folder containing an instruction document that specifies "when to use it and how". Each time the tool starts work, it doesn't stuff all instructions into the context. Instead, it first lists all skills' "names + one-sentence descriptions" and gives that list to the model; the model decides which to use based on descriptions, then reads the full instructions only after selecting one.

That sounds like it saves context. But what happens if you install too many skills?

Community observation: 220 of 283 skills lost their descriptions

On 2026-11-12, developer Murat Sert posted about a phenomenon: he installed 283 skills, and the list sent to the model had 220 skills with only names and no descriptions. The list length stayed stuck at about 30,000 characters (he noted that "about 30,000 characters" is an observed value, not an official spec). He also measured that before the user said anything, the first request already consumed 74,500 tokens, of which about 22,000 came from his installed plugins, skills, MCPs, and hooks; in another old session with 672 skills, 642 had no descriptions. He said he hadn't seen this mentioned in official docs.

We also checked our everyday machine (not test environment): in the last 12 sessions, each listed 120 to 125 skills, of which 54 to 60 had only names, and the list length stayed stable at 26,500 to 26,850 characters.

Actually, this is written in the official docs, and Claude Code and Codex handle it completely differently.

Budget rules in official docs

After skill listing exceeds budget, the two cut in different places

Checking both tools' official docs shows they both set a strict context budget for the skill listing:

Claude Code: Keep all names, cut descriptions of low-frequency skills first

In the "Skill descriptions are cut short" section of Claude Code docs:

Codex: Shorten each description first, then drop skills if needed

The Codex Skills page gives a different approach (note: Codex's listing also includes each skill's file path in addition to name and description):

Our practical comparison

Trigger results after adding 300 unrelated skills

How much difference do these two truncation strategies make in actual work? We tested on 2026-11-13.

Test environment and method

Core results

Condition Claude Code Codex
Only this one skill 3/3 triggered, ~8-10 seconds 3/3 triggered, ~21-25 seconds
Add 300 unrelated fake skills 1 of 3 triggered 3/3 triggered, ~22-25 seconds

Note: time differences include model and startup time; cannot be attributed solely to the skill mechanism.

With only this one skill, Claude Code had ~41k input tokens, Codex ~49k. After adding 300 fake skills, the two diverged:

Three other interesting observations

  1. A distinctive name gets guessed: early in testing, the target skill's name looked different from the 300 fake names. Even with description removed, Claude Code used it in all 4 runs, 3 times by directly clicking on the name that "looked different". The table data above is from rerunning after changing the target name to the same format as the fake names.
  2. Once used, the description returns: in Claude Code, after a skill is called once, in a fresh run under the same environment, its description reappears in the listing. This matches the official "remove least-called first" rule.
  3. Codex's failure point comes later: when fake skills increased to 1,500 (this condition ran only once), Codex warned that all skill descriptions were removed, and another 654 skills didn't make it into the listing. The target skill wasn't in the listing, so it didn't trigger; it also made up a number.

Test limitations

Practical advice you can follow directly

Based on official docs and test results, if you have many skills installed, optimize with these points:

  1. Put keywords first: write "when to use" as the first sentence of the description, putting core trigger words at the very front. This preserves matching even when Codex shortens descriptions.
  2. Make skill names reveal their purpose: in the extreme case where descriptions are trimmed and only names remain, a semantically clear name still helps the model guess the right tool.
  3. Clean up idle skills: disable or uninstall unused skills promptly. In Claude Code, use /doctor to see context usage of the listing, /skill-doctor to find unused skills, or set low-priority skills to "name-only" in skillOverrides.
  4. Increase budget as needed: in Claude Code, frequently used skills naturally keep their descriptions because they are called often; if you truly need many skills on standby, increase skillListingBudgetFraction in Claude Code settings (or configure SLASH_COMMAND_TOOL_CHAR_BUDGET), and adjust skills.max_context_tokens in Codex.

Reference links

Comments

Top 1 of 2 from juejin.cn, machine-translated. The original thread is authoritative.

shushenghong

54 to 60 skills left with only their names; the root cause is often that everyone installs their own and never uninstalls. Our team later maintained a single shared config, with a couple of tech-savvy people responsible for adding and removing, while others use it directly. Someone takes responsibility for the whole list when deciding which skill should be dropped. According to the rule in the article about Claude Code 'trimming descriptions starting from the least-called', rather than each person adjusting their budget, it's better to centralize the management of the list.

ZzT

What model are you? 😏