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 encrypted on the channel endpoint resource, 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

81%

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

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

The content is an exceptionally actionable, well-sequenced engineering playbook with strong validation checkpoints and copy-paste verification commands. Its main weakness is progressive disclosure: it repeatedly points to a reference.md that is not present in the bundle.

Suggestions

Add the missing reference.md bundle file under references/ (or scripts/) so the inline links to it resolve, or inline the per-file code patterns the body defers to it.

Consider moving the dense checklist file-path tables into the reference file and keeping SKILL.md as a tighter overview plus the discovery gate and invariants.

If reference.md is intentionally absent, replace the [reference.md](reference.md) links with the actual content or remove them to avoid dead navigation.

Dimension	Reasoning	Score
Conciseness	The body is dense and almost entirely domain-specific facts Claude would not know (invariants, file paths, gotchas) with little padding, though a few checklist lines and the Opsgenie note could be tightened.	4 / 5
Actionability	Highly actionable: concrete file paths, exact index specs, regex validators, copy-paste build/test bash commands, and per-slice checklist items map directly to executable edits.	5 / 5
Workflow Clarity	Clear mandatory discovery gate with explicit halt/ask/proceed checkpoints, a slice-ordered checklist with a stated build-order dependency, and a Build order & verification block with validation commands forming a validate-fix-retry loop.	5 / 5
Progressive Disclosure	The body references [reference.md](reference.md) for per-file code patterns and docs page structure, but no references/ directory or reference.md bundle file exists in the skill, so the signaled one-level-deep reference points to a missing file and structure is effectively inline.	3 / 5
	Total	17 / 20 Passed

Description

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

The description is specific, well-scoped, and explicitly pairs a 'what' with concrete 'use when' triggers around the PagerDuty/Opsgenie endpoint-routed model. It is strong on distinctiveness and completeness, with only minor gaps in trigger synonym coverage and action-concreteness.

Suggestions

Add a few more natural trigger synonyms (e.g. 'incident tool', 'alerting integration', 'per-subscriber secret routing') so users who phrase the need differently still match.

Lead the 'what' with one or two discrete actions (e.g. 'Add per-subscriber channel endpoints, encrypt routing secrets, route sends statelessly') before the architectural characteristics.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions (encrypted per-subscriber secrets, stateless provider resolving routing at send time, SKIPPED steps, full API/worker/dashboard/docs/playground surface) but these are architecture characteristics rather than discrete actions, leaving minor gaps in coverage clarity.	4 / 5
Completeness	Explicitly states both what the skill does ('Build or refactor a Tool-channel provider ... to be endpoint-routed') and when to use it ('Use when refactoring Opsgenie ...'), with the 'when' concrete but slightly narrow to a couple of named scenarios.	4 / 5
Trigger Term Quality	Includes natural trigger phrases users would say ('refactoring Opsgenie', 'adding a new tool provider', 'touching pagerduty_service channel endpoints') with good keyword coverage, though a few common phrasings (e.g. 'incident tool', 'alerting integration') are absent.	4 / 5
Distinctiveness Conflict Risk	The 'endpoint-routed tool provider' / 'PagerDuty model' niche and the specific provider/touch-point references (PagerDuty, Opsgenie, pagerduty_service) make it clearly distinguishable with minimal conflict risk against unrelated skills.	5 / 5
	Total	17 / 20 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: fc9a0fd

Reviewed: 3 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.