I gave Claude one prompt: make an animated Halloween pumpkin town that lights up one house at a time at night.
32 seconds later: 16 pumpkin houses grown, carved and lit, bats, a ghost and a soundtrack, all written as code. No stock assets.
Happy Halloween from Melbourne.
@binghott I stopped searching sessions. Every agent writes a short report file when it finishes, and grepping those is way faster than hunting for the chat it happened in.
@brookejlacey Same thing on a much smaller scale for me. The agents can draft and post all day, but anything that talks to a real person still waits for me, and that queue is the slow part. Did she say which people stuff eats the most time?
@omkarships The one thing I can't do from the app: launchd kicks off claude -p on a schedule every morning, so the agents run without me opening anything. Headless runs and piping the output into other scripts is where the terminal wins for me.
*ehm ehm* BIG ANNOUNCEMENTS DAY 📣
two new things cooking in herdr labs 🐏🧪
a brand new herdr-core, and a desktop app built on it. open source.
first, the app: software that fits you. every part of it is a file your agent can change. you just ask.
Learn to build evals, folks!
You're not really doing recursive self-improvement (RSI) if you are not doing evals. And don't tell me your agents are generating the evals for you. They are pretty bad at it.
I have found it really interesting and useful to give agents a concrete way to measure results and stay on track with a long-term goal. It's easier to hill climb when things are clearly measured and well defined. Probably one of the most important skills anyone in the space can have today.
It doesn't matter how many agents and intelligence you throw at a problem; you are not going too far without proper evals.
Anthropic donated Agent Skills to the Agentic AI Foundation (Linux Foundation).
A skill is a folder with a SKILL.md file that teaches an agent one task. Anthropic says 70+ platforms support it, including ChatGPT and Cursor.
Source: Anthropic blog, Oct 22
6 one-line prompts that make AI check its own work:
1. List what you'd need to know first
2. List 3 ways your answer could be wrong
3. Rate confidence 1 to 10
4. Review it as a strict reviewer
5. Show the steps
6. Say "not sure" instead of guessing
Full wording in the images.
What does a forward deployed engineer (FDE) do?
They go to the customer. Picture a bakery: sit with the owner, learn how orders, suppliers and rosters really work, then wire AI into that.
The model is the easy part. The plumbing and trust are the work.
Bakery is illustrative.
@mardehaym When one missed field means someone doesn't get paid, I'd keep a human click before anything gets submitted, at least until the error log has been boring for a few months. What ended up convincing the CTO, accuracy numbers or the review step?
@IamAroke I think the skill moves more than it disappears. Spotting what's subtly wrong in a diff is still problem solving, and it's hard if you never wrote the loop yourself. Having juniors write it first, then compare with the model's version, seems fair.
@itz_komal01 Part of it is the feedback loop. A broken web app shows you in seconds, but a database bug can sit there quietly for weeks. On the complex stuff I'd want the tests written before any vibing starts.
@snowmaker Threads are the part worth stealing. My agents each write a report file and one coordinator reads them, and the hard bit turned out to be deciding which message needs a human. How do you decide what pings you?
9 AI terms every manager should know, one line each:
Model, prompt, context window, token, hallucination, agent, RAG, MCP, evals.
The one people skip is evals: tests that check the AI's answers before and after a change. Ask any vendor how they run them.