CtrlK
BlogDocsLog inGet started
Tessl Logo

notification

Work with the OpenMeter notification package. Use when modifying notification event creation, delivery, reconciliation, rules, channels, webhooks, event payloads, or the Kafka consumer handlers. Trigger this skill whenever the task touches `openmeter/notification/...`, `cmd/notification-service/`, Svix integration, or notification-related tests.

76

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

A high-signal, actionable reference for a complex package with clear sequenced workflows and executable verification commands. Its main weakness is monolithic structure with no progressive disclosure via separate reference files, plus minor repetition of a few facts.

Suggestions

Move the large reference tables (Package Layout, HTTP API operations, Standard Annotations, Key Constants) into separate files under references/ and link to them from concise overview sections to improve progressive disclosure.

De-duplicate facts repeated across sections — e.g. invoice v0→v1 versioning and "events are never deleted" each appear 2–4 times — stating them once in the relevant section and cross-referencing elsewhere.

Tie the Editing Checklist to explicit verification steps, e.g. append 'then run POSTGRES_HOST=127.0.0.1 go test -tags=dynamic -v ./openmeter/notification/...' after each modification block.

DimensionReasoningScore

Conciseness

Dense, repo-specific material Claude would not know (file paths, state machines, dedup-hash inputs, constants) with almost no filler; minor cross-section reinforcement of a few facts (v0→v1 versioning, "events never deleted") is the only slack.

3 / 3

Actionability

Provides copy-paste-ready test commands, real Go struct/interface snippets, concrete constants, and exact file references throughout rather than abstract direction.

3 / 3

Workflow Clarity

The end-to-end event flow, consumer handlers, and reconciliation logic are given as numbered sequences, backed by a per-modification Editing Checklist and an executable Testing section for verification.

3 / 3

Progressive Disclosure

No bundle files exist (references/scripts/assets absent) and all detail lives inline in a ~380-line SKILL.md; content such as the full package layout, API-operations table, and annotations table could be split into separate reference files with signaled navigation.

2 / 3

Total

11

/

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 highly specific, well-triggered description that names concrete capabilities and gives explicit use-conditions with repo-path anchors. It clearly answers what and when with low conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "event creation, delivery, reconciliation, rules, channels, webhooks, event payloads, or the Kafka consumer handlers" — rather than vague language.

3 / 3

Completeness

Explicitly answers both what ("Work with the OpenMeter notification package") and when ("Use when modifying..." and "Trigger this skill whenever the task touches...").

3 / 3

Trigger Term Quality

Covers natural developer-facing terms (notification, webhooks, Svix, rules, channels, Kafka consumer) plus concrete path anchors like `openmeter/notification/...` and `cmd/notification-service/`.

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to the OpenMeter notification package and Svix integration, with path-based triggers that make conflict with other skills unlikely.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
openmeterio/openmeter
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.