nv-endpoint-routed-tool-provider

Build or refactor a Tool-channel provider (PagerDuty, Opsgenie, future incident/alerting tools) to be endpoint-routed: per-subscriber secrets stored encrypted on a ChannelConnection behind a typed channel endpoint, a stateless provider that resolves routing from channelData at send time, SKIPPED steps when no endpoint exists, and the full API/worker/dashboard/docs/playground surface. Starts with a mandatory provider-docs discovery gate. Use when refactoring Opsgenie to the PagerDuty model, adding a new tool provider, or touching pagerduty_service channel endpoints.

Quality

96%

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

92%

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

An exceptionally actionable, well-sequenced skill body that respects token budget and gives copy-paste-ready guidance across all five slices. Its only real defect is a missing referenced bundle file (reference.md) that withholds per-file code patterns the reader is told to consult.

Suggestions

Add the referenced reference.md (or remove the two [reference.md](reference.md) links on lines 109 and 114 and inline the per-file code patterns), since progressive disclosure currently points to a file that does not exist.

If keeping reference.md external, list it under references/ so the one-level-deep navigation actually resolves.

Dimension	Reasoning	Score
Conciseness	Information-dense with no padding: it assumes Claude's intelligence (no explaining what PagerDuty or a channel endpoint is) and every token earns its place via exact file paths, regexes, and commands.	3 / 3
Actionability	Fully executable guidance: exact paths like 'packages/shared/src/types/channel-endpoint.ts', a concrete validator regex '/^[a-zA-Z0-9]{32}$/', and copy-paste build and e2e commands.	3 / 3
Workflow Clarity	Clear sequence from the mandatory Step 0 discovery gate (with ask/halt/proceed branches) through a slice-ordered A–E checklist and an explicit Build order & verification block with validation commands.	3 / 3
Progressive Disclosure	The body is well sectioned and signals one-level-deep references to [reference.md](reference.md) for code patterns and page structure, but that referenced file is absent from the bundle, so the promised content is unreachable and navigation is broken.	2 / 3
	Total	11 / 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.

A strong, third-person description that pairs a precise list of concrete capabilities with an explicit, natural-language trigger clause and a distinct niche. It neither pads nor over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: 'Build or refactor a Tool-channel provider', 'per-subscriber secrets stored encrypted on a ChannelConnection', 'a stateless provider that resolves routing from channelData at send time', 'SKIPPED steps when no endpoint exists', and 'the full API/worker/dashboard/docs/playground surface'.	3 / 3
Completeness	Clearly answers both what (endpoint-routed provider with the full surface) and when via an explicit 'Use when' clause with three concrete triggers.	3 / 3
Trigger Term Quality	The explicit 'Use when refactoring Opsgenie to the PagerDuty model, adding a new tool provider, or touching pagerduty_service channel endpoints' covers natural terms a developer on this codebase would actually say.	3 / 3
Distinctiveness Conflict Risk	The endpoint-routed tool-provider / PagerDuty-model niche is specific and its triggers are tied to named artifacts, making it unlikely to fire for the wrong skill.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: novuhq/novu
Path: .cursor/skills/nv-endpoint-routed-tool-provider/SKILL.md
Commit: d921755

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