linkedin-setuplisted

# Setup > **Paths in this file are relative to the bundle root**, the directory holding > the router `SKILL.md`, not to this skill's own directory. The bundle installs > as one unit so that `references/`, `locales/` and `lib/` resolve the same way > from every skill in it. This is the entry point, and for anyone who did not write this engine it is the actual product. Without it, a published bundle is a folder of prompts. It takes about twenty minutes and it ends on a written post, not on a file. ## What it produces **One file, written out in this conversation for the person to save.** Not a directory, and not a file this skill creates: the floor writes nothing to disk. What comes out is text on screen, with a name suggested for it, and the person keeps it wherever they keep things. Its format is `references/material.md`, and it has six sections: Status, Profile, Voice, Pillars, Ideas, and a Ledger that starts empty. **Their published posts stay outside it.** They are pasted into this conversation at step 4, read once for the Voice section, and stay wherever the person already keeps them. A hundred post bodies inside an attached file is the one thing that does not scale. A tier that can write files may offer to save it. That is a convenience, and it never changes what this skill promises. ## Step 0. The language **Do not ask for a path, and do not assume one.** There is no directory to choose. A tier holding a filesystem may suggest where to put the file once it exis