apollo-observability

Set up Apollo.io monitoring and observability. Use when implementing logging, metrics, tracing, and alerting for Apollo integrations. Trigger with phrases like "apollo monitoring", "apollo metrics", "apollo observability", "apollo logging", "apollo alerts".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

The body is highly actionable with executable code throughout and a clean step sequence, but it suffers from duplicated inline code that overlaps an unreferenced bundle and lacks explicit verification checkpoints between steps. Strong on actionability, weaker on token efficiency and file-level structure.

Suggestions

Link the existing references/implementation-guide.md from the body (e.g. a '## Full implementation' section) and move the duplicated full code listings there, keeping SKILL.md as a concise overview — this improves both conciseness and progressive disclosure.

Add explicit validation checkpoints between steps, e.g. after wiring interceptors run 'curl localhost:9090/metrics' to confirm counters appear, and validate alert rules with 'amtool check prometheus/apollo-alerts.yml' before deploying.

Defer the extended Grafana dashboard and detailed health-check endpoint to the implementation guide so every inline token earns its place.

Dimension	Reasoning	Score
Conciseness	Prose is lean and free of concept-explanation fluff, but ~150 lines of inline TypeScript/YAML duplicate much of the existing references/implementation-guide.md, so the body could be tightened by deferring to that bundle.	2 / 3
Actionability	Each step ships complete, copy-paste-ready code with concrete file paths (e.g. 'src/observability/metrics.ts'), real prom-client/pino/OpenTelemetry definitions, and a working /metrics endpoint.	3 / 3
Workflow Clarity	Steps 1–6 are clearly sequenced, but no explicit validation checkpoints appear (e.g. confirming metrics scrape or alert rules load), leaving verification implicit.	2 / 3
Progressive Disclosure	Sections are well organized and a one-level reference (references/implementation-guide.md) exists, but the body never links to it and inlines content that belongs in the reference, so navigation is not clearly signaled.	2 / 3
	Total	9 / 12 Passed

Description

100%

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 is concise, specific, and complete: it names concrete observability actions, gives an explicit 'Use when' clause, and lists natural trigger phrases in third-person voice. It hits every anchor at the top of the scale.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'implementing logging, metrics, tracing, and alerting' — under a named Apollo.io domain rather than vague abstractions.	3 / 3
Completeness	Clearly states what it does ('Set up Apollo.io monitoring and observability') and when to use it ('Use when implementing logging, metrics, tracing, and alerting'), with explicit trigger guidance.	3 / 3
Trigger Term Quality	Provides explicit natural trigger phrases users would say: 'apollo monitoring', 'apollo metrics', 'apollo observability', 'apollo logging', 'apollo alerts'.	3 / 3
Distinctiveness Conflict Risk	A distinct Apollo-specific observability niche with 'apollo'-prefixed trigger phrases, making collision with unrelated skills unlikely.	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
Commit: 02d6341

Reviewed: 4 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.