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.

Quality

89%

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

86%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 well-structured and highly actionable, with executable code throughout and a clean split between the overview and supporting reference files. The only notable gap is the absence of validation/error-handling checkpoints around the subscriber update calls.

Suggestions

Add a brief verification step after subscriber preference updates (e.g., re-list preferences or check the API response) so the workflow includes an explicit feedback loop.

Trim the Channel Types table, since the same channel keys are already demonstrated in the preceding code block, to improve token efficiency.

Consolidate the Common Patterns section by referencing the example files instead of re-listing preference snippets already shown in the main body.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, code-first, and assumes Claude's competence, but the Channel Types table and the Common Patterns section partly restate values already shown in the preceding code blocks, adding minor redundancy that could be trimmed.	4 / 5
Actionability	Multiple copy-paste-ready TypeScript snippets cover the common cases end to end — workflow defaults, read-only/optional preferences, subscriber list/update, global updates, and the React UI components — with concrete identifiers and parameters.	5 / 5
Workflow Clarity	The Preference Resolution Order is a clear numbered sequence and Common Pitfalls act as a checklist, but the update flows lack any verification or error-handling checkpoint, so it stops short of the explicit validation feedback loops that define a 5.	4 / 5
Progressive Disclosure	The body functions as an overview and points to three real one-level-deep reference files (workflow-preferences-examples.md, subscriber-preferences-examples.md, preferences-ui-examples.md), all of which exist, are clearly signaled in a References section, and keep detail out of the main file.	5 / 5
	Total	18 / 20 Passed

Description

92%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 strong: it states concrete capabilities at both the workflow and subscriber level and provides explicit 'Use when' triggers tied to real user scenarios. It is specific, complete, and clearly distinct from other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across both levels — 'Set default channel preferences (email, SMS, push, chat, in-app), mark preferences as read-only or subscriber-editable, and manage subscriber-specific overrides' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (configure notification preferences at workflow and subscriber level) and 'when' via a concrete 'Use when setting up notification opt-in/opt-out, configuring per-channel delivery preferences, or building a preferences management UI' trigger clause.	5 / 5
Trigger Term Quality	Includes natural trigger phrases like 'notification opt-in/opt-out', 'per-channel delivery preferences', and 'preferences management UI', but misses some common variations users might say; not a 5 because coverage of synonyms is good rather than comprehensive.	4 / 5
Distinctiveness Conflict Risk	A clearly bounded Novu-specific niche with distinct, domain-specific triggers that make it unlikely to fire for unrelated skills.	5 / 5
	Total	19 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
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
Path: docs/.mintlify/skills/manage-preferences/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.