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

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 highly actionable, well-sequenced conversational skill: every step has copy-paste-ready payloads or commands, all three modes are cleanly dispatched, and destructive operations are gated behind confirmations and a dry-run loop. The only notable weaknesses are repeated language-handling rules and a long single file where some verbatim copy could be split out.

DimensionReasoningScore

Conciseness

The body is dense with copy-paste ask_user JSON payloads, exact shell commands, and templates, and never explains concepts Claude already knows. However, the language-handling rules are stated four times (Dispatch intro, A.1, B.1, C.2) and the full bilingual celebration copy is inlined, so it could be tightened.

4 / 5

Actionability

Every step ships executable material: exact card JSON in both languages, exact commands like `ruby "SKILL_DIR/scripts/install_builtin_skills.rb"` and `test -d ~/.openclaw && echo yes || echo no`, and complete SOUL.md/USER.md templates. Nothing is pseudocode or hand-wavy.

5 / 5

Workflow Clarity

All three modes are sequenced in numbered subsections with an explicit dispatch table and jump instructions. Risky operations carry validation checkpoints: import runs dry-run then confirm then --yes, memory deletion requires explicit confirmation and uses the trash tool rather than raw rm, and B.7 confirm-and-write loops back to B.4 on tweak.

5 / 5

Progressive Disclosure

Executable logic is properly pushed into two scripts referenced as SKILL_DIR/scripts/... (both verified to exist), one level deep and clearly signaled. The main file is ~580 lines with sizable inlined verbatim copy (bilingual cards and celebration scripts) that could arguably live in reference files.

4 / 5

Total

18

/

20

Passed

Description

83%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 specific, third-person, well-scoped description that explicitly covers what each invocation mode does and when each applies, anchored to concrete file artifacts. Its only gaps are a few missing natural-language trigger synonyms and the absence of an explicit "Use when..." clause with user-facing trigger phrases.

DimensionReasoningScore

Specificity

It lists multiple concrete actions with concrete artifacts for all three modes: "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/". Coverage of sub-actions is comprehensive with no generic filler.

5 / 5

Completeness

The "what" is explicit per mode, and "when" is explicitly given via argument dispatch ("Without arguments...", "With scope:soul or scope:user...", "With path:<abs>...") plus the opening use-case sentence, so equivalent explicit trigger guidance exists and the cap at 3 does not apply. It falls short of 5 only because there is no "Use when..." phrasing with natural trigger terms.

4 / 5

Trigger Term Quality

Natural terms like "onboard", "first-run", "AI name", "personality", "user profile", and "memory file" are present and would be said by a user needing this skill. Common variations such as "set up", "get started", or "remember/forget" are missing, so coverage is good but not comprehensive.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — this assistant's onboarding and inner-state curation — with distinct triggers anchored to specific artifacts (SOUL.md, USER.md, ~/.clacky/memories/). Minimal overlap risk with any other skill.

5 / 5

Total

18

/

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 (581 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.