Diagnose and fix Replit common errors and exceptions. Use when encountering Replit errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "replit error", "fix replit", "replit not working", "debug replit".
Diagnoses and fixes common Replit errors by analyzing logs and applying documented solutions.
/plugin marketplace add jeremylongshore/claude-code-plugins-plus-skills/plugin install replit-pack@claude-code-plugins-plusThis skill is limited to using the following tools:
Quick reference for the top 10 most common Replit errors and their solutions.
Check error message and code in your logs or console.
Match your error to one of the documented cases.
Follow the solution steps for your specific error.
Error Message:
Authentication error: Invalid API key
Cause: API key is missing, expired, or invalid.
Solution:
# Verify API key is set
echo $REPLIT_API_KEY
Error Message:
Rate limit exceeded. Please retry after X seconds.
Cause: Too many requests in a short period.
Solution:
Implement exponential backoff. See replit-rate-limits skill.
Error Message:
Request timeout after 30000ms
Cause: Network connectivity or server latency issues.
Solution:
// Increase timeout
const client = new Client({ timeout: 60000 });
# Check Replit status
curl -s https://status.replit.com
# Verify API connectivity
curl -I https://api.replit.com
# Check local configuration
env | grep REPLIT
replit-debug-bundleFor comprehensive debugging, see replit-debug-bundle.
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.