add-channel-whats-next-onboarding

Add a new chat channel's layer-2 dashboard onboarding — the connected-state "What's next" / "FOR YOUR USERS" developer-rollout guide plus its connected details page — in apps/dashboard, following the existing Slack, MS Teams, and Telegram pattern. Use when a connected agent integration needs a per-provider "what's next" guide (recap + dev steps with @novu/react ConnectButton snippet), a <Channel>AgentConnectedDetails view, and the resolver/registry wiring under components/agents/agent-integration-guides.

Quality

81%

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

71%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 body is dense, well-structured, and actionable with a clear sequenced workflow and validation steps, assuming Claude's competence throughout. Its main weakness is the broken reference to a missing reference.md that should hold the full templates.

Suggestions

Add the missing references/reference.md file containing the full Telegram/Slack/MS Teams templates, or inline a minimal copy-paste template so the 'Full templates' pointer resolves.

Replace the manual 'open the detail page and confirm' verification with one or more concrete, repeatable checks (e.g., an exact type-check command or grep assertion) to strengthen the validation checkpoint.

Tighten the Architecture section — the ASCII tree plus the explanatory paragraph restate the same relationships; consider letting the diagram carry most of that load.

Dimension	Reasoning	Score
Conciseness	Lean and assumes Claude's competence (no boilerplate about React/TanStack basics); the architecture diagram and surrounding prose add a little redundancy that could be trimmed, but most tokens earn their place.	4 / 5
Actionability	Provides concrete file paths, exact function signatures, enum/flag names, and field lists, but defers the actual copy-paste templates to reference.md, which is a missing file — a minor gap in executable completeness.	4 / 5
Workflow Clarity	Clear sequence from prerequisites through file checklist to a Build & verify section with validation checkpoints (type-check via Cursor diagnostics, manual UI confirmation, flag-off verification), with only minor gaps in automated feedback.	4 / 5
Progressive Disclosure	Well-organized sections, but the single external reference — 'Full templates: see reference.md' — points to a file that does not exist (no references/ directory), so the deferred content is unreachable and disclosure is incomplete.	3 / 5
	Total	15 / 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 specific, complete, and distinctive, clearly stating both what the skill does and when to use it with concrete trigger phrasing. Its only mild weakness is a reliance on domain-specific jargon over naturally spoken user terms.

Dimension	Reasoning	Score
Specificity	Names the domain and multiple concrete actions — 'Add a new chat channel's layer-2 dashboard onboarding', 'the connected-state What's next / FOR YOUR USERS developer-rollout guide', 'its connected details page', and 'the resolver/registry wiring' — giving comprehensive coverage of the niche.	5 / 5
Completeness	Explicitly answers both what (the onboarding guide, connected details page, and resolver/registry wiring) and when ('Use when a connected agent integration needs a per-provider what's next guide...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good keyword coverage including synonyms and provider names ('What's next', 'FOR YOUR USERS', 'Slack, MS Teams, and Telegram', 'ConnectButton snippet'), though several terms like 'layer-2', 'resolver/registry wiring' are technical jargon rather than natural user phrasing.	4 / 5
Distinctiveness Conflict Risk	A clear niche (layer-2 connected-state onboarding for chat channels in apps/dashboard) with distinct triggers and explicit scoping away from the layer-1 setup guide, minimizing conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: novuhq/novu
Path: .cursor/skills/add-channel-whats-next-onboarding/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.