How do I install the Life Setup skill?

Run npx skillmds@latest add jayden-dang/life-setup in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Life Setup skill do?

Use when installing Personal OS into a notes vault or remapping folders — produces a vault config mapping layout roles to the user's paths without forced renames. It is listed under Coding & Dev Tools on SkillMD.

Is Life Setup safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Life Setup?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Life Setup free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Life Setup?

jayden-dang (@jayden-dang) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Life Setup by jayden-dang — Agent Skill

Name: Life Setup
Author: jayden-dang

File contents

Setup Personal OS

User-invoked. Do not auto-start bulk moves.

Role

REQUIRED: read sibling ROLE.md (secretary default, grant rule, hybrid ban, config paths).

Goal

A working config file that maps logical roles → this vault's real folders, plus optional template seeds.

Templates

From package templates/personal-os/. Resolve pack seeds in this order, first path that exists: (1) templates/ beside this SKILL.md, (2) ${CLAUDE_PLUGIN_ROOT}/templates when that variable is set, (3) ../../../templates relative to this SKILL.md. If missing, create minimal stubs — do not invent a second layout system.

Steps

Detect top-level dirs (any PARA/journal/inbox style).
Propose layout: table: role → their path.
Show recommended tree as suggestion only (package README).
One decision: keep names vs adopt recommended.
Write config only after explicit OK.
Create dirs / migrate only with confirmation.
Seed empty registry + optional templates.
Optional roots.* — only paths the user states.
Do not auto-register disk repos as projects.
Re-read the written config: confirm it parses and every layout: role points to a dir that exists.
Name the next skill for the user to run — life-charter if no charter exists, else life-open-project.

Red Flags — Never

Bulk rename without consent
Delete notes
Invent machine-specific paths

Done when

Config parses and every role under layout: maps to a path that exists; registry seeded; life-charter or life-open-project named to the user as the next step.

Frequently asked questions

Life Setup