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.

referencesofficial-contract.md

≈327 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Official Grammarly contract boundary

Source: Writing Score API (accessed 2026-09-04).

The documented status values for a score request are PENDING, FAILED, and COMPLETED. A score request is created, a document is uploaded, and the status and result are retrieved through the documented API flow. This skill analyzes only a sanitized status receipt; it does not reproduce that flow or accept the document.

The official constraints section says to consider exponential backoff for HTTP 429 and reports an ideal base factor of 2 seconds from load-test results. That statement is deliberately narrow: this skill uses it only for a failed 429 when no retry_after_seconds evidence was supplied. It does not turn the documentation into an SLA, timeout, quota, universal maximum retry count, or guarantee.

When retry_after_seconds is supplied by the caller as sanitized evidence, preserve that value in the review output. Do not replace it with the 2-second base, average it, cap it, or claim that it is provider-authenticated.

The source also documents content and upload constraints. Those facts are not inputs to this analyzer: receipt processing must remain metadata-only, and a content or body field is rejected rather than inspected.

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 yesterday.

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