From grammarly-pack
Diagnoses Grammarly API errors like 400/401/413/429 with fixes for auth, chunking, backoff. Includes curl tests for connectivity and scoring endpoint.
How this skill is triggered — by the user, by Claude, or both
Slash command
/grammarly-pack:grammarly-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
**Cause:** Text has fewer than 30 words.
Cause: Text has fewer than 30 words. Fix: Ensure minimum 30 words. Pad short texts with context if needed.
Cause: Token expired or invalid. Fix: Re-authenticate with client credentials grant.
Cause: Text exceeds 100,000 characters or 4 MB.
Fix: Split into chunks using paragraph boundaries. See grammarly-sdk-patterns for chunking function.
Cause: Rate limit exceeded.
Fix: Implement exponential backoff. See grammarly-rate-limits.
Cause: Large document processing or service delay. Fix: Poll every 3-5 seconds, timeout after 90 seconds.
Cause: Short text produces unreliable results. Fix: AI detection works best on 200+ words. Scores on short text are less reliable.
# Test API connectivity
curl -s -o /dev/null -w "%{http_code}" \
-H "Authorization: Bearer $GRAMMARLY_ACCESS_TOKEN" \
https://api.grammarly.com/ecosystem/api/v2/scores
# Test with sample text
curl -X POST https://api.grammarly.com/ecosystem/api/v2/scores \
-H "Authorization: Bearer $GRAMMARLY_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{"text": "This is a test sentence that has more than thirty words so that the API will accept it and return a valid writing score for our diagnostic purposes."}' | python3 -m json.tool
For debugging tools, see grammarly-debug-bundle.
5plugins reuse this skill
First indexed Jul 10, 2026
npx claudepluginhub luxdevnet/claude-plus-lux --plugin grammarly-packDiagnoses and fixes common Grammarly API errors including 400, 401, 413, 429, plagiarism check hangs, and AI detection inconsistencies. Includes curl-based connectivity tests.
Guides 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.