Feature: Make skill budget configurable or provide visibility into hidden skills
Problem
Claude Code has an undocumented ~16,000 character budget for the available_skills section. Users who install many skills (60+) find that some skills are silently hidden from the agent. There's no way to:
- Know which skills are hidden without examining the system prompt
- Configure or increase the budget
- Prioritize which skills should be visible
Current Behavior
<!-- Showing 42 of 63 skills due to token limits -->
Hidden skills cannot be discovered or invoked by the agent, even if their names are explicitly typed.
Proposed Solutions
Any of these would improve the user experience:
Option A: Make budget configurable
Allow users to set the skill metadata budget in settings, trading off context window space for skill visibility.
{
"skills": {
"metadataBudget": 32000
}
}
Option B: Skill prioritization
Allow users to mark certain skills as high-priority so they're always included in the visible set.
# In SKILL.md frontmatter
priority: high
Option C: On-demand skill loading
Instead of truncating, show abbreviated entries for overflow skills that can be expanded on request:
<skill name="evidence-reasoning" collapsed="true" />
Option D: Warning/visibility improvements
At minimum, surface which skills are hidden:
- Show a warning when skills are installed that would exceed budget
- List hidden skill names in the truncation comment
- Provide a command to see hidden skills
Research
Detailed empirical analysis: https://gist.github.com/alexey-pelykh/faa3c304f731d6a962efc5fa2a43abe1
Impact
Users building comprehensive skill libraries (methodologies, domain expertise, workflows) are limited to ~40-50 skills before hitting invisible truncation. This limits the utility of skills as a customization mechanism.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗