CtrlK
BlogDocsLog inGet started
Tessl Logo

add-channel-connect-button

Build a new channel Connect button (e.g. WhatsApp, Discord, LINE) in @novu/js and @novu/react following the existing SlackConnectButton, MsTeamsConnectButton, and TelegramConnectButton pattern. Use when adding connect/disconnect UI for a new chat channel/provider to the SDK — covering the SolidJS core component, the React wrapper, the channelConnections (OAuth) vs channelEndpoints (deep-link) data layer, the component registry, and package exports.

76

Quality

96%

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

92%

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

The body is lean, highly actionable, and clearly sequenced with validation checkpoints. Its only real weakness is progressive disclosure: it points to a reference.md that is absent from the bundle, leaving the 'Full templates' link broken.

Suggestions

Create references/reference.md (or move the reference to the correct bundle path) so the 'Full templates' link resolves and the SKILL.md can offload the heavier template detail.

Consider moving the Button behavior contract and/or Conventions sections into reference.md to slim the SKILL.md overview, keeping only the decision table and file checklist inline.

If reference.md is intentionally omitted for now, remove or qualify the link (e.g. '(optional)') so Claude does not rely on a file that is not present.

DimensionReasoningScore

Conciseness

Lean and token-dense with no beginner-concept padding — it assumes Claude knows SolidJS/React/OAuth and uses tables, checklists, and terse bullets where every line carries actionable detail.

3 / 3

Actionability

Concrete file paths, exact SDK calls ("generateConnectOAuthUrl()", "list({ providerId, integrationIdentifier, limit: 1 })"), explicit prop lists, timing constants ("2500ms", "120_000ms"), and a copy-ready file checklist make this fully executable.

3 / 3

Workflow Clarity

Clearly sequenced — Step 0 decision table first, then file checklist, behavior contract, conventions, and a "Build & verify" section with explicit checkpoints ("pnpm build" required, type-check/lint, manual test) and a checklist for the complex process.

3 / 3

Progressive Disclosure

Sections are well-organized and the templates reference is clearly signaled one level deep ("Full templates: see reference.md"), but reference.md does not exist in references/scripts/assets, so the promised detail is unreachable and a fair amount of contract material stays inline.

2 / 3

Total

11

/

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.

The description is specific, trigger-rich, and complete with an explicit 'Use when' clause and third-person/imperative voice. It carves out a distinct niche anchored to existing reference implementations, with no over-claims or padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions/components — "covering the SolidJS core component, the React wrapper, the channelConnections (OAuth) vs channelEndpoints (deep-link) data layer, the component registry, and package exports" — rather than vague language, matching the score-3 anchor.

3 / 3

Completeness

Explicitly answers both what ("Build a new channel Connect button ... covering [layers]") and when ("Use when adding connect/disconnect UI for a new chat channel/provider to the SDK"), with an explicit 'Use when' clause present.

3 / 3

Trigger Term Quality

Natural terms a user would say are well covered — "channel Connect button", "connect/disconnect UI", "new chat channel/provider", plus named channels "WhatsApp, Discord, LINE"; the SDK jargon is additional, not a substitute for natural triggers.

3 / 3

Distinctiveness Conflict Risk

Clear narrow niche (adding a provider connect button in the Novu SDK) anchored to existing siblings "SlackConnectButton, MsTeamsConnectButton, and TelegramConnectButton", making it unlikely to trigger for an unrelated skill.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

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.