From openrouter-pack
Execute diagnose and fix common OpenRouter API errors. Use when troubleshooting failed requests. Trigger with phrases like 'openrouter error', 'openrouter not working', 'openrouter 401', 'openrouter 429', 'fix openrouter'.
How this skill is triggered — by the user, by Claude, or both
Slash command
/openrouter-pack:openrouter-common-errorsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill provides a comprehensive guide to identifying, diagnosing, and resolving the most common OpenRouter API errors.
This skill provides a comprehensive guide to identifying, diagnosing, and resolving the most common OpenRouter API errors.
Follow these steps to implement this skill:
Successful execution produces:
See ${CLAUDE_SKILL_DIR}/references/errors.md for comprehensive error handling.
See ${CLAUDE_SKILL_DIR}/references/examples.md for detailed examples.
npx claudepluginhub aiminnovations/claude-code-plugins-plus --plugin openrouter-packGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
4plugins reuse this skill
First indexed Jul 11, 2026