Hi, I'm Shingo Suzuki, also known as Suzushin.
As I briefly mentioned in my introduction, there's something I've wanted to do since starting this blog: create an agent team to help expand its reach and maximize revenue.
“Doing everything alone is hard. Could I give AI agents different roles and have them work as a team?”
I decided to try it with Claude Code. Here's a look at the agents I made and the things that didn't go smoothly.
The agents I've made
There are seven so far:
- Secretary: Immediately records ideas and observations, without evaluating them or asking questions.
- Brainstormer: Draws on existing articles, experiences, and revenue plans to suggest concrete article titles.
- SEO agent: Researches keywords and organizes title ideas and headings.
- Interviewer: Asks me directly for experiences rather than inventing anecdotes.
- Writer: Imitates my style to write articles.
- Proofreader: Checks typos, broken links, and inconsistent style before posting.
- Marketer: Suggests revenue strategies for affiliate links, ads, and my own products.
This article itself came from the brainstormer's suggestions. I'm using the SEO and writing agents to create it too!
Things that went wrong
Honestly, it wasn't all smooth sailing.
Running into security restrictions
The first problem was Wordfence, the WordPress security plugin, blocking the Application Passwords feature needed for automatic posting. One setting change resolved it, but I was a little worried when it simply wouldn't work.
I also found that the hosting provider's security features rejected the requests used to update articles. Switching to another way of sending them avoided that problem.
The theme feature didn't work
While building the marketing agent, I tried using the theme's Amazon and Rakuten product-search features. The actual calls returned errors.
It's quietly discouraging to design around something you expect to work and find that it doesn't! I abandoned automating that part and switched to registering real affiliate links myself.
The trap of identical filenames
Another surprisingly awkward issue involved thumbnails. Uploading every article's image under the same filename made them hard to distinguish in WordPress's media library. At one point, an image I needed disappeared.
I fixed this by including an article-specific identifier in uploaded filenames.
What changed when I used the team
After this trial and error, I got to the point where I could create articles with the team and publish them to WordPress.
The biggest change is spending less time stuck for ideas. Previously, deciding what to write next took a while. Now the team can look across existing posts and experiences and suggest specific titles, so I get stuck less often.
What I'd like to try next
The team is still a work in progress.
I'm not using social media yet, so an agent for social distribution is on hold. I'll tackle traffic and revenue analysis once there are more visits to analyze.
As the article collection grows, I'd like an editor-in-chief role to prioritize what comes next, and perhaps an agent that alerts me when published articles become outdated.
Building things one at a time through practical work feels like part of this blog's wider theme: taking on challenges and trying to turn my life around.
If you'd also like to use AI agents to streamline a blog, I'll keep sharing what works and what doesn't. I hope it helps.
This article focuses on my impressions. I've put the more detailed thinking behind the seven roles, the prompts I actually gave Claude Code, and how I resolved the obstacles into a paid article on note. If you're interested in going deeper, you're welcome to read that too.