From grammarly-pack
Guides secure Grammarly API credential management: Client ID/Secret storage, in-memory access tokens, token lifecycle, HTTPS calls, and leak-prevention checklist for integrations.
npx claudepluginhub jeremylongshore/claude-code-plugins-plus-skills --plugin grammarly-packThis skill is limited to using the following tools:
| Credential | Scope | Storage |
Configures Grammarly API authentication via OAuth for enterprise accounts. Sets up env vars, fetches bearer tokens, and verifies connection with TypeScript scripts.
Implements Gamma API security best practices: env-based key storage, rotation strategies, HMAC request signing, scoped access controls, permission checks, and audit logging.
Applies Groq API security best practices: key storage in env vars/secret managers, rotation procedures, git leak prevention hooks, and server-side patterns.
Share bugs, ideas, or general feedback.
| Credential | Scope | Storage |
|---|---|---|
| Client ID | App-level | Config |
| Client Secret | App-level | Secrets vault |
| Access Token | Session | Memory only |
# .env (never commit)
GRAMMARLY_CLIENT_ID=your_id
GRAMMARLY_CLIENT_SECRET=your_secret
Tokens from client_credentials grant expire. Never persist access tokens to disk. Re-authenticate when needed.
For production, see grammarly-prod-checklist.