Build log
Tell Borker what you are working on, day to day, straight from your coding agent.
The build log lets you tell Borker what you are working on, day to day. A skill for your coding agent reads your sessions, cleans them up and pulls out the entries worth sharing. You keep the ones you want, and Borker turns them into posts.
Set it up
- Create an agent key with write access in Borker under Settings, Keys.
- Paste one line into Claude Code:
Install the Borker build log skill from borker.xyz/skills/build-log - Run
/borker-build-login any session.
The skill asks for your key on its first run. The skill page has the current version. Install the skill manually: 1. Download the skill. 2. Tell your agent to install it from the zip.
What leaves your machine
Keys, emails, wallets and pasted blocks are removed by code before anything is read. The agent writes entries that name no client, person or employer unless you asked. The review page marks every name left in an entry and one click takes it out. Only the entries you keep are sent.
On the Sources tab
Your entries arrive in the Build log on the Sources tab, in the order they happened, not yet planned. Borker plans each new entry in its night run, oldest first, on the next days your channels post. Each channel writes the post in its own voice.
To plan them yourself, set New entries to I plan them in Settings, Sources. Then tick entries and use the plan bar to choose the start, the pace and the voice.
The posts
Borker writes the posts for each of your channels on the day the entry is planned for. They land in the Command Center, and you approve them in Review the way you approve every other draft.