onboarding

First-time vault setup and onboarding. Guides the user through a multi-phase conversation to collect preferences, life areas, integrations, and creates the full vault structure. Triggers: EN: "initialize the vault", "set up the vault", "onboarding", "vault setup". IT: "inizializza il vault", "configura il vault", "setup del vault". FR: "initialiser le vault", "configurer le vault". ES: "inicializar el vault", "configurar el vault". DE: "Vault initialisieren", "Vault einrichten". PT: "inicializar o vault", "configurar o vault". JA: "Vaultを初期化", "Vaultをセットアップ".

Quality

76%

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 ./tests/regression/snapshot/.claude/skills/onboarding/SKILL.md

Quality

Content

62%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 highly actionable with an exceptionally clear, validated multi-phase workflow, but it is heavily padded with duplicated sections and inlines bulk reference material that should live in separate files. Conciseness and progressive disclosure are the weakest dimensions.

Suggestions

De-duplicate the Email & Calendar Integration and Crew Scoping sections, which each appear twice (Phase 4 and again as standalone sections); keep a single canonical version.

Move the 16 full template definitions and the vault folder-structure tree into a references/ file (e.g. references/templates.md and references/vault-structure.md), keeping SKILL.md as an overview that links to them.

Trim repeated constraint restatements (e.g. the "never jump from Phase 2a to Phase 4" rule appears 3+ times) to a single authoritative statement in the Rules section.

Dimension	Reasoning	Score
Conciseness	The ~1137-line body is noticeably padded: the Email & Calendar integration and Crew Scoping sections are each duplicated verbatim, and the "never jump from Phase 2a to Phase 4" constraint is stated three or more times.	2 / 5
Actionability	Concrete copy-paste Bash (mkdir/cp/ls, the .mcp.json heredoc), exact YAML post-it and user-profile formats, and full template definitions give mostly executable guidance; the commented-out agent-copy lines are a minor gap.	4 / 5
Workflow Clarity	A clearly sequenced multi-phase protocol with a post-it resume feedback loop, an explicit consent gate, and a final verification checklist ("If any item is missing, fix it before declaring onboarding complete") matches the top anchor including for this destructive/batch operation.	5 / 5
Progressive Disclosure	Sections are well-organized with clear headers, but ~400 lines of inlined template definitions and the full vault-structure tree clearly belong in separate reference files; no bundle files are provided, and the runtime .claude/references paths are not skill-bundle references.	3 / 5
	Total	14 / 20 Passed

Description

91%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 strong, third-person description that clearly states both purpose and explicit multi-language triggers. It is highly complete and actionable, with only minor room to sharpen capability specifics and reduce overlap risk from the generic "onboarding" term.

Dimension	Reasoning	Score
Specificity	"Guides the user through a multi-phase conversation to collect preferences, life areas, integrations, and creates the full vault structure" names the domain plus several concrete actions, but stays high-level and omits specifics like templates, MOCs, and crew scoping.	4 / 5
Completeness	Explicitly answers both what ("First-time vault setup and onboarding... creates the full vault structure") and when (a dedicated "Triggers:" block with concrete phrases), satisfying the top anchor.	5 / 5
Trigger Term Quality	Provides comprehensive natural-language triggers with synonyms ("initialize the vault", "set up the vault", "vault setup", "onboarding") repeated across 8 languages, matching the comprehensive-coverage anchor.	5 / 5
Distinctiveness Conflict Risk	The vault-specific triggers ("initialize the vault", "vault setup") carve a clear niche with minimal conflict, but the bare generic term "onboarding" carries minor overlap risk, keeping it just below the top anchor.	4 / 5
	Total	18 / 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
skill_md_line_count	SKILL.md is long (1137 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: gnekt/My-Brain-Is-Full-Crew
Path: tests/regression/snapshot/.claude/skills/onboarding/SKILL.md
Commit: 238ae8c

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