[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F6FT89MPBMVR0HKFHACY8N":3,"skill-same:01M6F6FT89MPBMVR0HKFHACY8N":75},{"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":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6F6FT89MPBMVR0HKFHACY8N","evernote-incident-runbook",null,"Incident response runbook for Evernote integration issues.\nUse when troubleshooting production incidents, handling outages,\nor responding to Evernote service issues.\nTrigger with phrases like \"evernote incident\", \"evernote outage\",\n\"evernote emergency\", \"troubleshoot evernote production\".","Dicklesworthstone\u002Fpi_agent_rust","Dicklesworthstone","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F35050222?v=4","01M6CG26AR942CSVMN1M5E3DSE","Jeff Emanuel","01M6CG26EPP71PSHW1VDS71121",1992,"MIT","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsaas-packs\u002Fevernote-pack\u002Fskills\u002Fevernote-incident-runbook\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"runbook","evernote","evernote incident runbook","incident","edit","when","for","incidents","with","trigger","io","service","use","incident response","write","read","curl","grep","troubleshooting","Bash","Production","integration","issues","troubleshoot","2026-11-10 10:12:30",false,"---\nname: evernote-incident-runbook\ndescription: |\n  Incident response runbook for Evernote integration issues.\n  Use when troubleshooting production incidents, handling outages,\n  or responding to Evernote service issues.\n  Trigger with phrases like \"evernote incident\", \"evernote outage\",\n  \"evernote emergency\", \"troubleshoot evernote production\".\nallowed-tools: Read, Write, Edit, Bash(curl:*), Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\n---\n\n# Evernote Incident Runbook\n\n## Overview\n\nStep-by-step procedures for responding to Evernote integration incidents including outages, rate limits, authentication failures, and data issues.\n\n## Prerequisites\n\n- Access to monitoring dashboards\n- Production logs access\n- Evernote API credentials\n- Communication channels for escalation\n\n## Incident Classification\n\n| Severity | Impact | Response Time | Example |\n|----------|--------|---------------|---------|\n| P1 - Critical | All users affected | 15 min | Complete API outage |\n| P2 - High | Major feature broken | 30 min | OAuth failures |\n| P3 - Medium | Partial degradation | 2 hours | High error rate |\n| P4 - Low | Minor issues | 1 day | Slow response times |\n\n## Incident Response Procedures\n\n### INC-01: Complete API Outage\n\n**Symptoms:**\n- All Evernote API calls failing\n- 5xx errors from Evernote\n- Connection timeouts\n\n**Investigation:**\n\n```bash\n# Step 1: Check Evernote service status\ncurl -I https:\u002F\u002Fwww.evernote.com\u002F\ncurl -I https:\u002F\u002Fsandbox.evernote.com\u002F\n\n# Step 2: Check status page\n# https:\u002F\u002Fstatus.evernote.com\u002F\n```\n\n```javascript\n\u002F\u002F Step 3: Run diagnostic\nasync function diagnoseOutage() {\n  const results = {\n    timestamp: new Date().toISOString(),\n    checks: []\n  };\n\n  \u002F\u002F DNS resolution\n  try {\n    const dns = require('dns').promises;\n    const addresses = await dns.resolve4('www.evernote.com');\n    results.checks.push({ name: 'DNS', status: 'ok', addresses });\n  } catch (error) {\n    results.checks.push({ name: 'DNS', status: 'failed', error: error.message });\n  }\n\n  \u002F\u002F TCP connectivity\n  try {\n    const net = require('net');\n    await new Promise((resolve, reject) => {\n      const socket = net.connect(443, 'www.evernote.com');\n      socket.setTimeout(5000);\n      socket.on('connect', () => { socket.destroy(); resolve(); });\n      socket.on('error', reject);\n      socket.on('timeout', () => { socket.destroy(); reject(new Error('Timeout')); });\n    });\n    results.checks.push({ name: 'TCP', status: 'ok' });\n  } catch (error) {\n    results.checks.push({ name: 'TCP', status: 'failed', error: error.message });\n  }\n\n  \u002F\u002F HTTPS request\n  try {\n    const https = require('https');\n    await new Promise((resolve, reject) => {\n      const req = https.get('https:\u002F\u002Fwww.evernote.com\u002F', { timeout: 10000 }, (res) => {\n        results.checks.push({ name: 'HTTPS', status: 'ok', statusCode: res.statusCode });\n        resolve();\n      });\n      req.on('error', reject);\n    });\n  } catch (error) {\n    results.checks.push({ name: 'HTTPS', status: 'failed', error: error.message });\n  }\n\n  return results;\n}\n```\n\n**Mitigation:**\n\n1. Activate circuit breaker to prevent cascading failures\n2. Enable graceful degradation (show cached data)\n3. Display user-friendly error message\n4. Monitor Evernote status page\n\n```javascript\n\u002F\u002F Activate graceful degradation\nconst degradationMode = {\n  enabled: true,\n  reason: 'Evernote service unavailable',\n  startTime: Date.now(),\n\n  shouldServeFromCache: true,\n  shouldBlockWrites: true,\n  userMessage: 'Note syncing is temporarily unavailable. Your changes will sync when service is restored.'\n};\n\n\u002F\u002F Apply to endpoints\napp.use((req, res, next) => {\n  if (degradationMode.enabled) {\n    res.locals.degradationMode = degradationMode;\n  }\n  next();\n});\n```\n\n**Resolution:**\n1. Monitor Evernote status for resolution\n2. Gradually re-enable API calls\n3. Trigger sync for affected users\n4. Document incident timeline\n\n---\n\n### INC-02: Rate Limit Crisis\n\n**Symptoms:**\n- Frequent RATE_LIMIT_REACHED errors\n- rateLimitDuration > 300 seconds\n- Multiple users affected\n\n**Investigation:**\n\n```javascript\n\u002F\u002F Check rate limit metrics\nasync function analyzeRateLimits() {\n  const metrics = await prometheusQuery(`\n    sum(increase(evernote_rate_limits_total[1h])) by (api_key)\n  `);\n\n  const apiCallRate = await prometheusQuery(`\n    sum(rate(evernote_api_calls_total[5m])) by (operation)\n  `);\n\n  return {\n    rateLimitsLastHour: metrics,\n    currentCallRate: apiCallRate,\n    suspectedCauses: identifyCauses(apiCallRate)\n  };\n}\n\nfunction identifyCauses(callRate) {\n  const causes = [];\n\n  \u002F\u002F Check for polling abuse\n  if (callRate['NoteStore.getSyncState'] > 1) {\n    causes.push('Excessive sync state polling');\n  }\n\n  \u002F\u002F Check for inefficient requests\n  if (callRate['NoteStore.getResource'] > 10) {\n    causes.push('Individual resource fetching (should batch)');\n  }\n\n  return causes;\n}\n```\n\n**Mitigation:**\n\n```javascript\n\u002F\u002F Emergency rate limiting\nclass EmergencyRateLimiter {\n  constructor() {\n    this.globalPause = false;\n    this.pauseUntil = 0;\n  }\n\n  async activateEmergencyPause(durationSeconds) {\n    this.globalPause = true;\n    this.pauseUntil = Date.now() + (durationSeconds * 1000);\n\n    console.warn(`Emergency rate limit pause activated for ${durationSeconds}s`);\n\n    \u002F\u002F Notify operations\n    await alertOps('Emergency rate limit pause', {\n      duration: durationSeconds,\n      reason: 'Excessive rate limits detected'\n    });\n\n    \u002F\u002F Auto-deactivate\n    setTimeout(() => {\n      this.globalPause = false;\n      console.info('Emergency rate limit pause deactivated');\n    }, durationSeconds * 1000);\n  }\n\n  async checkBeforeRequest() {\n    if (this.globalPause) {\n      const waitTime = this.pauseUntil - Date.now();\n      if (waitTime > 0) {\n        throw new Error(`Rate limit emergency: retry in ${Math.ceil(waitTime \u002F 1000)}s`);\n      }\n    }\n  }\n}\n```\n\n**Resolution:**\n1. Identify and fix inefficient API usage\n2. Increase cache TTLs\n3. Implement request coalescing\n4. Request rate limit boost from Evernote\n\n---\n\n### INC-03: Authentication Failures\n\n**Symptoms:**\n- Users receiving auth errors\n- OAuth flow failing\n- Token rejections\n\n**Investigation:**\n\n```javascript\n\u002F\u002F Auth diagnostic\nasync function diagnoseAuthIssue(userId) {\n  const user = await db.users.findById(userId);\n  const token = await db.tokens.findByUserId(userId);\n\n  const diagnosis = {\n    userId,\n    hasToken: !!token,\n    tokenExpired: token ? (Date.now() > token.expiresAt) : null,\n    tokenExpiresIn: token ? Math.floor((token.expiresAt - Date.now()) \u002F 1000 \u002F 60 \u002F 60) + ' hours' : null\n  };\n\n  \u002F\u002F Test token validity\n  if (token && !diagnosis.tokenExpired) {\n    try {\n      const client = new Evernote.Client({ token: token.accessToken, sandbox: false });\n      const userStore = client.getUserStore();\n      await userStore.getUser();\n      diagnosis.tokenValid = true;\n    } catch (error) {\n      diagnosis.tokenValid = false;\n      diagnosis.tokenError = {\n        code: error.errorCode,\n        parameter: error.parameter\n      };\n    }\n  }\n\n  return diagnosis;\n}\n```\n\n**Common Causes & Fixes:**\n\n| Error Code | Cause | Fix |\n|------------|-------|-----|\n| 4 (INVALID_AUTH) | Token revoked | Re-authenticate user |\n| 5 (AUTH_EXPIRED) | Token expired | Re-authenticate user |\n| 3 (PERMISSION_DENIED) | Insufficient permissions | Check API key permissions |\n\n**Resolution:**\n```javascript\n\u002F\u002F Batch re-auth notification\nasync function notifyUsersToReauth(userIds) {\n  for (const userId of userIds) {\n    await sendNotification(userId, {\n      type: 'REAUTH_REQUIRED',\n      message: 'Please reconnect your Evernote account to continue syncing.',\n      action: { type: 'REDIRECT', url: '\u002Fauth\u002Fevernote' }\n    });\n\n    await db.tokens.markInvalid(userId);\n  }\n}\n```\n\n---\n\n### INC-04: Data Sync Issues\n\n**Symptoms:**\n- Notes not appearing\n- Sync state stuck\n- Missing changes\n\n**Investigation:**\n\n```javascript\n\u002F\u002F Sync state diagnostic\nasync function diagnoseSyncIssue(userId) {\n  const syncState = await db.syncState.findByUserId(userId);\n  const client = await getClientForUser(userId);\n\n  const remoteSyncState = await client.noteStore.getSyncState();\n\n  return {\n    localUSN: syncState.lastUpdateCount,\n    remoteUSN: remoteSyncState.updateCount,\n    behind: remoteSyncState.updateCount - syncState.lastUpdateCount,\n    lastSyncAt: syncState.lastSyncAt,\n    needsSync: remoteSyncState.updateCount > syncState.lastUpdateCount,\n    fullSyncRequired: syncState.fullSyncRequired\n  };\n}\n\n\u002F\u002F Force resync\nasync function forceResync(userId) {\n  await db.syncState.update(userId, {\n    lastUpdateCount: 0,\n    fullSyncRequired: true,\n    lastSyncAt: null\n  });\n\n  \u002F\u002F Queue sync job\n  await syncQueue.add('full-sync', { userId, priority: 'high' });\n\n  return { status: 'queued', message: 'Full resync initiated' };\n}\n```\n\n---\n\n## Incident Communication Templates\n\n### Status Page Update\n\n```markdown\n## [Investigating] Evernote Integration Issue\n\n**Time:** [TIMESTAMP]\n**Status:** Investigating\n\nWe are currently investigating issues with Evernote note synchronization.\nSome users may experience delays in note updates.\n\nWe will provide updates as we learn more.\n```\n\n### User Notification\n\n```markdown\n## Temporary Sync Delay\n\nHi [USER],\n\nWe're experiencing a temporary delay in syncing notes with Evernote.\nYour local changes are saved and will sync automatically when the\nissue is resolved.\n\nNo action is needed on your part.\n\nExpected resolution: Within 2 hours\n\nThank you for your patience.\n```\n\n### Resolution Update\n\n```markdown\n## [Resolved] Evernote Integration Issue\n\n**Time:** [TIMESTAMP]\n**Status:** Resolved\n\nThe Evernote synchronization issue has been resolved.\nAll notes should now be syncing normally.\n\n**Root Cause:** [BRIEF DESCRIPTION]\n**Duration:** [X hours Y minutes]\n**Impact:** [NUMBER] users affected\n\nWe apologize for any inconvenience.\n```\n\n## Post-Incident Checklist\n\n```markdown\n## Post-Incident Review\n\n### Timeline\n- [ ] Document incident timeline\n- [ ] Record all actions taken\n- [ ] Note what worked\u002Fdidn't work\n\n### Root Cause\n- [ ] Identify root cause\n- [ ] Determine contributing factors\n- [ ] Assess detection time\n\n### Prevention\n- [ ] Define preventive measures\n- [ ] Update monitoring\u002Falerts\n- [ ] Improve runbooks\n\n### Follow-up\n- [ ] Schedule post-mortem meeting\n- [ ] Assign action items\n- [ ] Update documentation\n```\n\n## Output\n\n- Incident classification guide\n- Step-by-step response procedures\n- Diagnostic scripts\n- Mitigation strategies\n- Communication templates\n- Post-incident checklist\n\n## Resources\n\n- [Evernote Status Page](https:\u002F\u002Fstatus.evernote.com\u002F)\n- [Evernote Developer Support](https:\u002F\u002Fdev.evernote.com\u002Fsupport\u002F)\n- [Error Handling](https:\u002F\u002Fdev.evernote.com\u002Fdoc\u002Farticles\u002Ferror_handling.php)\n\n## Next Steps\n\nFor data handling best practices, see `evernote-data-handling`.\n","# Evernote Incident Runbook\n\n## Overview\n\nStep-by-step procedures for responding to Evernote integration incidents including outages, rate limits, authentication failures, and data issues.\n\n## Prerequisites\n\n- Access to monitoring dashboards\n- Production logs access\n- Evernote API credentials\n- Communication channels for escalation\n\n## Incident Classification\n\n| Severity | Impact | Response Time | Example |\n|----------|--------|---------------|---------|\n| P1 - Critical | All users affected | 15 min | Complete API outage |\n| P2 - High | Major feature broken | 30 min | OAuth failures |\n| P3 - Medium | Partial degradation | 2 hours | High error rate |\n| P4 - Low | Minor issues | 1 day | Slow response times |\n\n## Incident Response Procedures\n\n### INC-01: Complete API Outage\n\n**Symptoms:**\n- All Evernote API calls failing\n- 5xx errors from Evernote\n- Connection timeouts\n\n**Investigation:**\n\n```bash\n# Step 1: Check Evernote service status\ncurl -I https:\u002F\u002Fwww.evernote.com\u002F\ncurl -I https:\u002F\u002Fsandbox.evernote.com\u002F\n\n# Step 2: Check status page\n# https:\u002F\u002Fstatus.evernote.com\u002F\n```\n\n```javascript\n\u002F\u002F Step 3: Run diagnostic\nasync function diagnoseOutage() {\n  const results = {\n    timestamp: new Date().toISOString(),\n    checks: []\n  };\n\n  \u002F\u002F DNS resolution\n  try {\n    const dns = require('dns').promises;\n    const addresses = await dns.resolve4('www.evernote.com');\n    results.checks.push({ name: 'DNS', status: 'ok', addresses });\n  } catch (error) {\n    results.checks.push({ name: 'DNS', status: 'failed', error: error.message });\n  }\n\n  \u002F\u002F TCP connectivity\n  try {\n    const net = require('net');\n    await new Promise((resolve, reject) => {\n      const socket = net.connect(443, 'www.evernote.com');\n      socket.setTimeout(5000);\n      socket.on('connect', () => { socket.destroy(); resolve(); });\n      socket.on('error', reject);\n      socket.on('timeout', () => { socket.destroy(); reject(new Error('Timeout')); });\n    });\n    results.checks.push({ name: 'TCP', status: 'ok' });\n  } catch (error) {\n    results.checks.push({ name: 'TCP', status: 'failed', error: error.message });\n  }\n\n  \u002F\u002F HTTPS request\n  try {\n    const https = require('https');\n    await new Promise((resolve, reject) => {\n      const req = https.get('https:\u002F\u002Fwww.evernote.com\u002F', { timeout: 10000 }, (res) => {\n        results.checks.push({ name: 'HTTPS', status: 'ok', statusCode: res.statusCode });\n        resolve();\n      });\n      req.on('error', reject);\n    });\n  } catch (error) {\n    results.checks.push({ name: 'HTTPS', status: 'failed', error: error.message });\n  }\n\n  return results;\n}\n```\n\n**Mitigation:**\n\n1. Activate circuit breaker to prevent cascading failures\n2. Enable graceful degradation (show cached data)\n3. Display user-friendly error message\n4. Monitor Evernote status page\n\n```javascript\n\u002F\u002F Activate graceful degradation\nconst degradationMode = {\n  enabled: true,\n  reason: 'Evernote service unavailable',\n  startTime: Date.now(),\n\n  shouldServeFromCache: true,\n  shouldBlockWrites: true,\n  userMessage: 'Note syncing is temporarily unavailable. Your changes will sync when service is restored.'\n};\n\n\u002F\u002F Apply to endpoints\napp.use((req, res, next) => {\n  if (degradationMode.enabled) {\n    res.locals.degradationMode = degradationMode;\n  }\n  next();\n});\n```\n\n**Resolution:**\n1. Monitor Evernote status for resolution\n2. Gradually re-enable API calls\n3. Trigger sync for affected users\n4. Document incident timeline\n\n---\n\n### INC-02: Rate Limit Crisis\n\n**Symptoms:**\n- Frequent RATE_LIMIT_REACHED errors\n- rateLimitDuration > 300 seconds\n- Multiple users affected\n\n**Investigation:**\n\n```javascript\n\u002F\u002F Check rate limit metrics\nasync function analyzeRateLimits() {\n  const metrics = await prometheusQuery(`\n    sum(increase(evernote_rate_limits_total[1h])) by (api_key)\n  `);\n\n  const apiCallRate = await prometheusQuery(`\n    sum(rate(evernote_api_calls_total[5m])) by (operation)\n  `);\n\n  return {\n    rateLimitsLastHour: metrics,\n    currentCallRate: apiCallRate,\n    suspectedCauses: identifyCauses(apiCallRate)\n  };\n}\n\nfunction identifyCauses(callRate) {\n  const causes = [];\n\n  \u002F\u002F Check for polling abuse\n  if (callRate['NoteStore.getSyncState'] > 1) {\n    causes.push('Excessive sync state polling');\n  }\n\n  \u002F\u002F Check for inefficient requests\n  if (callRate['NoteStore.getResource'] > 10) {\n    causes.push('Individual resource fetching (should batch)');\n  }\n\n  return causes;\n}\n```\n\n**Mitigation:**\n\n```javascript\n\u002F\u002F Emergency rate limiting\nclass EmergencyRateLimiter {\n  constructor() {\n    this.globalPause = false;\n    this.pauseUntil = 0;\n  }\n\n  async activateEmergencyPause(durationSeconds) {\n    this.globalPause = true;\n    this.pauseUntil = Date.now() + (durationSeconds * 1000);\n\n    console.warn(`Emergency rate limit pause activated for ${durationSeconds}s`);\n\n    \u002F\u002F Notify operations\n    await alertOps('Emergency rate limit pause', {\n      duration: durationSeconds,\n      reason: 'Excessive rate limits detected'\n    });\n\n    \u002F\u002F Auto-deactivate\n    setTimeout(() => {\n      this.globalPause = false;\n      console.info('Emergency rate limit pause deactivated');\n    }, durationSeconds * 1000);\n  }\n\n  async checkBeforeRequest() {\n    if (this.globalPause) {\n      const waitTime = this.pauseUntil - Date.now();\n      if (waitTime > 0) {\n        throw new Error(`Rate limit emergency: retry in ${Math.ceil(waitTime \u002F 1000)}s`);\n      }\n    }\n  }\n}\n```\n\n**Resolution:**\n1. Identify and fix inefficient API usage\n2. Increase cache TTLs\n3. Implement request coalescing\n4. Request rate limit boost from Evernote\n\n---\n\n### INC-03: Authentication Failures\n\n**Symptoms:**\n- Users receiving auth errors\n- OAuth flow failing\n- Token rejections\n\n**Investigation:**\n\n```javascript\n\u002F\u002F Auth diagnostic\nasync function diagnoseAuthIssue(userId) {\n  const user = await db.users.findById(userId);\n  const token = await db.tokens.findByUserId(userId);\n\n  const diagnosis = {\n    userId,\n    hasToken: !!token,\n    tokenExpired: token ? (Date.now() > token.expiresAt) : null,\n    tokenExpiresIn: token ? Math.floor((token.expiresAt - Date.now()) \u002F 1000 \u002F 60 \u002F 60) + ' hours' : null\n  };\n\n  \u002F\u002F Test token validity\n  if (token && !diagnosis.tokenExpired) {\n    try {\n      const client = new Evernote.Client({ token: token.accessToken, sandbox: false });\n      const userStore = client.getUserStore();\n      await userStore.getUser();\n      diagnosis.tokenValid = true;\n    } catch (error) {\n      diagnosis.tokenValid = false;\n      diagnosis.tokenError = {\n        code: error.errorCode,\n        parameter: error.parameter\n      };\n    }\n  }\n\n  return diagnosis;\n}\n```\n\n**Common Causes & Fixes:**\n\n| Error Code | Cause | Fix |\n|------------|-------|-----|\n| 4 (INVALID_AUTH) | Token revoked | Re-authenticate user |\n| 5 (AUTH_EXPIRED) | Token expired | Re-authenticate user |\n| 3 (PERMISSION_DENIED) | Insufficient permissions | Check API key permissions |\n\n**Resolution:**\n```javascript\n\u002F\u002F Batch re-auth notification\nasync function notifyUsersToReauth(userIds) {\n  for (const userId of userIds) {\n    await sendNotification(userId, {\n      type: 'REAUTH_REQUIRED',\n      message: 'Please reconnect your Evernote account to continue syncing.',\n      action: { type: 'REDIRECT', url: '\u002Fauth\u002Fevernote' }\n    });\n\n    await db.tokens.markInvalid(userId);\n  }\n}\n```\n\n---\n\n### INC-04: Data Sync Issues\n\n**Symptoms:**\n- Notes not appearing\n- Sync state stuck\n- Missing changes\n\n**Investigation:**\n\n```javascript\n\u002F\u002F Sync state diagnostic\nasync function diagnoseSyncIssue(userId) {\n  const syncState = await db.syncState.findByUserId(userId);\n  const client = await getClientForUser(userId);\n\n  const remoteSyncState = await client.noteStore.getSyncState();\n\n  return {\n    localUSN: syncState.lastUpdateCount,\n    remoteUSN: remoteSyncState.updateCount,\n    behind: remoteSyncState.updateCount - syncState.lastUpdateCount,\n    lastSyncAt: syncState.lastSyncAt,\n    needsSync: remoteSyncState.updateCount > syncState.lastUpdateCount,\n    fullSyncRequired: syncState.fullSyncRequired\n  };\n}\n\n\u002F\u002F Force resync\nasync function forceResync(userId) {\n  await db.syncState.update(userId, {\n    lastUpdateCount: 0,\n    fullSyncRequired: true,\n    lastSyncAt: null\n  });\n\n  \u002F\u002F Queue sync job\n  await syncQueue.add('full-sync', { userId, priority: 'high' });\n\n  return { status: 'queued', message: 'Full resync initiated' };\n}\n```\n\n---\n\n## Incident Communication Templates\n\n### Status Page Update\n\n```markdown\n## [Investigating] Evernote Integration Issue\n\n**Time:** [TIMESTAMP]\n**Status:** Investigating\n\nWe are currently investigating issues with Evernote note synchronization.\nSome users may experience delays in note updates.\n\nWe will provide updates as we learn more.\n```\n\n### User Notification\n\n```markdown\n## Temporary Sync Delay\n\nHi [USER],\n\nWe're experiencing a temporary delay in syncing notes with Evernote.\nYour local changes are saved and will sync automatically when the\nissue is resolved.\n\nNo action is needed on your part.\n\nExpected resolution: Within 2 hours\n\nThank you for your patience.\n```\n\n### Resolution Update\n\n```markdown\n## [Resolved] Evernote Integration Issue\n\n**Time:** [TIMESTAMP]\n**Status:** Resolved\n\nThe Evernote synchronization issue has been resolved.\nAll notes should now be syncing normally.\n\n**Root Cause:** [BRIEF DESCRIPTION]\n**Duration:** [X hours Y minutes]\n**Impact:** [NUMBER] users affected\n\nWe apologize for any inconvenience.\n```\n\n## Post-Incident Checklist\n\n```markdown\n## Post-Incident Review\n\n### Timeline\n- [ ] Document incident timeline\n- [ ] Record all actions taken\n- [ ] Note what worked\u002Fdidn't work\n\n### Root Cause\n- [ ] Identify root cause\n- [ ] Determine contributing factors\n- [ ] Assess detection time\n\n### Prevention\n- [ ] Define preventive measures\n- [ ] Update monitoring\u002Falerts\n- [ ] Improve runbooks\n\n### Follow-up\n- [ ] Schedule post-mortem meeting\n- [ ] Assign action items\n- [ ] Update documentation\n```\n\n## Output\n\n- Incident classification guide\n- Step-by-step response procedures\n- Diagnostic scripts\n- Mitigation strategies\n- Communication templates\n- Post-incident checklist\n\n## Resources\n\n- [Evernote Status Page](https:\u002F\u002Fstatus.evernote.com\u002F)\n- [Evernote Developer Support](https:\u002F\u002Fdev.evernote.com\u002Fsupport\u002F)\n- [Error Handling](https:\u002F\u002Fdev.evernote.com\u002Fdoc\u002Farticles\u002Ferror_handling.php)\n\n## Next Steps\n\nFor data handling best practices, see `evernote-data-handling`.\n",{"name":5,"author":48,"license":15,"version":49,"description":50,"allowed-tools":51},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Incident response runbook for Evernote integration issues.\nUse when troubleshooting production incidents, handling outages,\nor responding to Evernote service issues.\nTrigger with phrases like \"evernote incident\", \"evernote outage\",\n\"evernote emergency\", \"troubleshoot evernote production\".\n","Read, Write, Edit, Bash(curl:*), Grep","main","90b50ed0778745a80fd5bfb13b1843d45b9e82f7","tests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsaas-packs\u002Fevernote-pack\u002Fskills\u002Fevernote-incident-runbook",233,"https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust","https:\u002F\u002Fgithub.com\u002FDicklesworthstone","https:\u002F\u002Fwww.jeffreyemanuel.com\u002F","Building in NY","2026-11-15 01:54:15",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add Dicklesworthstone\u002Fpi_agent_rust --skill evernote-incident-runbook",{"tool":67,"command":68},"bunx","bunx skills add Dicklesworthstone\u002Fpi_agent_rust --skill evernote-incident-runbook",{"tool":70,"command":71},"pnpm","pnpm dlx skills add Dicklesworthstone\u002Fpi_agent_rust --skill evernote-incident-runbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Fplugins-community\u002Fplugins\u002Fsaas-packs\u002Fevernote-pack\u002Fskills\u002Fevernote-incident-runbook\u002FSKILL.md",true,[],[76,109,143,166,192,219],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":89,"publishedAt":108},"01M6FCR7G5A005P364Z6ZWCJDP","theme-factory","Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors\u002Ffonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Ftheme-factory\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fcreative-design\u002Ftheme-factory\u002FSKILL.md",[84],{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",[90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,27,106,107],"theme factory","factory","theme","docs","toolkit","generate","artifacts","SET","fly","slides","landing","html","styling","artifact","pages","themes","you","fonts","2026-11-11 15:11:14",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":119,"publishedAt":43},"01M6FEGPPK0ZTKCCM0R3E3KS33","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[116],{"categoryNo":117,"categoryName":118,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000009","前端开发",[120,121,96,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,31,101,137,138,139,140,25,141,142],"web artifacts builder","web","artifacts builder","builder","frontend","css","components","react","component","routing","state management","state","shadcn","file","ui","Tools","Tailwind","single-file","simple","ui components","multi","jsx","suite",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":147,"sourceHtmlUrl":148,"categories":149,"keywords":154,"publishedAt":43},"01M6FEE9VTK1W4GY21AKREJXRG","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[150,153],{"categoryNo":151,"categoryName":152,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":117,"categoryName":118,"taxonomyType":87,"taxonomyTypeDesc":88},[155,156,157,124,158,159,121,160,94,161,134,162,163,164,165,27,25],"testing","webapp testing","webapp","screenshots","playwright","debugging","browser","logs","applications","behavior","local",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":170,"sourceHtmlUrl":171,"categories":172,"keywords":173,"publishedAt":43},"01M6FE20F7ZTQBFWKF4MPJ2SBX","neuropixels-analysis","Neuropixels neural recording analysis. Load SpikeGLX\u002FOpenEphys data, preprocess, motion correction, Kilosort4 spike sorting, quality metrics, Allen\u002FIBL curation, AI-assisted visual analysis, for Neuropixels 1.0\u002F2.0 extracellular electrophysiology. Use when working with neural recordings, spike sorting, extracellular electrophysiology, or when the user mentions Neuropixels, SpikeGLX, Open Ephys, Kilosort, quality metrics, or unit curation.","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fneuropixels-analysis\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fscientific\u002Fneuropixels-analysis\u002FSKILL.md",[],[174,175,176,177,178,179,180,181,31,182,183,184,185,186,187,188,27,189,190,191,25,24],"analysis","neuropixels analysis","spike","metrics","data","open","quality","user","recordings","Neural","motion","visual","quality metrics","unit","sorting","curation","recording","load",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":196,"sourceHtmlUrl":197,"categories":198,"keywords":202,"publishedAt":43},"01M6FDP0PDK6F1GGX395C7625Z","skill-creator","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fskill-creator\u002FSKILL.md",[199],{"categoryNo":200,"categoryName":201,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000023","Skill与智能体开发",[203,204,205,206,207,208,209,210,211,212,213,214,215,216,27,25,217,24,218],"skill creator","creator","workflows","create","update","capabilities","knowledge","tool","integrations","specialized","guide","new skill","existing skill","users","Existing","new",{"skillNo":220,"name":221,"nameZh":6,"description":222,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":223,"sourceHtmlUrl":224,"categories":225,"keywords":227,"publishedAt":43},"01M6FDM8Y7VK7NYG9SM7QPA3PW","notebooklm","Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth. Drastically reduced hallucinations through document-only responses.","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fnotebooklm\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FDicklesworthstone\u002Fpi_agent_rust\u002Fblob\u002Fmain\u002Ftests\u002Fext_conformance\u002Fartifacts\u002Ftemplates-davila7\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fnotebooklm\u002FSKILL.md",[226],{"categoryNo":200,"categoryName":201,"taxonomyType":87,"taxonomyTypeDesc":88},[221,228,229,230,231,232,233,161,234,235,31,236,237,238,239,25,240],"google","browser automation","gemini","automation","auth","code","library","management","only","document","query","Citation","source"]