evernote-ci-integration
Configure CI/CD pipelines for Evernote integrations. Use when setting up automated testing, continuous integration, or deployment pipelines for Evernote projects. Trigger with phrases like "evernote ci", "evernote github actions", "evernote pipeline", "automate evernote tests".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill evernote-ci-integration84
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 skill description with excellent completeness and distinctiveness. It clearly defines its niche (Evernote CI/CD) and provides explicit trigger terms. The main weakness is that the capabilities could be more specific about what concrete actions the skill performs beyond the general category of 'configuring pipelines'.
Suggestions
Add specific concrete actions like 'create GitHub Actions workflows', 'configure test runners', 'set up deployment scripts' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (CI/CD pipelines for Evernote) and mentions actions like 'automated testing, continuous integration, deployment pipelines' but lacks specific concrete actions like 'create workflow files', 'configure test runners', or 'set up deployment triggers'. | 2 / 3 |
Completeness | Clearly answers both what ('Configure CI/CD pipelines for Evernote integrations') and when ('Use when setting up automated testing, continuous integration, or deployment pipelines') with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'evernote ci', 'evernote github actions', 'evernote pipeline', 'automate evernote tests'. These are realistic terms combining the domain (Evernote) with CI/CD concepts. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of 'Evernote' + 'CI/CD' creates a very specific niche. The explicit trigger terms like 'evernote github actions' and 'evernote pipeline' make it highly unlikely to conflict with generic CI/CD skills or other Evernote 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 highly actionable skill with excellent workflow clarity and complete, executable code examples for CI/CD setup. However, it suffers from being overly long with extensive inline code that could be better organized through progressive disclosure into separate reference files. The content is practical and immediately usable but could be more token-efficient.
Suggestions
Extract the mock Evernote client implementation to a separate MOCKS.md file and reference it from the main skill
Move the full test examples to a separate TESTS.md file, keeping only a minimal representative example inline
Condense the GitHub Actions workflow by showing a minimal working example inline and linking to a complete version
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary verbosity, such as the full mock implementation details and extensive test examples that could be condensed or referenced externally. The workflow YAML is complete but lengthy. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code including complete GitHub Actions workflow, Jest configuration, mock implementations, and test examples. All code is concrete and immediately usable. | 3 / 3 |
Workflow Clarity | Clear step-by-step progression from workflow setup through test configuration, mocking, unit tests, integration tests, secrets management, and scripts. Each step builds logically on the previous, with explicit validation through test execution. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is monolithic with ~400 lines of inline code that could be split into separate reference files. The mock implementation and full test examples would benefit from being in separate files with links. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (570 lines); consider splitting into references/ and linking | Warning |
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 | 8 / 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.