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

83%

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

71%Weight 40%Scale 1-5

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

Highly actionable, executable observability guidance with a clear step sequence. The main weaknesses are an orphaned references/implementation.md bundle file that the body never points to, and inlined content that duplicates it — both progressive-disclosure and conciseness issues.

Suggestions

Link references/implementation.md from the body (e.g., a '## Advanced setup' section pointing to it for the prom-client, Winston, OpenTelemetry, and Grafana-dashboard variants) so the bundle file is not orphaned.

Move the bulk of the hand-rolled Prometheus text-format endpoint and full alerting YAML into the reference file, keeping only a concise representative example inline to reduce duplication and body length.

Add an explicit validation checkpoint after Step 4/5 (e.g., 'Verify metrics appear at /metrics/gamma and that a test alert fires') so the workflow has a confirmation step before relying on observability.

Dimension	Reasoning	Score
Conciseness	Mostly code-driven and free of basic-concept padding, but the ~250-line body inlines full implementations (notably a hand-rolled Prometheus text endpoint and alerting YAML) that duplicate richer versions already in references/implementation.md, so it could be tightened by offloading that detail.	3 / 5
Actionability	Provides copy-paste-ready, executable TypeScript for the instrumented client, structured logger, health check, and metrics endpoint, plus concrete Prometheus alerting YAML covering the common cases.	5 / 5
Workflow Clarity	Steps are clearly sequenced (Step 1 instrumented client through Step 5 alerting) with a helpful error-handling/troubleshooting table, but there is no explicit 'verify metrics are being scraped / alert fires' checkpoint before relying on the setup.	4 / 5
Progressive Disclosure	The body is sectioned into steps and tables, but references/implementation.md (containing the prom-client, Winston, OpenTelemetry, and Grafana-dashboard variants) is never linked from the body, so a provided bundle file is orphaned and content that belongs in it is inlined rather than signaled.	3 / 5
	Total	15 / 20 Passed

Description

95%Weight 40%Scale 1-5

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: third-person voice, explicit what/when, and concrete natural trigger phrases scoped to a distinct Gamma niche. Only minor weakness is the slight buzzword quality of 'comprehensive observability' and actions not enumerated at a finer grain.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ('monitoring, logging, tracing, or building dashboards for Gamma API usage'), but the lead phrase 'comprehensive observability' is mildly buzzwordy and the actions are not broken into finer-grained sub-actions, leaving minor coverage gaps.	4 / 5
Completeness	Clearly answers 'what' (implement observability: monitoring, logging, tracing, dashboards) and 'when' (an explicit 'Use when...' clause plus concrete trigger phrases), satisfying the top anchor.	5 / 5
Trigger Term Quality	Explicit natural trigger phrases are listed ('gamma monitoring', 'gamma logging', 'gamma metrics', 'gamma observability', 'gamma dashboard') — varied synonyms a user would actually say, covering the domain comprehensively.	5 / 5
Distinctiveness Conflict Risk	The 'Gamma' qualifier and gamma-prefixed trigger phrases carve out a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 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/gamma-pack/skills/gamma-observability/SKILL.md
Commit: 0540a62

Reviewed: about 17 hours 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.