evernote-observability

Implement observability for Evernote integrations. Use when setting up monitoring, logging, tracing, or alerting for Evernote applications. Trigger with phrases like "evernote monitoring", "evernote logging", "evernote metrics", "evernote observability".

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

72%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Well-organized and concise overview with real executable snippets for metrics, logging, and alerts, plus a correctly signaled single-level reference file. It is held back by incomplete code for the instrumented client and health endpoints and by missing validation checkpoints in the setup workflow.

Suggestions

Add an executable code snippet for Step 2 (the NoteStore Proxy wrapper) and Step 4 (the /health and /ready endpoints) so every step is copy-paste ready, or move them explicitly into the implementation guide with a clear pointer.

Insert a validation checkpoint after instrumentation — e.g., 'curl /metrics and confirm evernote_api_calls_total appears' and 'verify /ready returns 200 against the Evernote API' — before moving to alert setup.

Cross-check Step 5's prose thresholds (error rate > 10%, p95 > 5s, quota > 90%) against the YAML rule shown, which only encodes the rate-limit alert, so the documented alert set matches what is actually provided.

Dimension	Reasoning	Score
Conciseness	The body is lean — short overview, terse step descriptions, and only code that earns its place — without explaining concepts Claude already knows. It is not above level 3, and is not level 2 because there is no padding to tighten.	3 / 3
Actionability	Steps 1 and 3 include executable JavaScript and Step 5 has a real YAML snippet, but Steps 2 (Proxy wrapper) and 4 (health endpoints) and tracing are prose-only with missing implementation details. It is not level 3 because several steps lack copy-paste-ready code.	2 / 3
Workflow Clarity	Steps 1-5 are clearly sequenced, but there are no explicit validation checkpoints (e.g., verify Prometheus is scraping, confirm /ready returns healthy). It is not level 3 because checkpoints are implicit rather than built into the flow.	2 / 3
Progressive Disclosure	The body is an overview that clearly signals a single one-level-deep reference ('see [Implementation Guide](references/implementation-guide.md)'), and that referenced file exists in the bundle. It is not below 3 because navigation is clean and content is appropriately split.	3 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it states concrete capabilities, provides explicit 'Use when' triggers with natural keyword phrases, and is tightly scoped to Evernote observability. Voice is appropriately third-person/imperative with no first- or second-person penalties.

Dimension	Reasoning	Score
Specificity	The description names multiple concrete actions — 'monitoring, logging, tracing, or alerting' — for a defined domain, matching the anchor that lists several specific actions rather than vague language.	3 / 3
Completeness	It explicitly answers both what ('Implement observability for Evernote integrations') and when ('Use when setting up monitoring, logging, tracing, or alerting'), with an explicit trigger clause, so it does not cap at 2.	3 / 3
Trigger Term Quality	It supplies natural phrases a user would say ('evernote monitoring', 'evernote logging', 'evernote metrics', 'evernote observability'), giving good coverage rather than jargon.	3 / 3
Distinctiveness Conflict Risk	The Evernote-specific scope and distinct trigger phrases give it a clear niche unlikely to collide with other skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/evernote-pack/skills/evernote-observability/SKILL.md
Commit: 0540a62

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.