Agent skill · software engineering · jeremylongshore
evernote-prod-checklist
Production readiness checklist for Evernote integrations.
Why this skill is useful
Adds a comprehensive production readiness checklist and verification scripts specifically for Evernote integrations, which are not commonly found in public documentation.
What it needs
Requires docker, jq installed locally. Requires evernote account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Evernote Production Checklist Overview Comprehensive checklist for deploying Evernote integrations to production, covering API key activation, security hardening, rate limit handling, monitoring, and go-live verification. Prerequisites Completed development and testing in sandbox Production API key approved by Evernote (requires review process) Production infrastructure provisioned Instructions API Key & Authentication [ ] Production API key requested and approved by Evernote [ ] EVERNOTESANDBOX=false in production config [ ] Consumer key and secret stored in secrets manager (not env files) [ ] OAuth callback URL uses HTTPS on production domain [ ] Token expiration tracking implemented (edamexpires) [ ] Token refresh/re-auth flow tested end-to-end Security [ ] Access tokens encrypted at rest (AES-256-GCM) [ ] CSRF protection on OAuth flow [ ] API credentials not in source control (.env in .gitignore) [ ] Log output redacts tokens and PII [ ] Input validation on all user-supplied content (ENML sanitization) [ ] Rate limit handling prevents API key suspension Rate Limits & Performance [ ] Exponential backoff on RATELIMITREACHED errors [ ] Minimum delay between API calls (100-200ms) [ ] Response caching for listNotebooks() and listTags() (5-10 min TTL) [ ] findNotesMetadata() used instead of findNotes() for listings [ ] Batch operations use sequential processing with delays Monitoring & Alerting [ ] Health check endpoint verifies Evernote API connectivity [ ] Metrics tracked: API call count, latency, error rate, rate limits [ ] Alerts configured for rate limits, auth failures, and high error rates [ ] Structured logging with correlation IDs [ ] Quota usage monitoring with threshold alerts (75%, 90%) Data Integrity [ ] ENML validation before every createNote/updateNote call [ ] Note titles sanitized (max 255 chars, no newlines) [ ] Tag names validated (max 100 chars, no commas) [ ] Resource hashes verified (MD5 match) [ ] Sync state (USN) tracked and persisted for incre …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/evernote-prod-checklist