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

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

77%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 highly actionable and clearly sequenced with validation checkpoints, but it is verbose and monolithic: rules are repeated multiple times, Phase 4 content is duplicated in later sections, and large template blocks are inlined rather than offloaded to bundle files.

Suggestions

Move the inlined template definitions (~430 lines) into a references/templates.md bundle file and keep only a pointer in SKILL.md, since the body already references that path.

De-duplicate the "NEVER jump from Phase 2a to Phase 4" rule (currently stated three times) and consolidate the Phase 4 creation steps with the later "Crew Scoping" and "Email & Calendar Integration" sections to remove repeated content.

Trim the motivational "Foundational Principle: The Human Never Touches the Vault" and "Golden Rule" prose to the concrete behavioral rules they imply, reducing token load.

Dimension	Reasoning	Score
Conciseness	Mostly actionable but padded: the "NEVER jump from Phase 2a to Phase 4" rule is stated three times, Phase 4 creation steps are duplicated in later "Crew Scoping" and "Email & Calendar Integration" sections, and the motivational "Foundational Principle"/"Golden Rule" prose could be tightened without losing guidance.	2 / 3
Actionability	Provides copy-paste-ready artifacts throughout — exact post-it and user-profile formats, complete Templater template definitions, and concrete bash (mkdir/cp/ls/cat heredoc for .mcp.json), fully executable rather than pseudocode.	3 / 3
Workflow Clarity	Multi-step onboarding is explicitly sequenced (Phases 1→2→2a→2b→2c→3→4) with an ordered checklist, a post-it resume mechanism, a consent stop-gate, and a final verification checklist with a validate-then-fix loop ("If any item is missing, fix it before declaring onboarding complete").	3 / 3
Progressive Disclosure	The skill is a single ~1160-line file; no bundle/reference files ship with it, and ~430 lines of template definitions are inlined even though a separate ".platform/references/templates.md" is referenced — content that should be split out is inline, matching the mid anchor.	2 / 3
	Total	10 / 12 Passed

Description

100%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 strong: third-person voice, concrete actions, explicit multi-language triggers, and a distinct niche with low conflict risk. It cleanly answers both what the skill does and when to use it.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "collect preferences, life areas, integrations, and creates the full vault structure" — which matches the anchor for listing several specific concrete actions rather than naming only a domain.	3 / 3
Completeness	Explicitly answers both what ("Guides the user through a multi-phase conversation... and creates the full vault structure") and when ("Triggers:") with explicit trigger guidance, satisfying the top anchor.	3 / 3
Trigger Term Quality	Provides extensive natural trigger phrases users would say ("initialize the vault", "set up the vault", "onboarding", "vault setup") across seven languages, giving good coverage of natural terms.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (first-time vault setup/onboarding for the crew) with vault-specific triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 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 (1161 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

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

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