CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

onboard

Onboard a new user OR curate a single piece of the assistant's inner state. Without arguments, runs the full first-run ceremony (AI name, personality, user profile, SOUL.md + USER.md, optional browser + personal website). With `scope:soul` or `scope:user`, runs a quick chat to update just that one profile file. With `path:<abs>`, runs a quick chat to update / keep / delete one memory file under ~/.clacky/memories/.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./lib/clacky/default_skills/onboard/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a highly actionable, well-sequenced interactive skill: every step has copy-paste cards, commands, or templates in both languages, and destructive operations are guarded by confirmations and safe tooling. Its weaknesses are token weight — everything inlined in one large bilingual file with some duplicated guidance — and missing error-recovery handling around the external script invocations.

Suggestions

Split each mode's full content (especially the bilingual SOUL/USER templates and the A.13 closing monologue variants) into one-level-deep reference files, keeping SKILL.md as a dispatch overview with per-mode quick summaries.

Add validation/error handling for the A.9 and A.10 ruby script invocations (what to do on non-zero exit or unparseable last stdout line) to close the workflow-clarity gap.

Deduplicate the personality descriptions (A.4 options vs the A.7 style-guide table) and consolidate the language-detection rules stated in Dispatch, A.1, B.1, and C.2.

DimensionReasoningScore

Conciseness

The body is dense with operational content — exact JSON cards, commands, and templates — and assumes Claude's competence rather than explaining concepts, but the personality style table in A.7 repeats the option descriptions from A.4, language-handling rules are restated across sections, and the six full celebration monologue variants in A.13 could be trimmed, matching the score-4 anchor of minor instances that could be cut.

4 / 5

Actionability

Guidance is fully executable throughout: copy-paste ask_user JSON payloads in both languages, exact shell commands (e.g., `ruby "SKILL_DIR/scripts/install_builtin_skills.rb"`, the WSL powershell home-detection one-liner, `test -d ~/.openclaw && echo yes || echo no`), complete SOUL.md/USER.md templates, and explicit branch logic — matching the score-5 anchor with common cases covered.

5 / 5

Workflow Clarity

The three modes are dispatched by an explicit parse-first rule and each is a clearly numbered sequence (A.1–A.14, B.1–B.8, C.1–C.8) with real checkpoints: confirm/tweak/cancel loop before writes (B.7), double-confirmation before deletion with `trash` instead of `rm` (C.6c), and silent skip of unreachable links (A.6). Minor gaps — no error handling if the A.9/A.10 ruby scripts fail or emit unparseable output — place it at the score-4 anchor rather than 5.

4 / 5

Progressive Disclosure

Section structure is clear (mode table, dispatch, lettered modes with numbered subsections) and the two scripts are correctly externalized and referenced, but the single ~570-line file inlines everything else — full bilingual template sets, all card JSON variants, and per-mode flows that could each live in one-level-deep reference files — matching the score-3 anchor of content that should be separate left inline.

3 / 5

Total

16

/

20

Passed

Description

67%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, third-person, and comprehensively covers all three invocation modes with concrete actions and distinct file-path anchors. Its main weaknesses are the absence of a "Use when..." trigger clause and reliance on invocation-argument syntax rather than natural user phrases, though the skill is explicitly user-invocable only, which limits the practical impact of trigger-term gaps.

Suggestions

Add a 'Use when...' clause (e.g., 'Use when the user wants to personalize the assistant, update their profile, or review a stored memory') to explicitly state invocation triggers and lift completeness.

Include natural user phrasings such as 'personalize', 'set up your assistant', 'change personality', or 'update my profile' alongside the scope:/path: argument syntax.

Consider mentioning the user-facing slash-command form (/onboard) so the description aligns with how users actually invoke it.

DimensionReasoningScore

Specificity

"runs the full first-run ceremony (AI name, personality, user profile, SOUL.md + USER.md, optional browser + personal website)" and "update / keep / delete one memory file under ~/.clacky/memories/" enumerate multiple concrete actions with comprehensive coverage of all three modes, matching the score-5 anchor.

5 / 5

Completeness

The "what" is clearly and explicitly described for all three modes, but there is no "Use when..." clause or equivalent explicit trigger guidance for when to invoke the skill; the argument-dispatch sentences describe mode selection, not usage triggers, so per the guidelines completeness is capped at 3.

3 / 5

Trigger Term Quality

Keywords present ("onboard", "first-run", "profile", "memory file") are relevant, but most terms are invocation syntax ("scope:soul", "scope:user", "path:<abs>") rather than natural phrases a user would say, and common variations like "personalize", "set up", or "change your personality" are missing — fitting the score-3 anchor of some relevant keywords missing common variations.

3 / 5

Distinctiveness Conflict Risk

Onboarding/first-run setup with unique artifacts (SOUL.md, USER.md, ~/.clacky/memories/, browser-setup, personal website) occupies a clear niche with minimal overlap with other skills, matching the score-5 anchor.

5 / 5

Total

16

/

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (579 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

clacky-ai/openclacky

Path

lib/clacky/default_skills/onboard/SKILL.md

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.