welcome

Introduce yourself to a newly connected channel. Triggered automatically when a channel is first wired. Send a friendly greeting and brief overview of what you can do.

Quality

67%

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

Fix and improve this skill with Tessl

tessl review fix ./container/skills/welcome/SKILL.md

Quality

Content

70%Weight 40%Scale 1-3

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

The body is well-structured with a clear sequenced onboarding workflow and clean organization, but loses points to pep-talk verbosity and a few vague directives that undercut actionability.

Suggestions

Trim motivational filler ('you got this!', 'time to shine', 'feel like they just unlocked something powerful') and editorial asides to improve conciseness.

Add a concrete example greeting or template and replace vague directives ('just go', 'match the vibe') with specific guidance to raise actionability.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with tight 2-4 sentence capability blocks, but padded with pep-talk filler ('This your time to shine', 'you got this!', 'feel like they just unlocked something powerful') and editorializing that could be trimmed.	2 / 3
Actionability	Concrete guidance exists (an ordered reveal sequence with per-item sentence limits, explicit memory file paths, framed trust/control points), but it is mixed with vague directives like 'just go', 'be intriguing', and 'match the channel vibe' and lacks an example greeting template.	2 / 3
Workflow Clarity	The onboarding flow is clearly sequenced (greeting, name, capability prompt, ordered reveal, trust/control, interaction note, wrap-up) with checklist-like 'always include' sections; no validation loops are needed for this non-destructive conversational flow.	3 / 3
Progressive Disclosure	A single cohesive SKILL.md with clear section headers, no nested references, and appropriately inline content for a conversational onboarding script; no bundle files exist to verify against.	3 / 3
	Total	10 / 12 Passed

Description

65%Weight 40%Scale 1-3

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 complete and distinctive with an explicit auto-trigger, but its specificity is dragged down by second-person voice and somewhat generic actions (greeting + overview).

Suggestions

Rewrite the description in third person (e.g. 'Introduces the agent to a newly connected channel...') to avoid the second-person voice penalty and lift the specificity score.

Add a couple more concrete actions beyond 'greeting and overview' (e.g. 'reveals capabilities one at a time and covers approvals and access control') to improve specificity.

Dimension	Reasoning	Score
Specificity	Base 2 for naming the domain and a couple of actions ('Introduce yourself', 'Send a friendly greeting and brief overview'), but reduced by 1 because the description uses second-person voice ('yourself', 'what you can do') which the rubric penalizes.	1 / 3
Completeness	It clearly answers both what ('Introduce yourself... Send a friendly greeting and brief overview') and when ('Triggered automatically when a channel is first wired'), with explicit trigger guidance equivalent to a 'Use when...' clause.	3 / 3
Trigger Term Quality	Relevant terms like 'newly connected channel', 'greeting', and 'overview' are present, but since the skill is auto-triggered there are no natural user-spoken keywords and common variations are missing.	2 / 3
Distinctiveness Conflict Risk	The trigger is a distinct event ('channel is first wired') tied to a clear niche (channel onboarding), making it unlikely to fire for the wrong skill.	3 / 3
	Total	9 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: nanocoai/nanoclaw
Path: container/skills/welcome/SKILL.md
Commit: 641963c

Reviewed: 6 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.