evernote-incident-runbook
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".
77
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/evernote-pack/skills/evernote-incident-runbook/SKILL.mdQuality
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 solid description with excellent trigger terms and completeness, clearly specifying both what the skill does and when to use it. Its main weakness is that the 'what' portion is somewhat general—it says 'manage incident response' without detailing the specific actions or steps involved. The Evernote-specific focus makes it highly distinctive.
Suggestions
Add more specific concrete actions to the capability description, e.g., 'check Evernote API status, review integration logs, escalate outages, coordinate rollback procedures'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (incident response for Evernote integration) and some actions (troubleshooting, handling outages, responding to service issues), but doesn't list specific concrete actions like 'check API status', 'rollback integration', 'notify stakeholders', etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (manage incident response for Evernote integration issues) and 'when' (explicit 'Use when' clause with troubleshooting, outages, service issues, plus a 'Trigger with' clause listing specific phrases). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'evernote incident', 'evernote outage', 'evernote emergency', 'troubleshoot evernote production'. These are phrases users would naturally say when facing Evernote integration issues. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific combination of 'Evernote' + 'incident response'. The trigger terms are narrowly scoped to Evernote production incidents, making conflicts with other skills very unlikely. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a reasonably structured incident runbook with good organization and severity classification, but it falls short on actionability—most steps after the initial triage are prose descriptions rather than executable commands or code. The workflow lacks explicit validation checkpoints and decision gates, which are critical for incident response procedures involving data integrity risks.
Suggestions
Add concrete, executable diagnostic commands for Steps 2-4 (e.g., actual code to check token expiration, compare USNs, implement circuit breaker logic) instead of prose descriptions.
Add explicit validation checkpoints and decision gates between steps, especially before destructive operations like full re-sync from USN 0 (e.g., 'Verify backup exists before resetting sync state').
Remove the 'Output' section which merely restates the skill's table of contents and adds no actionable value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary sections like the 'Output' section which just restates what the skill contains, and the 'Examples' at the end are somewhat redundant with the steps above. The overview and prerequisites are reasonable but could be tighter. | 2 / 3 |
Actionability | Step 1 has concrete bash commands which is good, but Steps 2-4 are vague prose descriptions rather than executable commands or code. 'Contact Evernote developer support' and 'compare local USN with server USN via getSyncState()' lack concrete implementation. The mitigation strategies are described conceptually rather than with executable examples. | 2 / 3 |
Workflow Clarity | The steps are sequenced and the severity classification table is helpful, but there are no explicit validation checkpoints or feedback loops. For an incident runbook involving potentially destructive operations like 'reset to full sync from USN 0', there should be validation steps before and after. The workflow lacks clear decision points (e.g., when to escalate from Step 2 to Step 3). | 2 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-organized sections, a single-level reference to the implementation guide for detailed scripts, and external resource links. Content is appropriately split between the runbook overview and the referenced implementation guide. | 3 / 3 |
Total | 9 / 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 | |
- Commit
70e9fa4
- 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.