Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jeremylongshore/grammarly-incident-runbook
Follow Grammarly incident response runbook for API outages.
Passed 24 of 25 test cases with the skill, and 11 of 25 without it.
and 13 more in the full report
14 fixed10 passed either way0 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
Provide the exact curl command payload text string used to test authenticated text scoring health against the Grammarly API.
| Checked | Without skill | With skill |
|---|---|---|
| Includes the payload string Test sentence for Grammarly API diagnostic health check. | Missed | Passed |
The instructions your model reads when the skill loads.
Incident response procedures for Grammarly writing API integration failures. Covers text check timeouts, suggestion quality degradation, OAuth token failures, and rate limit storms. Grammarly powers real-time writing assistance, so API incidents directly impact user-facing text checking, scoring workflows, and content quality pipelines. Classify severity immediately using the matrix below and follow the corresponding playbook.
| Level | Definition | Response Time | Example |
|---|---|---|---|
| P1 - Critical | Full API outage, all scoring requests fail | 15 min | 5xx on /v2/scores for all requests |
| P2 - High | OAuth token failures or sustained timeouts | 30 min | All authenticated requests return 401 |
| P3 - Medium | Rate limit storms or elevated latency | 2 hours | 429 responses, scoring takes 10s+ per request |
| P4 - Low | Suggestion quality drift or single endpoint issue | 8 hours | Scores returning but correctness values seem off |
# Test API health (unauthenticated)
curl -s -o /dev/null -w "HTTP %{http_code}\n" \
https://api.grammarly.com/ecosystem/api/v2/scores
# Test authenticated scoring
curl -s -w "\nHTTP %{http_code}\n" \
-H "Authorization: Bearer $GRAMMARLY_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-X POST https://api.grammarly.com/ecosystem/api/v2/scores \
-d '{"text": "Test sentence for Grammarly API diagnostic health check."}'
# Check OAuth token validity
curl -s -o /dev/null -w "HTTP %{http_code}\n" \
-H "Authorization: Bearer $GRAMMARLY_ACCESS_TOKEN" \
https://api.grammarly.com/ecosystem/api/v2/account
test cases passed, vs 11 / 25 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.