From evernote-pack
Provides production checklist for Evernote API integrations, covering auth, security, rate limits, monitoring, data integrity, and deployment verification.
npx claudepluginhub jeremylongshore/claude-code-plugins-plus-skills --plugin evernote-packThis skill is limited to using the following tools:
Comprehensive checklist for deploying Evernote integrations to production, covering API key activation, security hardening, rate limit handling, monitoring, and go-live verification.
Deploys Evernote Node.js integrations to production via Docker, AWS ECS/Lambda, Google Cloud Run, and Kubernetes with secrets management and health checks.
Provides production readiness checklist for OneNote Graph API integrations, verifying auth resilience, rate limits, SharePoint thresholds, and failure modes.
Provides production deployment checklist for TwinMind integrations, covering authentication, security, data privacy, infrastructure provisioning, and monitoring setup.
Share bugs, ideas, or general feedback.
Comprehensive checklist for deploying Evernote integrations to production, covering API key activation, security hardening, rate limit handling, monitoring, and go-live verification.
EVERNOTE_SANDBOX=false in production configedam_expires).env in .gitignore)RATE_LIMIT_REACHED errorslistNotebooks() and listTags() (5-10 min TTL)findNotesMetadata() used instead of findNotes() for listingscreateNote/updateNote callNODE_ENV=production set in container#!/bin/bash
set -euo pipefail
echo "Verifying Evernote production deployment..."
# 1. Health check
curl -sf "$APP_URL/health" | jq '.evernoteApi' | grep -q '"connected"'
echo " Health check: PASS"
# 2. Create test note
GUID=$(curl -sf "$APP_URL/api/test-note" | jq -r '.guid')
echo " Note creation: PASS (GUID: $GUID)"
# 3. Clean up test note
curl -sf -X DELETE "$APP_URL/api/notes/$GUID"
echo " Cleanup: PASS"
echo "All checks passed."
For the complete checklist details and verification scripts, see Implementation Guide.
| Error | Cause | Solution |
|---|---|---|
INVALID_AUTH in production | Using sandbox token with production endpoint | Verify EVERNOTE_SANDBOX=false matches production key |
| Verification script fails | Service not healthy after deploy | Check logs, rollback if needed |
| Rate limits on launch | Burst of API calls at startup | Add startup delay, warm caches gradually |
PERMISSION_DENIED | Production key missing permissions | Contact Evernote developer support |
For version upgrades, see evernote-upgrade-migration.
Go-live checklist: Walk through each section, check off items, run the verification script, and sign off with the team before switching DNS to the production deployment.
Security audit: Review encrypted token storage, verify log redaction, confirm CSRF protection, and test token expiration handling before the production launch.