|
|
Was this forwarded to you? Get The Fourth Estate AI Brief in your inbox →
|
|
|
|
View this issue in your browser
Friday Deep-Dive
I automated our Athlete of the Week video. Here is the honest version.
I gave Claude one raw Athlete of the Week interview, almost eleven minutes of two people talking on a phone camera, plus eight game photos, our logo, and the sponsor spot we had been running. Back came a finished five and a half minute video: cold open, animated title, a broadcast-voice sponsor read, the interview cut between wide and tight with game photos over the long answers, and a thumbnail and YouTube text to go with it. Then I had Claude build a web app so our sports editor can do it himself every week. The honest headline before anything else: the app is deployed and has not yet finished a single live episode. Two live runs failed, both are fixed, and the reasons they failed are the most useful part of this. Below: the prompts, the one idea worth stealing even if you never build anything, what it actually costs, and a question about student data I had not thought about until I wrote this up.
|
One interview in, a finished episode out, and then an app to repeat it
Two phases. First, Claude edited one real episode start to finish: it transcribed the interview, wrote an editor's critique, had ElevenLabs record a broadcast-voice sponsor read, assembled the cut with free open-source video tools, placed game photos over the long answers, and produced a thumbnail plus YouTube title, description and chapters. Second, it wrote a Python web app, pushed it to a private repository and deployed it, so the sports editor pastes the announcement email he already sends, drops in the photos and video, reviews, and approves. The app is not proven live yet: two runs failed, both on account settings rather than anything to do with video. In the full post: all four prompts, the corrections that became the app's permanent rules, the real costs with one of my own assumptions corrected, and the student-data question nobody raised.
Two things here are worth your time even if you never build an app. The first is that editing one real episode alongside the AI, then writing down every correction you gave it, is how you discover what your weekly tool actually needs to do. My three corrections became its permanent rules. The second is that the smartest decision in the build was not technical: the app reads the announcement email our sports editor was already writing, so he is not learning a new process. Build around the paperwork your staff already produces and the weekly job becomes paste, drop, approve.
All four prompts, the costs, and what broke →
|
|
What is?
API Key
What it is: An API key is a long password that lets one piece of software use another company's service without a person signing in. When an app needs to send text to an AI service or get a voice recording back, it includes its key with the request, and the service checks the key, does the work, and bills whoever owns it. Keys usually carry permissions, so one key might be allowed to make speech but not to transcribe audio. They are not the same thing as your subscription: a key bills separately, per use, straight to whoever created it.
Why publishers care: Two reasons, and the first one cost me two failed attempts. Anything built for your publication, whether you build it or pay someone, almost certainly runs on keys, and a key with the wrong permission switched off fails in a way that looks like the software is broken. Knowing to check the key first saves an afternoon. The second reason is money and security. A key is a live charge against your account and it does not care who is holding it, so it belongs in the hosting service's settings, never in an email, a shared document, or a text message. If somebody leaves, the keys get replaced the same day the door code does.
|
|
|
|
Like what you see here, please forward to someone who you think would enjoy reading about AI in publishing!
|
|
Trevor
Trevor Slette
Co-founder, Quadd.ai · 28-year community publisher
trevors@quadd.ai
·
Book a 15-min call
·
LinkedIn
P.S. Take last week's interview, put it in a folder, and run the first prompt in this issue. Send me what the critique says about your own footage. I would genuinely like to see what it tells other publishers, because mine was more blunt than I expected.
|
|
|
|
|
From meeting audio to usable copy.
Upload a council meeting, an interview, a coach's post-game scrum. Get a clean transcript and an AI summary, then ask Quadd to compose a first-draft story or paste your own prompt, and get formatted output in your publication's exact style. No more scrubbing through forty minutes of audio at 9pm because the lede quote was somewhere in the middle. Trained on the way reporters actually use audio, not the way podcast editors do.
See how transcription works →
|
|
|