evernote-incident-runbook

Incident response runbook for Evernote integration issues. Use when troubleshooting production incidents, handling outages, or responding to Evernote service issues. Trigger with phrases like "evernote incident", "evernote outage", "evernote emergency", "troubleshoot evernote production".

Install with Tessl CLI

npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill evernote-incident-runbook

What are skills?

Review — 83%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Validation — 9 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Evaluation results

100%

39%

Evernote Integration Outage: Emergency Response Implementation

INC-01 outage response and graceful degradation

Criteria

Without context

With context

P1 severity classification

100%

15-minute response time

100%

curl to production host

100%

DNS resolution check

100%

TCP connectivity check

100%

HTTPS request check

100%

shouldServeFromCache true

100%

shouldBlockWrites true

100%

Degradation middleware

100%

Investigating header

100%

Resolution template fields

71%

100%

Resolved header

100%

Without context: $0.5350 · 2m 34s · 25 turns · 26 in / 9,018 out tokens

With context: $0.7215 · 2m 30s · 31 turns · 112 in / 8,692 out tokens

100%

40%

Evernote Rate Limit Emergency: Investigation and Mitigation

INC-02 rate limit crisis and emergency rate limiter

Criteria

Without context

With context

prometheusQuery for rate limits

88%

100%

prometheusQuery for call rate

100%

getSyncState polling check

100%

getResource batching check

100%

EmergencyRateLimiter class

100%

globalPause boolean

37%

100%

pauseUntil timestamp

50%

100%

setTimeout auto-deactivate

100%

checkBeforeRequest method

44%

100%

Request coalescing in plan

80%

100%

Cache TTL increase in plan

70%

100%

Without context: $0.5680 · 3m 12s · 19 turns · 20 in / 11,830 out tokens

With context: $0.7430 · 2m 58s · 28 turns · 1,799 in / 9,448 out tokens

100%

32%

Evernote Authentication Wave: Diagnosis and User Recovery

INC-03 authentication failure diagnosis and batch re-auth

Criteria

Without context

With context

P2 severity

100%

30-minute response time

100%

hasToken check

100%

tokenExpired check

100%

tokenExpiresIn field

100%

Live token validation

100%

tokenValid field

100%

Error code 4 = revoked

100%

Error code 5 = expired

100%

Error code 3 = permissions

100%

REAUTH_REQUIRED notification type

100%

markInvalid called

100%

Without context: $0.6106 · 2m 43s · 32 turns · 31 in / 9,485 out tokens

With context: $0.6330 · 2m 16s · 28 turns · 59 in / 7,529 out tokens

Evaluated: about 17 hours ago
Agent: Claude Code

Table of Contents

Evernote Integration Outage: Emergency Response Implementation Evernote Rate Limit Emergency: Investigation and Mitigation Evernote Authentication Wave: Diagnosis and User Recovery

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.