[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78ZP0WHC8EPZX9JPYVBQZ7S":3,"skill-same:01M78ZP0WHC8EPZX9JPYVBQZ7S":56},{"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":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M78ZP0WHC8EPZX9JPYVBQZ7S","evernote-incident-runbook",null,"Manage incident response 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\".","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-incident-runbook\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: evernote-incident-runbook\ndescription: |\n  Manage incident response 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>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, evernote, incident-response]\n---\n# Evernote Incident Runbook\n\n## Overview\nStep-by-step procedures for responding to Evernote integration incidents including API outages, rate limit escalations, authentication failures, data sync issues, and quota exhaustion.\n\n## Prerequisites\n- Access to monitoring dashboards and production logs\n- Production Evernote API credentials\n- Communication channels for escalation (Slack, PagerDuty)\n\n## Instructions\n\n### Incident Classification\n\n| Severity | Symptoms | Response Time |\n|----------|----------|---------------|\n| P1 - Critical | All Evernote API calls failing, data loss risk | 15 minutes |\n| P2 - High | Persistent rate limits, auth failures for multiple users | 1 hour |\n| P3 - Medium | Intermittent errors, degraded sync performance | 4 hours |\n| P4 - Low | Single user issues, non-critical feature affected | Next business day |\n\n### Step 1: Triage\n\nCheck Evernote's status page first. If Evernote is down, activate the circuit breaker and wait.\n\n```bash\n# Check Evernote service status\ncurl -sf https:\u002F\u002Fstatus.evernote.com\u002Fapi\u002Fv2\u002Fstatus.json | jq '.status'\n\n# Check your API connectivity\ncurl -sf -H \"Authorization: Bearer $EVERNOTE_TOKEN\" \\\n  https:\u002F\u002Fwww.evernote.com\u002Fshard\u002Fs1\u002Fnotestore | head -20\n\n# Check error rate in logs (last 15 min)\ngrep -c 'EDAMSystemException' \u002Fvar\u002Flog\u002Fevernote-app.log\n```\n\n### Step 2: Rate Limit Escalation\n\nIf rate limits are persistent: reduce API call frequency, increase delays between batch operations, and contact Evernote developer support for a rate limit increase.\n\n### Step 3: Authentication Failure\n\nFor auth failures: verify tokens are not expired (`edam_expires`), check that production credentials match the production endpoint (`sandbox: false`), and test with a fresh Developer Token to isolate the issue.\n\n### Step 4: Sync Failure Recovery\n\nFor sync issues: compare local USN with server USN via `getSyncState()`. If gap is too large, reset to full sync from USN 0. Verify data integrity after re-sync.\n\n### Step 5: Mitigation Strategies\n\n- **Circuit breaker**: Disable Evernote API calls after N consecutive failures. Retry after cooldown period.\n- **Graceful degradation**: Serve cached data when API is unavailable. Queue writes for retry.\n- **Failover**: Switch to polling-based sync if webhooks stop arriving.\n\n### Post-Incident\n\n- Document root cause and timeline\n- Update runbook with new failure modes discovered\n- Adjust alert thresholds if false positive or missed detection\n- Review and improve circuit breaker settings\n\nFor the complete diagnostic scripts, mitigation implementations, and communication templates, see [Implementation Guide](references\u002Fimplementation-guide.md).\n\n## Output\n- Incident severity classification table\n- Triage diagnostic commands for quick assessment\n- Rate limit, auth, and sync failure response procedures\n- Circuit breaker and graceful degradation patterns\n- Post-incident review checklist\n\n## Error Handling\n| Incident Type | Diagnostic | Mitigation |\n|---------------|------------|------------|\n| API outage | Check `status.evernote.com` | Activate circuit breaker, serve cached data |\n| Rate limit storm | Check `evernote_rate_limits_total` metric | Reduce batch sizes, increase delays |\n| Mass auth failure | Verify token expiration dates in DB | Trigger re-auth flow for affected users |\n| Sync data loss | Compare local vs server note counts | Full re-sync from USN 0 |\n\n## Resources\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\nFor data handling best practices, see `evernote-data-handling`.\n\n## Examples\n\n**API outage response**: Alert fires, on-call checks status page, confirms Evernote outage, activates circuit breaker, posts status update to internal Slack, monitors for recovery, then gradually re-enables API calls.\n\n**Rate limit recovery**: Persistent `RATE_LIMIT_REACHED` errors detected. Reduce batch size from 100 to 10, increase delay to 500ms, clear the request queue, and contact Evernote support if limits continue after 1 hour.\n","# Evernote Incident Runbook\n\n## Overview\nStep-by-step procedures for responding to Evernote integration incidents including API outages, rate limit escalations, authentication failures, data sync issues, and quota exhaustion.\n\n## Prerequisites\n- Access to monitoring dashboards and production logs\n- Production Evernote API credentials\n- Communication channels for escalation (Slack, PagerDuty)\n\n## Instructions\n\n### Incident Classification\n\n| Severity | Symptoms | Response Time |\n|----------|----------|---------------|\n| P1 - Critical | All Evernote API calls failing, data loss risk | 15 minutes |\n| P2 - High | Persistent rate limits, auth failures for multiple users | 1 hour |\n| P3 - Medium | Intermittent errors, degraded sync performance | 4 hours |\n| P4 - Low | Single user issues, non-critical feature affected | Next business day |\n\n### Step 1: Triage\n\nCheck Evernote's status page first. If Evernote is down, activate the circuit breaker and wait.\n\n```bash\n# Check Evernote service status\ncurl -sf https:\u002F\u002Fstatus.evernote.com\u002Fapi\u002Fv2\u002Fstatus.json | jq '.status'\n\n# Check your API connectivity\ncurl -sf -H \"Authorization: Bearer $EVERNOTE_TOKEN\" \\\n  https:\u002F\u002Fwww.evernote.com\u002Fshard\u002Fs1\u002Fnotestore | head -20\n\n# Check error rate in logs (last 15 min)\ngrep -c 'EDAMSystemException' \u002Fvar\u002Flog\u002Fevernote-app.log\n```\n\n### Step 2: Rate Limit Escalation\n\nIf rate limits are persistent: reduce API call frequency, increase delays between batch operations, and contact Evernote developer support for a rate limit increase.\n\n### Step 3: Authentication Failure\n\nFor auth failures: verify tokens are not expired (`edam_expires`), check that production credentials match the production endpoint (`sandbox: false`), and test with a fresh Developer Token to isolate the issue.\n\n### Step 4: Sync Failure Recovery\n\nFor sync issues: compare local USN with server USN via `getSyncState()`. If gap is too large, reset to full sync from USN 0. Verify data integrity after re-sync.\n\n### Step 5: Mitigation Strategies\n\n- **Circuit breaker**: Disable Evernote API calls after N consecutive failures. Retry after cooldown period.\n- **Graceful degradation**: Serve cached data when API is unavailable. Queue writes for retry.\n- **Failover**: Switch to polling-based sync if webhooks stop arriving.\n\n### Post-Incident\n\n- Document root cause and timeline\n- Update runbook with new failure modes discovered\n- Adjust alert thresholds if false positive or missed detection\n- Review and improve circuit breaker settings\n\nFor the complete diagnostic scripts, mitigation implementations, and communication templates, see [Implementation Guide](references\u002Fimplementation-guide.md).\n\n## Output\n- Incident severity classification table\n- Triage diagnostic commands for quick assessment\n- Rate limit, auth, and sync failure response procedures\n- Circuit breaker and graceful degradation patterns\n- Post-incident review checklist\n\n## Error Handling\n| Incident Type | Diagnostic | Mitigation |\n|---------------|------------|------------|\n| API outage | Check `status.evernote.com` | Activate circuit breaker, serve cached data |\n| Rate limit storm | Check `evernote_rate_limits_total` metric | Reduce batch sizes, increase delays |\n| Mass auth failure | Verify token expiration dates in DB | Trigger re-auth flow for affected users |\n| Sync data loss | Compare local vs server note counts | Full re-sync from USN 0 |\n\n## Resources\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\nFor data handling best practices, see `evernote-data-handling`.\n\n## Examples\n\n**API outage response**: Alert fires, on-call checks status page, confirms Evernote outage, activates circuit breaker, posts status update to internal Slack, monitors for recovery, then gradually re-enables API calls.\n\n**Rate limit recovery**: Persistent `RATE_LIMIT_REACHED` errors detected. Reduce batch size from 100 to 10, increase delay to 500ms, clear the request queue, and contact Evernote support if limits continue after 1 hour.\n",{"name":5,"tags":24,"author":28,"license":15,"version":29,"description":30,"allowed-tools":31,"compatible-with":32},[25,26,27],"saas","evernote","incident-response","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Manage incident response 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","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--evernote-pack--evernote-incident-runbook",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":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill evernote-incident-runbook",{"tool":48,"command":49},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill evernote-incident-runbook",{"tool":51,"command":52},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill evernote-incident-runbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--evernote-pack--evernote-incident-runbook\u002FSKILL.md",true,[],[57,64,71,78,85,93],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"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":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"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",[],[]]