CtrlK
BlogDocsLog inGet started
Tessl Logo

novu-manage-preferences

Configure notification preferences in Novu at the workflow and subscriber level. Set default channel preferences (email, SMS, push, chat, in-app), mark preferences as read-only or subscriber-editable, and manage subscriber-specific overrides. Use when setting up notification opt-in/opt-out, configuring per-channel delivery preferences, or building a preferences management UI.

69

Quality

86%

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

72%

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

A well-organized, highly actionable reference skill with strong progressive disclosure and real bundle files. Its main weaknesses are minor code repetition in Common Patterns and the absence of explicit verification steps after preference mutations.

Suggestions

Remove or condense the 'Critical Alerts' and 'Marketing' snippets in Common Patterns since the same configurations already appear in the Read-Only and Optional sections, keeping only genuinely new patterns like 'In-App Only by Default'.

Add an explicit verification step after subscriber preference updates (e.g., re-call `novu.subscribers.preferences.list` to confirm the override took effect) to give the workflow a validation checkpoint.

Consider noting the read-only vs. critical distinction once and linking out sooner, to reduce the cross-reference overhead between the in-body table and the external severity-and-critical reference.

DimensionReasoningScore

Conciseness

The body is code/table-dense and avoids explaining concepts Claude already knows, but the 'Common Patterns' section re-presents the critical-alert (`readOnly: true`) and marketing snippets already shown earlier, so it could be tightened to earn the 'every token earns its place' bar.

2 / 3

Actionability

Provides complete, executable TypeScript/TSX examples with imports, concrete API calls, and copy-paste-ready preference objects rather than pseudocode or abstract direction.

3 / 3

Workflow Clarity

The Preference Resolution Order is a clearly sequenced 1–4 model and the Pitfalls section acts as a checklist, but there are no explicit validation/verification checkpoints after mutating API calls (e.g., re-listing to confirm an override applied).

2 / 3

Progressive Disclosure

Clear overview structure with a well-signaled, one-level-deep References section whose three linked files all exist, and deeper detail is appropriately offloaded to the framework-integration skill and an external severity-and-critical reference.

3 / 3

Total

10

/

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 concrete capability statements with an explicit 'Use when' trigger and distinct, domain-specific keywords. It answers both what and when without verbosity or over-claiming.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Configure notification preferences', 'Set default channel preferences (email, SMS, push, chat, in-app)', 'mark preferences as read-only or subscriber-editable', 'manage subscriber-specific overrides' — matching the 'lists multiple specific concrete actions' anchor rather than merely naming a domain.

3 / 3

Completeness

Clearly states what it does ('Configure notification preferences in Novu at the workflow and subscriber level…') and when to use it via an explicit 'Use when…' clause, satisfying both halves of the anchor.

3 / 3

Trigger Term Quality

Natural user-facing terms like 'notification opt-in/opt-out', 'per-channel delivery preferences', and 'preferences management UI' give good coverage of phrasings a user would actually say, beyond technical jargon.

3 / 3

Distinctiveness Conflict Risk

Scoped to a clear Novu notification-preferences niche with distinct triggers, making it unlikely to fire for unrelated skills; not generic enough to conflict broadly.

3 / 3

Total

12

/

12

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 2 suspicious

Warning

Total

14

/

16

Passed

Repository
novuhq/novu
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.