DEV Community

Cover image for My AI Agent Skill Found Ten Blog Post Ideas in One Project. I Wrote One.
Stephan Miller
Stephan Miller

Posted on Originally published at stephanmiller.com on

My AI Agent Skill Found Ten Blog Post Ideas in One Project. I Wrote One.

I built an AI agent skill that comes up with article ideas, and the post I was going to write about it was the most obvious one: basically a README with a header image.

So before I wrote about it, I ran the skill on itself to see if any angle sounded better than the one I already had. It came back with eleven. This post is one of them, the tutorial.

That’s how I use it now. It hands me a dozen or so ideas, and I use two or three. Sometimes one. The skill can plan a real backlog, and it’s built to, but what I get out of it most is options.

The skill is called angle-board. Below is how, then one real board built start to finish from a real project, my Obsidian Mobile Optimizer plugin, and what happened to the ten posts it found.

What the Skill Does

An angle is one specific post you could write about a thing: which piece of it, for whom, framed how. The skill reads your notes on a project and gives you angles at five levels, from a single error with a single fix up to a claim about how everybody should work. Then it writes them to a markdown file.

The five levels and what each one has to have before the skill will add it to the board:

Level What the post is What it needs to exist
Thesis What everyone gets wrong 3+ independent proof points
Practice How to work, pulled out of projects 2+ instances of the same pattern
Project story How I built X and what broke One project arc with a real failure in it
Tutorial Build the thing end to end One feature plus code to point at
Weeds One error, one fix One concrete failure with a concrete fix

What the Skill Does

The right column makes it worth running. Any AI will give you ten blog ideas… with confident bluffs about things you’ve done once.

Install It

It’s an agent skill: a folder with a SKILL.md and a few workflow and reference files, which your coding agent loads when you ask for what it does. It runs in Claude Code, Codex, Cursor, OpenCode, GitHub Copilot and Gemini CLI. Nothing else from the repo is needed.

For Claude Code, globally:

git clone https://github.com/eristoddle/agent-skills.git
cp -r agent-skills/skills/angle-board ~/.claude/skills/

Enter fullscreen mode Exit fullscreen mode

For a single project, copy it to .claude/skills/ in that project instead. The other tools each have their own folder, listed in the repo README. If you use skillshare to keep skills synced across tools, skillshare install https://github.com/eristoddle/agent-skills pulls in the whole repo.

Then point it at your notes: “angle board for ”, or “what could I write about this” with a notes file open. If you haven’t used skills before, I wrote the agent skills guide I wish I’d had.

Step 1: Start With the Research

The skill doesn’t just read the one file you hand it. It scans everything around it, because the ideas at a higher level only show up when the same thing happens in multiple places.

For the Obsidian mobile optimizer, the starting material was the project outline from July and the October 30 session where Kiro’s first version turned out to measure nothing. My Ideas folder had nothing else on the project. So the research became my published Obsidian plugin posts.

The scan never reads every file whole. It lists them, grabs the dates and headings, and only then reads the slices that look related. This is the loop from workflows/build-board.md, with your folder swapped in:

cd <pool-dir>
ls -la *.md
for f in *.md; do
  echo "=== $f"
  grep -n "^project:\|^date:\|^# \|^## " "$f"
done

Enter fullscreen mode Exit fullscreen mode

That’s a few KB for a whole folder of notes.

And here’s what it turned up. In my Jules post from June 2025 I wrote “Jules created broken unit tests again.” In the October session, Kiro’s 94 tests all passed against a fake version of Obsidian and every real measurement came back null.

Step 2: Cut the Material Into Subjects

Step 2: Cut the Material Into Subjects

Next it breaks the material into subjects, and it has a list of where subjects hide: an error and how you recovered from it, a task you checked off that has a story behind it, a combination of tools, a file you kept touching over and over, a question you parked, a dead end, a pattern that shows up in two projects.

The cuts on the mobile optimizer board, each with the thing it can point at:

  • The Performance API returns nothing for plugins. Obsidian reads a plugin’s main.js off disk and evaluates it, so there’s no timing entry to find. A live check came back perfNamed: 0.
  • styles.css in the wrong folder. Obsidian only loads it from the plugin’s root. Kiro put it in src/, so nothing was styled. The fix is one git mv in commit ea5f1f1.
  • Copying .obsidian copies node_modules. The “lean” mobile config from July was 794 MB and 44,347 files, because every plugin I develop in that vault drags its dependencies along.
  • IndexedDB databases named after plugins , which is how you figure out which one is hoarding storage.
  • Driving the running app over the DevTools protocol with --remote-debugging-port=9222 and a small Node script.
  • Prior art. Obsidian already has a built-in Debug startup time view. That one changed the pitch.

The rule it applies: if something shows up once and left nothing behind (no commit, no error, no number), it’s a detail. It gets folded into a bigger subject instead of getting its own post.

Step 3: Walk the Ladder, and Let Rungs Stay Empty

Then it goes down the five levels and checks each one against the right column of that table.

On this board, the practice level got filled, and only because of step 1. “Your AI agent’s tests pass because it wrote the world they run in” needs two or more instances, and the old posts supplied them.

The thesis level came out empty. The board says so, in its own line:

- **A5 — Thesis: (empty)** — all three proof points are Obsidian plugins.
  A thesis like "agents can't see the app, so 'done' means 'compiles
  against its imagination'" needs a proof point outside plugin dev — a web
  app or CLI where driving the real thing changed the outcome. Unlocks with
  the next project where that happens.

Enter fullscreen mode Exit fullscreen mode

Step 3: Walk the Ladder, and Let Rungs Stay Empty

A chatbot fills every slot. This one tells me the big claim isn’t earned yet. An empty level is information: it tells you what to go do more of.

Step 4: Give Every Angle a Reader and a Moment

Every angle names a specific person and the moment they’re in. “Developers” doesn’t count. The mobile optimizer board’s tutorial angle names “the person currently in the reload loop, phone in one hand, laptop in the other, who wants steps and not a story.”

That reader doesn’t want to hear how the plugin got built. They want to fix their issue.

Here’s that angle, minus its pitch and evidence lines:

- [] **A2-01 — Find the Plugin Crashing Obsidian on Your iPad (Without
  Turning Off 40 Plugins by Hand)** ⏫ #altitude/tutorial #lens/1am-rescue #ev/strong
    - **Reader:** the person *currently* in the reload loop, phone in one
      hand, laptop in the other, who wants steps and not a story.
    - **Don't restate:** no how-it-was-built and no Kiro story — that's
      A3-01. This post starts at "your iPad is looping."

Enter fullscreen mode Exit fullscreen mode

Two more things depend on every angle. A lens , which is the framing: postmortem, build-along, receipts, confession, and so on. The skill picks a few per board and has to invent at least one that isn’t on its list, so every board doesn’t come out as the same seven posts with the nouns swapped. This board invented 1am-rescue and the-mock-is-the-spec. And an evidence rating : strong, medium, or thin. Thin angles stay on the board, tagged #ev/needs-you, so I can see which ones I’d be writing from memory.

Step 5: Pick the Pillar and Wire the Spokes

One angle becomes the pillar, the main post. Usually it’s the project story, the one with the failure in it. Everything below it becomes a spoke that links back up.

Every spoke carries a Don’t restate line saying what belongs to the pillar. You saw one in step 4: “no how-it-was-built and no Kiro story.” Without that line, four posts off one project tell the same story four times.

Step 6: What the Board Looks Like on Disk

Step 6: What the Board Looks Like on Disk

It’s a markdown file. Frontmatter on top, then the pillar, the spokes, the higher levels, a “thin ice” section for takes with no proof, and questions for me at the bottom.

Here’s part of the board the skill built about itself, open in Obsidian. These things are long. This is maybe a fifth of it.

The angle board for the angle-board skill open in Obsidian, showing the thesis pillar and the first story spoke as checkbox tasks with tags

The skill stops there on purpose. It never writes the article.

What Happened to the Ten

The mobile optimizer board has ten angles on it, plus the empty thesis line. I wrote one post: Obsidian Keeps Reloading on My iPad, So I Built a Plugin to Find the Plugins Killing It.

But go grep that post for the angles. The fake-Obsidian tests are a section. The styles.css folder is in there. So are node_modules, the Performance API, IndexedDB, the DevTools port, and Obsidian’s own startup timer. Nine of the ten show up in it somewhere. None of them became its own post.

The board didn’t give me a posting schedule. It showed me everything that was in the project, and I just wrote a lot of it into one post.

And the plugin worked. The iPad stopped reloading. Then Remotely Save, the plugin that syncs my vault to the iPad and the whole reason I wanted the iPad back, refused to sync because I’d started putting emoji in my file names. So that’s still broken.

Planning or Sparking

Right now my Ideas folder has six of these boards in it. Not one box on any of them is checked. Some of that is me not checking the box when a post goes out. Most of it is that I was never going to write the whole list.

If you want a content plan, the board is one. Pillar, spokes, readers, a don’t-restate line on everything, and checkboxes. Work down it.

If you’re like me, run it the week after you ship something, read the board, and see which two or three angles make you want to write.

Go grab angle-board, run it on the last thing you shipped, and see which posts were hiding in it.

Top comments (0)