Evernote Incident Runbook

Name: Evernote Incident Runbook
Author: micsapp

ASecurity

Manage incident response 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".

4 stars
0 votes
0 copies
4 views
Added September 10, 2026

developmentphpbashapi

Works with

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 10, 2026

npx -y skills add micsapp/micstec-skills --skill evernote-incident-runbook --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Evernote Incident Runbook?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Evernote Incident Runbook

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/micsapp-evernote-incident-runbook/badge)](https://www.skillsdirectory.com/skills/micsapp-evernote-incident-runbook)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: evernote-incident-runbook
description: |
  Manage incident response 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".
allowed-tools: Read, Write, Edit, Bash(curl:*), Grep
version: 1.0.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
compatible-with: claude-code, codex, openclaw
---
# Evernote Incident Runbook

## Overview
Step-by-step procedures for responding to Evernote integration incidents including outages, rate limits, authentication failures, and data issues.

## Prerequisites
- Access to monitoring dashboards
- Production logs access
- Evernote API credentials
- Communication channels for escalation

## Instructions

1. See implementation guide for detailed steps.

2. For full implementation details and code examples, load:
3. `references/implementation-guide.md`

## Output
- Incident classification guide
- Step-by-step response procedures
- Diagnostic scripts
- Mitigation strategies
- Communication templates
- Post-incident checklist

## Resources
- [Evernote Status Page](https://status.evernote.com/)
- [Evernote Developer Support](https://dev.evernote.com/support/)
- [Error Handling](https://dev.evernote.com/doc/articles/error_handling.php)

## Next Steps
For data handling best practices, see `evernote-data-handling`.

## Error Handling

| Error | Cause | Resolution |
|-------|-------|------------|
| Authentication failure | Invalid or expired credentials | Refresh tokens or re-authenticate with Evernote Incident Runbook |
| Configuration conflict | Incompatible settings detected | Review and resolve conflicting parameters |
| Resource not found | Referenced resource missing | Verify resource exists and permissions are correct |

## Examples

**Basic usage**: Apply evernote incident runbook to a standard project setup with default configuration options.

**Advanced scenario**: Customize evernote incident runbook for production environments with multiple constraints and team-specific requirements.