Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/grammarly-api-reliability

@820dfc8
Run it yourself

Analyze a sanitized Grammarly asynchronous job receipt without sending requests, reading document content, or guessing provider SLAs. Use when a Writing Score or similar document job is PENDING, FAILED, or COMPLETED and a bounded retry decision is needed. Trigger with "analyze Grammarly job receipt", "Grammarly 429 retry", or "Grammarly job status".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/grammarly-api-reliability

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈95 tokens for metadata: the name and description. ≈1.2k when used: this file. ≈2.3k more on demand in 3 files.

Description uses 4.7% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈379 characters, or 4.7%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Grammarly API Reliability

This is a read-only, metadata-only decision aid for asynchronous Grammarly jobs. It does not call Grammarly, upload text, inspect a response body, create a token, or retry a request. It turns one strict JSON receipt into a bounded, evidence-labeled classification.

Overview

Use this skill to classify a sanitized asynchronous receipt without treating a provider response as permission to retry blindly.

Prerequisites

No credentials, network access, Grammarly account, document, or response body is needed. Python 3.10+ is the only runtime requirement. If a separate live integration is being designed, use the official OAuth 2.0 credentials documentation (accessed 2026-09-04) to determine access; live authentication and requests are outside this skill.

Instructions

Step 1: Run the deterministic analyzer

Run the bundled script against a receipt file or standard input:

python3 scripts/analyze_job_receipt.py receipt.json
cat receipt.json | python3 scripts/analyze_job_receipt.py -
python3 scripts/analyze_job_receipt.py --self-test

The analyzer accepts only the documented metadata schema in references/receipt-schema.md. It recursively rejects keys associated with document content, bodies, text, headers, or tokens, including those hidden in an otherwise unknown nested object. Unknown keys, malformed values, inconsistent 429 evidence, and attempts above the cap fail closed.

Step 2: Apply the decision rules

  • COMPLETED is terminal. Do not retry it.
  • PENDING is not a failure. Report that the receipt is still pending; do not invent a polling interval, timeout, SLA, quota, or freshness guarantee.
  • FAILED with http_status: 429 is the only status-specific retry class in this skill. If a numeric retry_after_seconds value is supplied, the output preserves that evidence as the wait instruction. If it is absent, the output names Grammarly's documented 2-second-base exponential-backoff guidance for 429 only; it does not invent a maximum, jitter rule, quota, or service promise.
  • Any failure without 429 evidence is MANUAL_REVIEW: the receipt alone does not establish that retrying is safe.
  • A failed receipt at attempts == max_attempts is ATTEMPT_CAP_REACHED and must not receive retry guidance. An input with attempts > max_attempts is invalid.

The cap is caller-supplied policy, not a Grammarly limit. The analyzer never changes the cap or performs the next attempt. A human or caller-owned controller must decide whether a retry is appropriate after reviewing the emitted classification.

Step 3: Enforce the safety boundaries

Use synthetic receipts for evaluation. Never paste document text, raw request or response bodies, HTTP headers, access tokens, authorization values, or secrets. The script is standard-library-only and has no network, filesystem-write, subprocess, or deletion behavior. It reports validation errors rather than trying to sanitize unsafe input.

Read the focused references only when needed:

Output

The JSON result names the accepted status, attempts, cap, classification, and a short evidence-bounded guidance string. It never echoes submitted metadata beyond those safe scalar fields and never fabricates an SLA, timeout, quota, result body, or document diagnosis.

Error Handling

Invalid JSON, forbidden recursive keys, unknown fields, unsupported statuses, contradictory 429 evidence, and cap violations are errors. The script exits non-zero and emits no classification. A valid non-429 failure is MANUAL_REVIEW, not a retry recommendation.

Examples

  • A completed receipt returns COMPLETED_TERMINAL and no retry instruction.
  • A failed 429 with retry_after_seconds: 17 returns RETRY_AFTER_EVIDENCE and preserves 17 seconds.
  • A nested diagnostics.response_body or credentials.access_token field is rejected before classification.

Resources

Official source

Grammarly Writing Score API (accessed 2026-09-04).

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill is a security-hardened analyzer for Grammarly job receipts that operates locally without network access. It uses strict input validation to prevent sensitive data exposure and includes a comprehensive test suite to ensure resistance against prompt injection attacks.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 hours ago.

Activeupdated 3 months ago
What it can do
Runs commands
version
2.0.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
compatibility
Agent Skills-compatible hosts; requires Python 3.10+
All 1 allowed tools
Bash(python3:*)
Other metadata
tags
[
  "saas",
  "grammarly",
  "reliability",
  "retries",
  "privacy"
]

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/grammarly-api-reliability