CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

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 dense, highly actionable integration guide with verified one-level-deep references and copy-paste-ready code. Its main weaknesses are repeated prop boilerplate across examples plus a Common Pitfalls section that duplicates earlier guidance, and workflows lacking explicit validation checkpoints.

Suggestions

Collapse the repeated applicationIdentifier/subscriberId/subscriberHash props into a single 'common props' note and use /* ... */ in subsequent examples to cut boilerplate without losing copy-paste value.

Trim the Common Pitfalls list to only items not already stated inline (e.g. drop the 'use client', 'variables override baseTheme', and 'don't store secrets in data' entries that are covered in their own sections), or convert it into a cross-referenced checklist.

For the Multi-Tenancy and HTML-rendering workflows, add an explicit verify step (e.g. confirm the context match table / confirm sanitization is disabled) so the sequence earns a validation checkpoint.

DimensionReasoningScore

Conciseness

Content is largely lean and avoids explaining concepts Claude knows, but the applicationIdentifier/subscriberId/subscriberHash boilerplate is repeated across ~10 examples and the 12-item 'Common Pitfalls' section largely restates guidance already given in the body; could be tightened. Not a 3 because of this verifiable redundancy, not a 1 because there is no conceptual fluff.

2 / 3

Actionability

Provides fully executable, copy-paste-ready TSX/TS/Python/bash (e.g. the React Quick Start install + import + Inbox render, and the createHmac server-side hash) — matching the score-3 anchor of complete, specific examples.

3 / 3

Workflow Clarity

Sequences are present (Multi-Tenancy steps 1-3 with a contextHash security step; HTML rendering steps 1-2) but there are no explicit validation checkpoints or fix→retry feedback loops, fitting the score-2 anchor of 'steps listed but checkpoints missing or implicit.' Not a 3 because no validation/feedback loop is written; not a 1 because the multi-step sequences are clearly ordered.

2 / 3

Progressive Disclosure

SKILL.md acts as an overview with well-signaled, one-level-deep references (e.g. 'See [Branding & Styling Reference](./references/branding-and-styling.md)') and a References section; all seven referenced files exist in ./references/, confirming content is appropriately split rather than monolithic.

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 names many concrete capabilities and pairs them with an explicit 'Use when...' trigger clause using natural terms. It is specific, complete, and clearly distinct to Novu's Inbox product.

DimensionReasoningScore

Specificity

Lists multiple specific 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' — matching the score-3 anchor of enumerating several concrete actions.

3 / 3

Completeness

Explicitly answers both what (integration capabilities above) and when via a dedicated 'Use when...' clause, so it is not capped at 2 for a missing trigger clause.

3 / 3

Trigger Term Quality

'Use when adding an in-app notification center, bell icon, notification feed, real-time notification updates, or building a personalized and branded notification experience' covers natural terms a user would actually say; not merely a 2 because it gives good variation rather than a single keyword.

3 / 3

Distinctiveness Conflict Risk

Scoped to 'Novu's in-app notification inbox' with Novu/product-specific triggers, giving it a clear niche unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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