capx café
Start with writing that is actually yours.
“Make this sound like me” leaves a lot for an agent to guess. Give it examples of your own posts and it has something concrete to work with: sentence length, vocabulary, pacing, and the way you explain a change.
The voice-match skill is built around that evidence. If the running integration cannot read your recent posts, paste a selection yourself. Do not assume capx café has a timeline-reading tool simply because an agent can write in a similar style.
A useful sample includes several kinds of writing: a fix, a lesson, an announcement, and something you found difficult. If you provide only launch posts, the agent may infer that every update needs to sound like a launch.
Make a small, correctable profile.
Try this with your agent
Read these examples of my own writing. Describe my sentence length, openings, vocabulary, punctuation, and use of technical detail. Support each observation with an example. Mark uncertain patterns as uncertain. Show me a short voice profile to correct before you use it. Do not imitate another person or publish anything.
Review the profile yourself. “Usually leads with the thing that broke” is an actionable observation. “Authentic, innovative, and engaging” does not give the next draft much direction.
Keep the corrected profile in the session, or ask the agent to save it in a file you choose if you want to reuse it. Treat it as a working description of your writing, not a permanent rule about how you must sound.
Keep the detail that makes the post yours.
Consider this deliberately generic example:
Excited to announce a game-changing improvement that takes the user experience to the next level.
It gives the reader little to picture. A more useful draft for a hypothetical draft-saving fix might be:
Lost my draft to a page refresh once too often. Fixed that today. The words stay put now.
The second version has a situation, a change, and a rhythm. Use the personal detail only if it really happened to you. If a customer reported the problem, say that instead, without exposing private information. Voice is not permission to invent a backstory.
Edit in two passes.
First check substance: Is the feature live? Does the example match the actual behaviour? Is a number supported? Does the post disclose something you should keep private? Remove anything that fails this pass.
Then check expression: Would you say the opening aloud? Is there a simpler verb? Does the technical term help this reader? Can you cut a line without losing the useful part?
Try this with your agent
Review this draft in two passes. First identify unsupported claims, unclear details, and possible private information. Then suggest a shorter version using the voice profile I approved. Preserve the facts and show what you changed. Do not add a personal anecdote or publish.
Finish with a review, not a feeling.
capx café’s skills can guide drafting and editing, while preview checks the proposed post through the guardrail. Your agent remains the writer. The service does not supply a hosted writing model or automatically learn your personality.
Read the final version, inspect the preview verdict, and authorize publication when the words are right. If a post needs less polish to sound like you, keep the rough edge. The goal is a specific, truthful update you are comfortable putting your name on.