Skill

grammarly-common-errors

Diagnoses Grammarly API errors like 400/401/413/429 with fixes for auth, chunking, backoff. Includes curl tests for connectivity and scoring endpoint.

Bash

api-development

developer-tools

npx claudepluginhub jeremylongshore/claude-code-plugins-plus-skills --plugin grammarly-pack

Tool Access

This skill is limited to using the following tools:

ReadGrepBash(curl:*)

Preview

**Cause:** Text has fewer than 30 words.

SKILL.md

Similar Skills

grammarly-incident-runbook

1.9k

Executes Grammarly API outage triage: curl health checks, severity classification, TypeScript fallback implementation.

3 tools

grammarly-pack

cache-components

139.3k

Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

Stats

Parent Repo Stars1854

Parent Repo Forks248

Last CommitMar 22, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Grammarly Common Errors

Error Reference

400 Bad Request — Text Too Short

Cause: Text has fewer than 30 words. Fix: Ensure minimum 30 words. Pad short texts with context if needed.

401 Unauthorized

Cause: Token expired or invalid. Fix: Re-authenticate with client credentials grant.

413 Payload Too Large

Cause: Text exceeds 100,000 characters or 4 MB. Fix: Split into chunks using paragraph boundaries. See grammarly-sdk-patterns for chunking function.

429 Too Many Requests

Cause: Rate limit exceeded. Fix: Implement exponential backoff. See grammarly-rate-limits.

Plagiarism Check Stuck on "pending"

Cause: Large document processing or service delay. Fix: Poll every 3-5 seconds, timeout after 90 seconds.

AI Detection — Inconsistent Scores

Cause: Short text produces unreliable results. Fix: AI detection works best on 200+ words. Scores on short text are less reliable.

Quick Diagnostics

# 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

Resources

Next Steps

For debugging tools, see grammarly-debug-bundle.