← ClaudeAtlas

bl-setuplisted

Build the two files every other BylineKit skill reads - voice.md (how the user sounds) and ledger.md (what the user can actually claim). Use when the user first installs BylineKit, says "set up my voice", "my posts don't sound like me", asks where their profile lives, or when any other bl- skill finds the files missing.
ehteshambuildagents/automatedlinkedIn · ★ 1 · Data & Documents · score 72
Install: claude install-skill ehteshambuildagents/automatedlinkedIn
# bl-setup Two files do all the work in this pack. Everything else reads them. | file | what it holds | what breaks without it | | --- | --- | --- | | `~/.claude/bylinekit/voice.md` | how the user writes | every draft sounds like a stranger | | `~/.claude/bylinekit/ledger.md` | what the user can truthfully claim | every draft either fabricates or is empty | Most tools in this space have the first file. The second one is the reason this pack does not make things up. ## Run it in this order ### 1. Create the folder ```bash mkdir -p ~/.claude/bylinekit ``` Copy `templates/voice.md` and `templates/ledger.md` from the repo into it if they are not already there. ### 2. Fill voice.md from evidence, not from questions Ask the user for **three of their own posts** - the three that sound most like them, not the three that performed best. Those are different sets and the difference matters. Read them and write `voice.md` yourself. Infer: - sentence length and how much it varies - whether they use contractions (almost always yes) - their actual vocabulary, including the words they overuse - whether they swear, and how hard - emoji: never, rarely, or freely - how they open and how they close - who they are visibly talking to Then show the user what you inferred and let them correct it. People describe their own writing badly. They recognise it accurately. If they have no posts yet, interview them instead, but say plainly that the voice file will be a guess until there are rea