What this error means
beta.skills.list hard-capped at 100 items with broken pagination — has_more always false, no cursor available is a Anthropic API failure pattern reported for developers trying to fix broken pagination in anthropic beta.skills.list endpoint returning only first 100 items regardless of total count. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.
Why this happens
GitHub Issue #1391 on anthropics/anthropic-sdk-python by RahulBalakavi (Apr 15 2026). The API endpoint caps results at 100 and the pagination mechanism (has_more flag + cursor) is completely broken. Users with more than 100 registered skills cannot access them. Clear error signature, actionable fix needed. Category mapping: direct Anthropic API error.
Common causes
- GitHub Issue #1391 on anthropics/anthropic-sdk-python by RahulBalakavi (Apr 15 2026). The API endpoint caps results at 100 and the pagination mechanism (has_more flag + cursor) is completely broken. Users with more than 100 registered skills cannot access them. Clear error signature, actionable fix needed. Category mapping: direct Anthropic API error.
Quick fixes
- Confirm the exact error signature matches
beta.skills.list hard-capped at 100 items with broken pagination — has_more always false, no cursor available. - Check the Anthropic API account, local tool state, and provider configuration involved in the failing workflow.
- Compare the failing environment with a known working setup, then change one configuration value at a time.
Platform/tool-specific checks
- Verify the command, editor, extension, or API client that produced the error.
- Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
- Avoid deleting credentials, local model data, or project settings until the failing scope is clear.
Step-by-step troubleshooting
- Capture the exact error message and the command, editor action, or request that triggered it.
- Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
- Review the source evidence below and compare it with your environment.
- Apply one change at a time and rerun the smallest failing action.
- Keep the working fix documented for the team or deployment environment.
How to prevent it
- Keep provider/tool configuration documented.
- Record non-secret diagnostics such as tool version, provider name, model name, and command path.
- Add a lightweight check before CI or production workflows depend on the tool.