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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill evernote-prod-checklist85
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 terms and clear when/what guidance. The main weakness is the lack of specific concrete actions - it tells you it's a 'checklist' but doesn't enumerate what the checklist actually covers (e.g., authentication, rate limits, error handling, logging).
Suggestions
Add 2-3 specific checklist items to improve specificity, e.g., 'Covers authentication validation, rate limit configuration, error handling, and logging setup.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Evernote integrations) and mentions 'production readiness checklist' and 'auditing production readiness', but doesn't list specific concrete actions like 'verify API rate limits', 'check authentication tokens', or 'validate error handling'. | 2 / 3 |
Completeness | Clearly answers both what ('Production readiness checklist for Evernote integrations') and when ('Use when preparing to deploy Evernote integration to production, or auditing production readiness') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'evernote production', 'deploy evernote', 'evernote go live', 'production checklist evernote'. These are realistic terms users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining 'Evernote' + 'production readiness' + 'deployment'. Unlikely to conflict with general deployment skills or other integration skills due to the explicit Evernote focus and production checklist context. | 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 solid production readiness checklist with excellent actionability through complete, executable code examples and clear workflow structure. The main weakness is its length - at nearly 400 lines, some detailed implementations (circuit breaker, monitoring setup, logging configuration) could be extracted to separate reference files to improve token efficiency while keeping the main checklist focused.
Suggestions
Extract detailed code implementations (circuit breaker, monitoring metrics, logging configuration) into separate reference files like MONITORING.md and PATTERNS.md, keeping only brief examples in the main checklist
Consolidate the duplicate checklist items - the markdown checkboxes and the code examples often cover the same ground
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy - the checklist items appear both in markdown checkbox format and are then re-explained in code examples. Some sections like the circuit breaker implementation are quite lengthy when a reference to a pattern would suffice. | 2 / 3 |
Actionability | Excellent actionability with fully executable JavaScript code examples, complete configuration templates, and copy-paste ready implementations for error handling, circuit breakers, monitoring, health checks, and deployment verification scripts. | 3 / 3 |
Workflow Clarity | Clear sequential structure with numbered sections, explicit validation through the deployment verification script, and a comprehensive final checklist that serves as a validation checkpoint before go-live. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections, but it's quite monolithic - the detailed code implementations for monitoring, circuit breakers, and logging could be split into separate reference files. The skill does reference external resources and next steps appropriately. | 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.