novu-inbox-integration

Integrate Novu's in-app notification inbox into web applications. Supports React, Next.js, and vanilla JavaScript. Includes the Inbox component (bell icon + notification feed), composable components (Bell, Notifications, InboxContent, Preferences), headless hooks, branded theming, custom render props, multi-tenancy via contexts, tabs, localization, and HMAC security. Use when adding an in-app notification center, bell icon, notification feed, real-time notification updates, or building a personalized and branded notification experience.

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.

A well-structured, highly actionable reference with copy-paste code and good progressive disclosure. Minor conciseness redundancy and slightly implicit validation checkpoints are the only weak spots.

Suggestions

Deduplicate the HMAC contextHash example (it appears in both Multi-Tenancy and HMAC Authentication) by referencing one from the other.

Add an explicit 'verify the notification appears' or validation checkpoint after the multi-tenancy and HMAC setup steps to strengthen workflow clarity.

Tighten the inline severity-vs-critical explanation by deferring more of it to the referenced severity doc.

Dimension	Reasoning	Score
Conciseness	Dense and code-heavy with almost no conceptual padding, but minor redundancy (HMAC shown in both Multi-Tenancy and HMAC sections; severity/critical distinction explained inline and referenced) keeps it just short of fully lean.	4 / 5
Actionability	Copy-paste-ready executable code across React, Next.js (App + Pages Router), composable components, branding, render props, tabs, multi-tenancy, localization, and HMAC (TypeScript + Python), covering the common cases thoroughly.	5 / 5
Workflow Clarity	Multi-step flows (e.g. multi-tenancy: trigger → pass context → secure with contextHash) are numbered and 'Common Pitfalls' acts as a checklist, but explicit validate-then-proceed feedback loops are largely implicit rather than called out.	4 / 5
Progressive Disclosure	Clear overview body with well-signaled, one-level-deep references — each major section links to a real file in ./references/ and a consolidated References list closes the document; bulk detail is appropriately offloaded to those files.	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.

A strong, specific description that names concrete capabilities and provides an explicit 'Use when' trigger clause. Trigger-term coverage is good but could add a few more natural synonyms.

Suggestions

Add a couple of natural synonyms (e.g. 'notifications', 'inbox widget') to the 'Use when' clause to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'Inbox component (bell icon + notification feed)', 'composable components (Bell, Notifications, InboxContent, Preferences)', 'headless hooks', 'branded theming', 'custom render props', 'multi-tenancy via contexts', 'tabs, localization, and HMAC security' — giving comprehensive coverage.	5 / 5
Completeness	Clearly states what it does (integrate Novu's inbox; enumerates features) and gives an explicit 'Use when...' clause with concrete trigger phrases, satisfying both what and when.	5 / 5
Trigger Term Quality	Natural trigger phrases are present ('in-app notification center, bell icon, notification feed, real-time notification updates, personalized and branded notification experience'), but a few common synonyms (e.g. 'notifications', 'inbox') and framework-specific phrasings are under-covered.	4 / 5
Distinctiveness Conflict Risk	A clear niche — Novu's in-app notification inbox — with specific, distinctive triggers; minimal risk of firing for unrelated skills.	5 / 5
	Total	19 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (618 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	13 / 16 Passed

Repository: novuhq/novu
Path: docs/.mintlify/skills/inbox-integration/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.