CtrlK
BlogDocsLog inGet started
Tessl Logo

groq-observability

Set up observability for Groq integrations: latency histograms, token throughput, rate limit gauges, cost tracking, and Prometheus alerts. Use when instrumenting Groq API calls, building a metrics dashboard, or wiring latency/cost/rate-limit alerts. Trigger with phrases like "groq monitoring", "groq metrics", "groq observability", "monitor groq", "groq alerts", "groq dashboard".

72

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

A well-structured, actionable skill body that keeps the overview lean and pushes full code into clearly linked reference files. Minor gains available from de-duplicating the example and adding explicit verification steps.

Suggestions

Remove the duplicated example block from the body or trim it to a one-line pointer to examples.md to tighten conciseness.

Define emitMetrics (or note it lives in implementation.md) in the inline skeleton so the snippet is self-contained.

Add an explicit validation step to the workflow, e.g. 'Confirm Prometheus is scraping groq_latency_ms before relying on alert rules'.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude's competence (no explaining what Prometheus or a histogram is), but the Output section restates metrics already in the table and the inline example duplicates code in examples.md.

4 / 5

Actionability

Provides an executable TypeScript skeleton and a concrete error-handling table, but the inline snippet calls emitMetrics without defining it inline, so it is not fully copy-paste ready without the reference file.

4 / 5

Workflow Clarity

The six steps are explicitly ordered with a clear 1-2 core / 3-6 add-on grouping, but there are no explicit validation checkpoints (e.g., confirm Prometheus is scraping before alerting).

4 / 5

Progressive Disclosure

SKILL.md is a well-organized overview with clearly signaled, one-level-deep references to implementation.md and examples.md, both of which exist and hold the detail split appropriately.

5 / 5

Total

17

/

20

Passed

Description

100%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 high-quality description: third-person voice, concrete capabilities, explicit 'Use when' guidance, and natural trigger phrases scoped tightly to Groq. No vague fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'latency histograms, token throughput, rate limit gauges, cost tracking, and Prometheus alerts' — giving comprehensive coverage of the observability domain rather than vague abstractions.

5 / 5

Completeness

Explicitly answers both 'what' (set up observability with the listed metrics) and 'when' ('Use when instrumenting Groq API calls, building a metrics dashboard, or wiring latency/cost/rate-limit alerts') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Provides natural trigger phrases a user would say ('groq monitoring', 'groq metrics', 'groq observability', 'monitor groq', 'groq alerts', 'groq dashboard') with good synonym coverage.

5 / 5

Distinctiveness Conflict Risk

Clear niche scoped to Groq, with every trigger containing 'groq', so it is unlikely to fire for unrelated skills.

5 / 5

Total

20

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
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.