Agent skill · software engineering · jeremylongshore
evernote-ci-integration
Configure CI/CD pipelines for Evernote integrations.
Why this skill is useful
Adds a comprehensive CI/CD pipeline configuration for Evernote integrations, including mock testing and secrets management that the AI wouldn't reliably generate on its own.
What it needs
Requires npm installed locally. Requires github account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Evernote CI Integration Overview Configure continuous integration pipelines for Evernote integrations with mock-based unit tests, sandbox-based integration tests, credential management, and deployment workflows. Prerequisites Git repository with Evernote integration code CI/CD platform (GitHub Actions, GitLab CI, etc.) Test framework (Jest, Vitest, or Mocha) Sandbox API credentials for integration tests Instructions Step 1: GitHub Actions Workflow Create a workflow that runs unit tests on every PR and integration tests on merges to main. Store sandbox credentials as GitHub Actions secrets. Step 2: Mock Evernote Client for Unit Tests Create a mock NoteStore that returns predictable data without hitting the API. Mock createNote, getNote, findNotesMetadata, listNotebooks, and listTags. Step 3: Unit and Integration Test Examples Write unit tests against the mock client (fast, no credentials needed). Write integration tests against the sandbox (slow, needs EVERNOTEDEVTOKEN). Tag integration tests so they can run separately. Step 4: Secrets Management Store EVERNOTECONSUMERKEY, EVERNOTECONSUMERSECRET, and EVERNOTEDEVTOKEN as repository secrets. Never log or echo secret values. Use environment-specific secret names for staging vs production. For the full CI workflow, mock client, test examples, and deployment pipeline, see Implementation Guide. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/evernote-ci-integration