gamma-observability

Implement comprehensive observability for Gamma integrations. Use when setting up monitoring, logging, tracing, or building dashboards for Gamma API usage. Trigger with phrases like "gamma monitoring", "gamma logging", "gamma metrics", "gamma observability", "gamma dashboard".

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 complete, executable code and a clear step sequence, but it underuses its bundle: implementation.md is never referenced, content that could be split out is inlined, and the workflow lacks explicit validation checkpoints between steps.

Suggestions

Link references/implementation.md from the body (e.g., 'For Winston logging, OpenTelemetry tracing, and a Grafana dashboard, see [implementation.md](references/implementation.md)') and move duplicated code there to reduce SKILL.md length.

Add explicit validation checkpoints between steps — e.g., after Step 4, 'Verify Prometheus is scraping /metrics/gamma before adding alert rules' — to lift workflow clarity.

Replace bare skill-name mentions ('gamma-sdk-patterns', 'gamma-incident-runbook') with actual links or paths so navigation is unambiguous.

Dimension	Reasoning	Score
Conciseness	The ~250-line body is dense, executable, and assumes Claude's competence without explaining basics, but it inlines full implementations (instrumented client, health check, alert rules) that overlap with references/implementation.md, so it could be tightened by deferring detail to the reference.	2 / 3
Actionability	Every step ships complete, copy-paste-ready TypeScript (createInstrumentedClient, getMetrics, checkGammaHealth) plus concrete Prometheus YAML alert rules and a metrics endpoint — fully executable with no pseudocode.	3 / 3
Workflow Clarity	The five steps are clearly sequenced, but there are no validation checkpoints between them (e.g., confirm metrics are being scraped before authoring alerts), so checkpoints are implicit rather than explicit.	2 / 3
Progressive Disclosure	A references/implementation.md file exists, but the body never links to or signals it; related skills (gamma-sdk-patterns, gamma-incident-runbook) are mentioned in prose without links, and content that belongs in the reference is inlined in SKILL.md.	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 well-constructed: it states concrete actions, gives explicit 'Use when' triggers, lists natural trigger phrases, and is tightly scoped to the Gamma niche. The only minor weakness is the slightly fluffy word 'comprehensive'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across the domain: 'setting up monitoring, logging, tracing' and 'building dashboards for Gamma API usage'. The word 'comprehensive' is mild fluff, but the named actions are specific enough to clear the top anchor.	3 / 3
Completeness	Clearly answers both 'what' (observability for Gamma integrations) and 'when' ('Use when setting up monitoring, logging, tracing, or building dashboards'), with explicit trigger phrases. Both halves are present and explicit.	3 / 3
Trigger Term Quality	Provides explicit natural phrases users would say — 'gamma monitoring', 'gamma logging', 'gamma metrics', 'gamma observability', 'gamma dashboard' — giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Scoped tightly to 'Gamma' with distinct trigger phrases, making it unlikely to fire for unrelated skills. It occupies a clear niche tied to a specific API.	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: 1628598

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.