linkedin-postlisted

# Write a post > **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. The bottleneck is not writing, it is extraction. This skill interviews first and writes second. **It never invents material.** ## Before anything 1. Read the material's `## Status` block. If `filled: no`, say so in one line and offer `linkedin-setup`. Do not proceed by guessing who this person is. 2. Read its Profile, Voice, Pillars and Ideas sections. 3. Read `locales/<interview_language>/style.md` and `interview.md`. If the pack does not exist, fall back to `locales/en`, and say so. 4. Count the pillars of the last eight ledger rows with `state: published`, drafts do not count. Announce the balance in one line and name the pillar that is behind. 5. Find ledger rows published more than seven days ago whose three numbers are still empty. Ask for them. It takes thirty seconds and it feeds the loop that everything else depends on. Then offer three ways in: a free subject, a voice note, or an idea from the Ideas section, prioritising the pillar that is behind. For a voice note, transcribe locally. Nothing about this leaves the machine. ## The interview Intents and ladder: `references/interview-intents.md`, set B. Wording: `locales/<interview_language>/interview.md`. **One ques