evernote-prod-checklist
Production readiness checklist for Evernote integrations. Use when preparing to deploy Evernote integration to production, or auditing production readiness. Trigger with phrases like "evernote production", "deploy evernote", "evernote go live", "production checklist evernote".
76
72%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/evernote-pack/skills/evernote-prod-checklist/SKILL.mdQuality
Discovery
79%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description excels at trigger terms, completeness, and distinctiveness due to its narrow Evernote production deployment niche. However, it is weak on specificity—it names no concrete actions or checklist items, making it unclear what the skill actually does beyond being a generic 'checklist'. Adding specific capabilities would significantly improve it.
Suggestions
Add specific concrete actions the checklist covers, e.g., 'Validates OAuth token handling, rate limit configuration, error retry logic, webhook setup, and API endpoint security for Evernote integrations.'
Replace the vague 'checklist' framing with enumerated capabilities so Claude understands the scope of what this skill evaluates or produces.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Production readiness checklist for Evernote integrations' but does not list any concrete actions or capabilities. It doesn't specify what the checklist covers (e.g., authentication checks, rate limit validation, error handling review). 'Checklist' is abstract without enumerating what it checks. | 1 / 3 |
Completeness | The description answers both 'what' (production readiness checklist for Evernote integrations) and 'when' (preparing to deploy, auditing production readiness) with explicit trigger phrases. Both dimensions are clearly addressed. | 3 / 3 |
Trigger Term Quality | The description explicitly lists natural trigger phrases like 'evernote production', 'deploy evernote', 'evernote go live', 'production checklist evernote'. These are realistic phrases a user would say and cover good variations. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of 'Evernote' + 'production readiness' is a very specific niche. It is unlikely to conflict with other skills given the narrow domain of Evernote integration deployment. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid production readiness checklist with highly actionable, specific guidance including concrete configuration values, API method recommendations, and an executable verification script. Its main weaknesses are the lack of explicit sequencing between checklist sections, a referenced implementation guide that doesn't exist in the bundle, and some redundant sections (Output, Examples) that add little value. The error handling table is a strong addition.
Suggestions
Add explicit sequencing guidance (e.g., 'Complete sections in order: Authentication → Security → Rate Limits → Monitoring → Data Integrity → Deployment → Verification') to improve workflow clarity.
Remove or significantly trim the 'Output' and 'Examples' sections, which restate what the checklist already communicates and consume tokens without adding value.
Either provide the referenced 'references/implementation-guide.md' bundle file or remove the reference to avoid a broken link.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with well-structured checklists, but includes some unnecessary sections like the 'Output' section which restates what the checklist already covers, the 'Examples' section which adds little value, and the 'Overview' paragraph that could be trimmed. The checklist items themselves are lean and useful. | 2 / 3 |
Actionability | The skill provides highly concrete, actionable guidance: specific configuration values (EVERNOTE_SANDBOX=false, AES-256-GCM), specific API methods (findNotesMetadata vs findNotes), exact thresholds (100-200ms delays, 5-10 min TTL, 75%/90% quota alerts), and a complete executable verification bash script. The error handling table maps specific errors to specific solutions. | 3 / 3 |
Workflow Clarity | The checklist sections are well-organized by domain, and the verification script provides a clear post-deploy validation sequence. However, there's no explicit ordering or sequencing between the major sections (should security be verified before deployment?), and there's no feedback loop for what to do if checklist items fail beyond the error table. The deployment section mentions a rollback plan but doesn't detail the trigger conditions. | 2 / 3 |
Progressive Disclosure | The skill references an implementation guide at 'references/implementation-guide.md' and an upgrade migration skill, which shows intent for progressive disclosure. However, no bundle files are provided, meaning the referenced file doesn't exist. The main content is also somewhat long (~100 lines of checklist) but the checklist format keeps it scannable, so it's borderline acceptable inline. | 2 / 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
3a2d27d
- 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.