CtrlK
BlogDocsLog inGet started
Tessl Logo

novu-manage-subscribers

Create, update, search, and delete subscribers in Novu. Manage topics for group-based notification targeting. Set subscriber credentials for push and chat channels. Use when managing notification recipients, creating subscriber records, organizing subscribers into topics, or configuring channel-specific credentials.

68

Quality

84%

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

76%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 concise, actionable skill body with good structure and real reference files. The main gap is missing explicit validation for destructive/batch operations, which caps workflow clarity.

Suggestions

Add an explicit verification step before destructive/batch calls (e.g., retrieve and confirm the subscriber exists before delete, and check the bulk-create response for per-record failures) so workflow clarity can exceed the batch/destructive cap of 3.

Fix the copy-paste errors in the credentials examples: correct the "subsriberId-1" typo and replace the APNS block's "fcm-abc-123" integrationIdentifier with an APNS-specific identifier.

Move the exhaustive per-field inline CRUD examples into the reference files, keeping SKILL.md as a tighter overview, to push progressive disclosure toward level 5.

DimensionReasoningScore

Conciseness

The body is lean — mostly copy-paste code with one-line intros and a concise, high-value Common Pitfalls section — assuming Claude's competence with no padding; it is not level 4 because there is essentially no over-explanation to trim.

5 / 5

Actionability

Concrete, executable TypeScript examples cover CRUD, bulk, topics, and credentials, but minor copy-paste errors ("subsriberId-1" placeholder typo, APNS block reusing the FCM "fcm-abc-123" integrationIdentifier) and an empty `topics.list({})` body leave small gaps; it is not level 5 because of these correctness slips and not level 3 because the code is genuinely executable.

4 / 5

Workflow Clarity

Individual operations are unambiguous, but destructive (delete subscriber/topic) and batch (bulk create of up to 500) operations lack explicit validation checkpoints — the rubric caps such skills at 3; it is not level 4 because validation is only implicit via the Common Pitfalls list rather than explicit verify-then-proceed steps.

3 / 5

Progressive Disclosure

Clear section headers and a References section pointing to three real one-level-deep files (subscriber-crud-examples.md, topics-examples.md, credentials-examples.md — all present) give good navigation; it is not level 5 because the full CRUD reference is inlined rather than relying more on the reference files.

4 / 5

Total

16

/

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, third-person description that clearly states capabilities and provides explicit trigger guidance. Minor room for more natural-synonym coverage in the trigger clause.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across the domain — "Create, update, search, and delete subscribers", "Manage topics", "Set subscriber credentials" — giving comprehensive coverage of the skill's surface, matching the level-5 anchor; it is not level 4 because coverage is broad rather than having minor gaps.

5 / 5

Completeness

Explicitly answers both what (CRUD + topics + credentials) and when (a concrete "Use when..." clause with multiple trigger phrases), matching the level-5 anchor exactly; it is not level 4 because the when-guidance is explicit and specific rather than improvable.

5 / 5

Trigger Term Quality

The "Use when" clause surfaces natural phrases ("managing notification recipients", "creating subscriber records", "organizing subscribers into topics", "configuring channel-specific credentials") with good keyword coverage, but a few natural synonyms are missing so it sits just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

The Novu subscriber/topic niche is specific with distinct triggers ("subscribers in Novu", "subscriber credentials") and minimal conflict risk; it is not level 4 because the triggers are clearly bounded to this domain rather than overlapping closely related skills.

5 / 5

Total

19

/

20

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