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-runbook85
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/skillValidation for skill structure
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured description with excellent trigger term coverage and clear 'when to use' guidance. The main weakness is the lack of specific concrete actions - it describes the category of work (incident response) but not the specific capabilities the skill provides. Adding 2-3 specific actions would strengthen the description.
Suggestions
Add specific concrete actions the runbook covers, such as 'diagnose API failures, check authentication tokens, verify webhook configurations, escalate to Evernote support'
Consider adding file types or artifacts this skill produces, such as 'generates incident reports' or 'creates status updates'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Evernote integration issues) and general actions (troubleshooting, handling outages, responding to issues), but doesn't list specific concrete actions like 'check API status', 'restart services', or 'escalate to on-call'. | 2 / 3 |
Completeness | Clearly answers both what (incident response runbook for Evernote integration issues) and when (troubleshooting production incidents, handling outages, responding to service issues) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'evernote incident', 'evernote outage', 'evernote emergency', 'troubleshoot evernote production'. These are realistic terms for incident response scenarios. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Evernote' as a specific service name combined with 'incident', 'outage', and 'emergency' terms. Unlikely to conflict with general troubleshooting or other integration skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong incident runbook with excellent actionability - the diagnostic scripts, mitigation code, and error code tables are immediately usable. The workflow clarity is good with clear sequences for each incident type. However, the document is lengthy and could benefit from better progressive disclosure by moving detailed code to reference files while keeping the SKILL.md as a concise overview with links.
Suggestions
Consider moving detailed diagnostic functions (diagnoseOutage, analyzeRateLimits, etc.) to a separate DIAGNOSTICS.md file and linking from the main runbook
The communication templates section could be a separate TEMPLATES.md file to reduce main document length
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The runbook is comprehensive but includes some verbose elements like full diagnostic functions that could be condensed. The communication templates and post-incident checklist add value but could be more concise or linked externally. | 2 / 3 |
Actionability | Provides fully executable code for diagnostics, mitigation, and resolution. Bash commands, JavaScript functions, and specific error code mappings are copy-paste ready with clear context. | 3 / 3 |
Workflow Clarity | Each incident type follows a clear Investigation → Mitigation → Resolution sequence. Explicit validation steps are present (e.g., 'Test token validity', 'Monitor Evernote status for resolution'). The severity classification table provides clear response time expectations. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the document is quite long (300+ lines) and could benefit from splitting detailed diagnostic scripts into separate reference files. The 'Next Steps' reference to another skill is good, but inline code blocks could be externalized. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Reviewed
Table of Contents
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.