CtrlK
BlogDocsLog inGet started
Tessl Logo

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/.

66

Quality

80%

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

77%

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 skill body with concrete card payloads, commands, and solid validation checkpoints across all three modes. Its weaknesses are length and monolithic structure — the celebratory prose and bilingual variants inflate the body and could be externalized.

Suggestions

Move the long A.13 closing-moment copy (all three variants × zh/en) into a reference file and keep only a brief pointer plus the tone instruction in SKILL.md to improve conciseness and progressive disclosure.

Consider collapsing the repetitive zh/en request_user_feedback JSON into a shared structure with a language-tagged example, reducing duplicated card blocks throughout sections A and B.

Tighten the inline commentary in A.14/B.8/C.8 notes into terse bullet rules so every remaining token earns its place.

DimensionReasoningScore

Conciseness

Largely efficient and assumes Claude's competence, but the ~579-line body carries content that could be tightened — notably the extended celebratory closing prose in A.13 and inline zh/en card variants at every step — so it lands at 'mostly efficient but could be tightened' rather than lean.

2 / 3

Actionability

Provides fully executable, copy-paste-ready guidance: exact request_user_feedback JSON payloads in both languages, concrete shell commands (ruby install/import scripts, test -d ~/.openclaw, the WSL powershell probe), file paths, and templates.

3 / 3

Workflow Clarity

Three modes are explicitly sequenced (A.1–A.14, B.1–B.8, C.1–C.8) with a clear dispatch order and validation/feedback checkpoints — confirm-and-write loops in B.7 and a double-confirmation plus trash (not rm) for destructive memory deletion in C.6c.

3 / 3

Progressive Disclosure

The two referenced bundle scripts exist and are linked one level deep, but the SKILL.md body is a ~579-line monolith with large blocks (closing-moment prose, full zh/en variants) that could be split into separate reference files, matching 'some structure but content that should be separate is inline'.

2 / 3

Total

10

/

12

Passed

Description

82%

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 strong, specific description that clearly delineates three invocation modes with concrete actions and distinct triggers. Its main gap is the absence of an explicit 'Use when...' clause, which leaves the activation context implicit.

Suggestions

Append an explicit 'Use when...' clause (e.g. 'Use when the user first sets up the assistant, or asks to change the AI personality, user profile, or a memory file.') to raise completeness.

Add a couple of common natural variants like 'set up', 'personalize', or 'tweak my AI' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across three modes — 'runs the full first-run ceremony (AI name, personality, user profile, SOUL.md + USER.md, optional browser + personal website)', 'update just that one profile file', 'update / keep / delete one memory file' — matching the score-3 anchor.

3 / 3

Completeness

It thoroughly answers 'what' for all three modes but never gives an explicit 'Use when...' trigger, so the 'when' is only implied — the rubric caps completeness at 2 for a missing Use-when clause.

2 / 3

Trigger Term Quality

Natural user-facing terms like 'Onboard a new user', 'first-run ceremony', 'personality', 'user profile', and 'memory file' give good coverage of phrases a user would actually say.

3 / 3

Distinctiveness Conflict Risk

It carves a clear niche (assistant first-run onboarding plus profile/memory curation) with distinct dispatch args (scope:soul, scope:user, path:<abs>), making conflict with other skills unlikely.

3 / 3

Total

11

/

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

skill_md_line_count

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

Warning

Total

15

/

16

Passed

Repository
clacky-ai/openclacky
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.