[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78ZMWAXEX55GQR84G1SHSPD":3,"skill-same:01M78ZMWAXEX55GQR84G1SHSPD":58},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M78ZMWAXEX55GQR84G1SHSPD","evernote-ci-integration",null,"Configure CI\u002FCD pipelines for Evernote integrations.\nUse when setting up automated testing, continuous integration,\nor deployment pipelines for Evernote projects.\nTrigger with phrases like \"evernote ci\", \"evernote github actions\",\n\"evernote pipeline\", \"automate evernote tests\".","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--evernote-pack--evernote-ci-integration\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: evernote-ci-integration\ndescription: |\n  Configure CI\u002FCD pipelines for Evernote integrations.\n  Use when setting up automated testing, continuous integration,\n  or deployment pipelines for Evernote projects.\n  Trigger with phrases like \"evernote ci\", \"evernote github actions\",\n  \"evernote pipeline\", \"automate evernote tests\".\nallowed-tools: Read, Write, Edit, Bash(npm:*), Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, evernote, deployment, testing, ci-cd]\n---\n# Evernote CI Integration\n\n## Overview\nConfigure continuous integration pipelines for Evernote integrations with mock-based unit tests, sandbox-based integration tests, credential management, and deployment workflows.\n\n## Prerequisites\n- Git repository with Evernote integration code\n- CI\u002FCD platform (GitHub Actions, GitLab CI, etc.)\n- Test framework (Jest, Vitest, or Mocha)\n- Sandbox API credentials for integration tests\n\n## Instructions\n\n### Step 1: GitHub Actions Workflow\n\nCreate a workflow that runs unit tests on every PR and integration tests on merges to main. Store sandbox credentials as GitHub Actions secrets.\n\n```yaml\n# .github\u002Fworkflows\u002Fevernote-ci.yml\nname: Evernote CI\non: [push, pull_request]\njobs:\n  test:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - uses: actions\u002Fsetup-node@v4\n        with: { node-version: '20' }\n      - run: npm ci\n      - run: npm test\n      - name: Integration tests\n        if: github.ref == 'refs\u002Fheads\u002Fmain'\n        env:\n          EVERNOTE_DEV_TOKEN: ${{ secrets.EVERNOTE_SANDBOX_TOKEN }}\n          EVERNOTE_SANDBOX: 'true'\n        run: npm run test:integration\n```\n\n### Step 2: Mock Evernote Client for Unit Tests\n\nCreate a mock NoteStore that returns predictable data without hitting the API. Mock `createNote`, `getNote`, `findNotesMetadata`, `listNotebooks`, and `listTags`.\n\n```javascript\nclass MockNoteStore {\n  constructor() {\n    this.notes = new Map();\n    this.notebooks = [{ guid: 'nb-1', name: 'Default', defaultNotebook: true }];\n  }\n\n  async createNote(note) {\n    const guid = `note-${Date.now()}`;\n    const created = { ...note, guid, created: Date.now(), updated: Date.now() };\n    this.notes.set(guid, created);\n    return created;\n  }\n\n  async getNote(guid, withContent) {\n    const note = this.notes.get(guid);\n    if (!note) throw { identifier: 'Note.guid', key: guid };\n    return withContent ? note : { ...note, content: undefined };\n  }\n\n  async listNotebooks() { return this.notebooks; }\n}\n```\n\n### Step 3: Unit and Integration Test Examples\n\nWrite unit tests against the mock client (fast, no credentials needed). Write integration tests against the sandbox (slow, needs `EVERNOTE_DEV_TOKEN`). Tag integration tests so they can run separately.\n\n### Step 4: Secrets Management\n\nStore `EVERNOTE_CONSUMER_KEY`, `EVERNOTE_CONSUMER_SECRET`, and `EVERNOTE_DEV_TOKEN` as repository secrets. Never log or echo secret values. Use environment-specific secret names for staging vs production.\n\nFor the full CI workflow, mock client, test examples, and deployment pipeline, see [Implementation Guide](references\u002Fimplementation-guide.md).\n\n## Output\n- GitHub Actions workflow with unit and integration test stages\n- `MockNoteStore` class for deterministic unit testing\n- Integration test suite using sandbox credentials\n- Secrets management configuration for GitHub Actions\n- npm scripts: `test`, `test:unit`, `test:integration`\n\n## Error Handling\n| Error | Cause | Solution |\n|-------|-------|----------|\n| Integration test auth failure | Expired sandbox token | Regenerate Developer Token in sandbox settings |\n| Flaky integration tests | Rate limits in CI | Add delays between integration tests, reduce parallelism |\n| Secret not available | Missing repository secret | Add secret in GitHub Settings > Secrets and variables |\n| Mock drift | Mock doesn't match real API behavior | Update mock when upgrading SDK version |\n\n## Resources\n- [GitHub Actions](https:\u002F\u002Fdocs.github.com\u002Fen\u002Factions)\n- [Jest Documentation](https:\u002F\u002Fjestjs.io\u002Fdocs\u002Fgetting-started)\n- [Evernote Sandbox](https:\u002F\u002Fsandbox.evernote.com)\n- [GitHub Encrypted Secrets](https:\u002F\u002Fdocs.github.com\u002Fen\u002Factions\u002Fsecurity-for-github-actions\u002Fsecurity-guides\u002Fusing-secrets-in-github-actions)\n\n## Next Steps\nFor deployment pipelines, see `evernote-deploy-integration`.\n\n## Examples\n\n**Unit test suite**: Test `NoteService.createNote()` against `MockNoteStore` to verify ENML wrapping, title sanitization, and tag handling without any API calls.\n\n**Sandbox integration test**: In CI, create a note in the sandbox, retrieve it by GUID, verify content matches, then delete it. Runs only on main branch merges.\n","# Evernote CI Integration\n\n## Overview\nConfigure continuous integration pipelines for Evernote integrations with mock-based unit tests, sandbox-based integration tests, credential management, and deployment workflows.\n\n## Prerequisites\n- Git repository with Evernote integration code\n- CI\u002FCD platform (GitHub Actions, GitLab CI, etc.)\n- Test framework (Jest, Vitest, or Mocha)\n- Sandbox API credentials for integration tests\n\n## Instructions\n\n### Step 1: GitHub Actions Workflow\n\nCreate a workflow that runs unit tests on every PR and integration tests on merges to main. Store sandbox credentials as GitHub Actions secrets.\n\n```yaml\n# .github\u002Fworkflows\u002Fevernote-ci.yml\nname: Evernote CI\non: [push, pull_request]\njobs:\n  test:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - uses: actions\u002Fsetup-node@v4\n        with: { node-version: '20' }\n      - run: npm ci\n      - run: npm test\n      - name: Integration tests\n        if: github.ref == 'refs\u002Fheads\u002Fmain'\n        env:\n          EVERNOTE_DEV_TOKEN: ${{ secrets.EVERNOTE_SANDBOX_TOKEN }}\n          EVERNOTE_SANDBOX: 'true'\n        run: npm run test:integration\n```\n\n### Step 2: Mock Evernote Client for Unit Tests\n\nCreate a mock NoteStore that returns predictable data without hitting the API. Mock `createNote`, `getNote`, `findNotesMetadata`, `listNotebooks`, and `listTags`.\n\n```javascript\nclass MockNoteStore {\n  constructor() {\n    this.notes = new Map();\n    this.notebooks = [{ guid: 'nb-1', name: 'Default', defaultNotebook: true }];\n  }\n\n  async createNote(note) {\n    const guid = `note-${Date.now()}`;\n    const created = { ...note, guid, created: Date.now(), updated: Date.now() };\n    this.notes.set(guid, created);\n    return created;\n  }\n\n  async getNote(guid, withContent) {\n    const note = this.notes.get(guid);\n    if (!note) throw { identifier: 'Note.guid', key: guid };\n    return withContent ? note : { ...note, content: undefined };\n  }\n\n  async listNotebooks() { return this.notebooks; }\n}\n```\n\n### Step 3: Unit and Integration Test Examples\n\nWrite unit tests against the mock client (fast, no credentials needed). Write integration tests against the sandbox (slow, needs `EVERNOTE_DEV_TOKEN`). Tag integration tests so they can run separately.\n\n### Step 4: Secrets Management\n\nStore `EVERNOTE_CONSUMER_KEY`, `EVERNOTE_CONSUMER_SECRET`, and `EVERNOTE_DEV_TOKEN` as repository secrets. Never log or echo secret values. Use environment-specific secret names for staging vs production.\n\nFor the full CI workflow, mock client, test examples, and deployment pipeline, see [Implementation Guide](references\u002Fimplementation-guide.md).\n\n## Output\n- GitHub Actions workflow with unit and integration test stages\n- `MockNoteStore` class for deterministic unit testing\n- Integration test suite using sandbox credentials\n- Secrets management configuration for GitHub Actions\n- npm scripts: `test`, `test:unit`, `test:integration`\n\n## Error Handling\n| Error | Cause | Solution |\n|-------|-------|----------|\n| Integration test auth failure | Expired sandbox token | Regenerate Developer Token in sandbox settings |\n| Flaky integration tests | Rate limits in CI | Add delays between integration tests, reduce parallelism |\n| Secret not available | Missing repository secret | Add secret in GitHub Settings > Secrets and variables |\n| Mock drift | Mock doesn't match real API behavior | Update mock when upgrading SDK version |\n\n## Resources\n- [GitHub Actions](https:\u002F\u002Fdocs.github.com\u002Fen\u002Factions)\n- [Jest Documentation](https:\u002F\u002Fjestjs.io\u002Fdocs\u002Fgetting-started)\n- [Evernote Sandbox](https:\u002F\u002Fsandbox.evernote.com)\n- [GitHub Encrypted Secrets](https:\u002F\u002Fdocs.github.com\u002Fen\u002Factions\u002Fsecurity-for-github-actions\u002Fsecurity-guides\u002Fusing-secrets-in-github-actions)\n\n## Next Steps\nFor deployment pipelines, see `evernote-deploy-integration`.\n\n## Examples\n\n**Unit test suite**: Test `NoteService.createNote()` against `MockNoteStore` to verify ENML wrapping, title sanitization, and tag handling without any API calls.\n\n**Sandbox integration test**: In CI, create a note in the sandbox, retrieve it by GUID, verify content matches, then delete it. Runs only on main branch merges.\n",{"name":5,"tags":24,"author":30,"license":15,"version":31,"description":32,"allowed-tools":33,"compatible-with":34},[25,26,27,28,29],"saas","evernote","deployment","testing","ci-cd","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Configure CI\u002FCD pipelines for Evernote integrations.\nUse when setting up automated testing, continuous integration,\nor deployment pipelines for Evernote projects.\nTrigger with phrases like \"evernote ci\", \"evernote github actions\",\n\"evernote pipeline\", \"automate evernote tests\".\n","Read, Write, Edit, Bash(npm:*), Grep","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--evernote-pack--evernote-ci-integration",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill evernote-ci-integration",{"tool":50,"command":51},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill evernote-ci-integration",{"tool":53,"command":54},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill evernote-ci-integration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--evernote-pack--evernote-ci-integration\u002FSKILL.md",true,[],[59,66,73,80,87,95],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]