<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: koooyooo</title>
    <description>The latest articles on DEV Community by koooyooo (@koooyooo).</description>
    <link>https://dev.to/koooyooo</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4205898%2Ff97e2e5c-eeb0-4542-b191-171619199142.jpg</url>
      <title>DEV Community: koooyooo</title>
      <link>https://dev.to/koooyooo</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/koooyooo"/>
    <language>en</language>
    <item>
      <title>I Built an Obsidian Plugin Where an AI Angel and Devil Banter Over Your Journal</title>
      <dc:creator>koooyooo</dc:creator>
      <pubDate>Fri, 20 Nov 2026 14:00:55 +0000</pubDate>
      <link>https://dev.to/koooyooo/i-built-an-obsidian-plugin-where-an-ai-angel-and-devil-banter-over-your-journal-1ncj</link>
      <guid>https://dev.to/koooyooo/i-built-an-obsidian-plugin-where-an-ai-angel-and-devil-banter-over-your-journal-1ncj</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Foxt7lnrarpfe3hx0b1vv.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Foxt7lnrarpfe3hx0b1vv.png" width="800" height="557"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Overview
&lt;/h2&gt;

&lt;p&gt;I built an Obsidian plugin that takes a journal entry and has an angel and a devil praise and roast it—basically a banter review of what you wrote. I mainly use it on daily notes.&lt;/p&gt;

&lt;p&gt;At first glance it looks like a silly AI toy. It turned out more fun than I expected, so I wanted to share it.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/koooyooo/angel-and-devil-obsidian" rel="noopener noreferrer"&gt;https://github.com/koooyooo/angel-and-devil-obsidian&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://koooyooo.github.io/angel-and-devil-site/en/" rel="noopener noreferrer"&gt;https://koooyooo.github.io/angel-and-devil-site/en/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/user-attachments/assets/4cb76c93-52a1-4a85-8f78-bd2dc12e0a79" rel="noopener noreferrer"&gt;Demo video (based on this article)&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Background
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Digitizing the journal
&lt;/h3&gt;

&lt;p&gt;Over the past few years I’ve gotten into keeping a journal and work log in Markdown. I used to prefer handwriting on paper, but I finally gave in to digital convenience.&lt;/p&gt;

&lt;p&gt;Analog has texture and freedom; digital has search and sync. AI broke that balance. The decisive point: digital notes aren’t just digital data anymore—they become a strong knowledge base for collaborating with AI.&lt;/p&gt;

&lt;p&gt;That’s why I keep writing in Markdown. There are plenty of solid tools—Notion on the web, VS Code or Typora locally—but lately I’ve been using Obsidian the most.&lt;/p&gt;

&lt;h3&gt;
  
  
  Sharing content with AI
&lt;/h3&gt;

&lt;p&gt;When you work with AI, you often need an LLM to look at a document: “What do you think of this?” “Any concerns about whether this plan is realistic?” Sometimes you want a third-party, critical view; sometimes you want a fact check. In those cases, handing the file to the AI beats retyping everything. Concretely:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;With ChatGPT or Gemini in the browser, upload the local file&lt;/li&gt;
&lt;li&gt;In IDEs like Antigravity or Cursor, or CLIs like Claude Code or Codex, reference the file with &lt;code&gt;@&lt;/code&gt; in the terminal&lt;/li&gt;
&lt;li&gt;In Obsidian, open the vault in an IDE, or install a Terminal plugin and use a CLI agent&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;All of that works well and I’d recommend any of it. I just wondered if I could be a bit lazier. Engineers get to call laziness a virtue. We love automating everything.&lt;/p&gt;

&lt;h2&gt;
  
  
  Building an Agent Skill
&lt;/h2&gt;

&lt;p&gt;I started with an Agent Skill. Making a skill that says “review this document (journal)” is easy—but I wanted something with a bit more spark. The idea I landed on: an angel and a devil comment on the day’s entry.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why an angel and a devil?
&lt;/h3&gt;

&lt;p&gt;It’s not only that positive/negative characters are fun. What a journal often needs is exactly two things: a fair look at what you did well, and a clear list of what still needs work.&lt;/p&gt;

&lt;p&gt;The angel finds the good in actions you didn’t even notice. People struggle to feel confident about their own behavior—praising yourself can feel ridiculous—so you quietly get harsh with yourself. That can be healthy self-awareness, but as objective data it’s bias. An angel that says “good is good” and points out things you missed is worth more than simple affirmation.&lt;/p&gt;

&lt;p&gt;The devil puts unspoken weak spots into words. We like to think we’re average and objective; we’re usually more skewed than we admit. You can’t fully see your own biases, so a critical devil gets to cut to the point. Because it’s a devil, you might dismiss it as snark—until it names a real flaw. You can plug your ears and treat it as pure annoyance, or listen and grow.&lt;/p&gt;

&lt;p&gt;Then another idea: don’t stop at one-off comments—make them banter. Angel and devil were always supposed to argue on your shoulders. Sometimes they’ll just disagree; sometimes their lines will build on each other. You might get an insight—or just enjoy the exchange. Even if the banter is dumb, it’s over quickly.&lt;/p&gt;

&lt;h3&gt;
  
  
  Shipping the Agent Skill
&lt;/h3&gt;

&lt;p&gt;With that hypothesis, I built the Agent Skill. I drafted the core at night with AI and finished the details in the morning—about half a day. I’d built Agent Skills before, so the basics were familiar. The &lt;a href="https://agentskills.io/home" rel="noopener noreferrer"&gt;Agent Skills&lt;/a&gt; spec is simple anyway; you mostly follow it.&lt;/p&gt;

&lt;p&gt;In practice: put the main behavior in &lt;code&gt;SKILL.md&lt;/code&gt;, and put character sheets under &lt;code&gt;references&lt;/code&gt;—&lt;code&gt;Angel.md&lt;/code&gt; and &lt;code&gt;Demon.md&lt;/code&gt;. I wrote the personas carefully, and calling the skill made an angel (👼) and a devil (👿) banter in text. The quality was decent.&lt;/p&gt;

&lt;p&gt;That alone is a reason to keep journaling, and the output is fun enough. As a POC, I’d call it a success.&lt;/p&gt;

&lt;p&gt;Around then I was interested in voice output with the Agent Development Kit (ADK), so I extended the skill so users could opt into speech. (I didn’t end up using ADK.) Agent Skills can pick up scripts under &lt;code&gt;scripts&lt;/code&gt; when needed. I added a single Python file, &lt;code&gt;speak.py&lt;/code&gt;, that calls Gemini TTS.&lt;/p&gt;

&lt;p&gt;It was optional—nice if it worked, fine if it didn’t. It worked surprisingly well: the banter sounded natural. I used &lt;code&gt;gemini-3.8-live&lt;/code&gt; for TTS. It isn’t a dedicated voice product—just Gemini’s speech-focused model—and the quality was already high.&lt;/p&gt;

&lt;p&gt;You can try that earlier version here:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/koooyooo/dot-agent-angel-and-devil" rel="noopener noreferrer"&gt;https://github.com/koooyooo/dot-agent-angel-and-devil&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;After install, something like this starts the banter. Add a request for voice output if you want speech:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt; /angel-and-devil-note @notes/today.md
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Turning it into an Obsidian plugin
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Why Obsidian?
&lt;/h3&gt;

&lt;p&gt;After that, I brainstormed with AI for a better distribution path. My rough idea was “maybe a web app would reach more people.” Daily Agent Skill users are still a niche. When I threw that problem at the AI, the answer wasn’t “build a web service”—it was “ship an Obsidian or VS Code plugin.”&lt;/p&gt;

&lt;p&gt;Why? Today the skill uses a &lt;code&gt;GEMINI_API_KEY&lt;/code&gt; from the environment. A web service with the same setup needs someone to host a shared key. That someone would be me. If it’s free, I eat the cost. Charging might recover it, but I’m not sure the product earns that yet. Awkward middle ground—too risky as a first move.&lt;/p&gt;

&lt;p&gt;For “try it lightly,” Obsidian and VS Code plugins fit better. They’re not far behind a web app functionally—Electron means the same stack underneath. Users only pay their own API usage; beyond agent costs, it’s effectively free. The host app already ships excellent editor UX. Both are industry standards, and I’m happy to ride that.&lt;/p&gt;

&lt;p&gt;Also: I’d rather get feedback on an unfinished thing than charge for it and watch most people bounce. So I packaged the angel-and-devil flow as an Obsidian plugin. VS Code would have been fine too—I just use Obsidian.&lt;/p&gt;

&lt;h3&gt;
  
  
  What the Obsidian plugin adds
&lt;/h3&gt;

&lt;p&gt;As a plugin, I could ship a UI the Agent Skill never had—something closer to a world you can feel, beyond text or audio alone. I redrew the screen and the angel/devil art many times. The first designs were painfully safe. After many iterations I landed on a playful, pop look. I preferred light entertainment over a muted adult vibe that risks feeling oddly religious.&lt;/p&gt;

&lt;h3&gt;
  
  
  Architecture
&lt;/h3&gt;

&lt;p&gt;There’s no middle server. Obsidian talks to the Gemini API directly:&lt;br&gt;
&lt;/p&gt;

&lt;pre data-lang="mermaid"&gt;&lt;code&gt;sequenceDiagram
    actor U as User
    participant P as Obsidian plugin
    participant G as Gemini API

    U-&amp;gt;&amp;gt;P: Tap 😇😈
    P-&amp;gt;&amp;gt;G: Note body + angel/devil personas
    G--&amp;gt;&amp;gt;P: Banter (JSON)
    P-&amp;gt;&amp;gt;U: Show as chat bubbles

    opt When reading aloud
        U-&amp;gt;&amp;gt;P: Tap 🔊
        P-&amp;gt;&amp;gt;U: Confirm paid usage
        U-&amp;gt;&amp;gt;P: OK
        P-&amp;gt;&amp;gt;G: Banter lines
        G--&amp;gt;&amp;gt;P: Two-voice audio
        P-&amp;gt;&amp;gt;U: Play in sync with bubbles
    end

    opt When saving
        U-&amp;gt;&amp;gt;P: Save
        P-&amp;gt;&amp;gt;P: Append to end of note
    end&lt;/code&gt;&lt;/pre&gt;



&lt;h3&gt;
  
  
  How I developed it
&lt;/h3&gt;

&lt;p&gt;Same as the Agent Skill: document-driven development with my own Agent Skills (separate ones) for PRDs and design docs. LLMs often write bloated, scattered docs, so I keep tightening them. I push as much as possible into Mermaid for visibility. Once the design doc is clear and carefully reviewed, I have the LLM generate code from it—and you usually get something that runs.&lt;/p&gt;

&lt;p&gt;After that it’s endless polish: default to voice or ask each time? settings for defaults? scroll math that clips the UI edge? voices that slowly morph mid-banter? Fix those one by one. Repeat, and the “AI scaffolding” smell fades until you actually want to use it yourself.&lt;/p&gt;

&lt;p&gt;Finally I scan for design changes worth making early. This time I stopped treating angel and devil as hard-coded—they’re characters among others, so I can plug in more personas later. The leads are still the angel and the devil. Demand is still unknown, so I only left minimal extensibility and decided to learn after shipping. After that point, you can refactor forever without changing what users see—quiet but important extensibility.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;When voices slowly morph during banter&lt;/strong&gt;&lt;br&gt;
The angel uses Leda (a relatively high female voice); the devil uses Puck (male). In a 1. angel → 2. devil → 3. angel → 4. devil → 5. angel sequence, turn 4 often got higher and turn 5 lower. When generating multiple speakers at once, voice traits can bleed between speakers. Prompt tweaks weren’t enough, so internally I stopped generating the whole scene at once and split into pairs: (1–2), (3–4), (5). That largely stopped the gradual voice drift.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h3&gt;
  
  
  How to use it (short version)
&lt;/h3&gt;

&lt;blockquote&gt;
&lt;p&gt;Full details are in the GitHub repo.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;ul&gt;
&lt;li&gt;From &lt;a href="https://github.com/koooyooo/angel-and-devil-obsidian/releases" rel="noopener noreferrer"&gt;Releases&lt;/a&gt;, download the latest &lt;code&gt;angel-and-devil.zip&lt;/code&gt; and unzip it&lt;/li&gt;
&lt;li&gt;Put the contents of the &lt;code&gt;angel-and-devil&lt;/code&gt; folder into &lt;code&gt;${YOUR_OBSIDIAN_VAULT}/.obsidian/plugins/angel-and-devil&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Restart Obsidian&lt;/li&gt;
&lt;li&gt;Enable &lt;strong&gt;Angel &amp;amp; Devil&lt;/strong&gt; under Community Plugins&lt;/li&gt;
&lt;li&gt;In the plugin settings at the bottom, add your &lt;code&gt;GEMINI_API_KEY&lt;/code&gt; and save

&lt;ul&gt;
&lt;li&gt;If you don’t have a key, create one at &lt;a href="https://aistudio.google.com/docs/api-key" rel="noopener noreferrer"&gt;https://aistudio.google.com/docs/api-key&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;The key is stored in Obsidian’s secret storage

&lt;ul&gt;
&lt;li&gt;(* Secret storage is shared across plugins; other plugins can read it. If you use untrusted plugins, skip setting a key / using this plugin for safety.)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Journal text is sent directly to the Gemini API with that key (no middle server today)&lt;/li&gt;
&lt;li&gt;Usage is billed to your key. Check &lt;strong&gt;Gemini API usage&lt;/strong&gt; in &lt;a href="https://aistudio.google.com/" rel="noopener noreferrer"&gt;Google AI Studio&lt;/a&gt; often at first (reporting can lag by about a day)

&lt;ul&gt;
&lt;li&gt;Roughly a few yen to ~10 yen per run in my experience (not rigorously measured)—on the order of a few cents USD&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Closing
&lt;/h2&gt;

&lt;p&gt;After all the twists, what I ended up with is the screen at the top. I’m pretty happy with it already. Personality depth, whether it stays interesting over time, and what else it could become—that’s still the beginning. When the mood hits, I want to keep iterating.&lt;/p&gt;

&lt;p&gt;If you’re curious, please try it. Even a one-line reaction would make me genuinely happy.&lt;/p&gt;

&lt;p&gt;Tools and services got much easier to ship once I started using AI. It’s a high birth / high death era for software. Engineering may not fully follow, but the loop will get faster either way. Building lots of small apps to sharpen craft and market sense feels more important. I’m still feeling my way—for now I’ll keep the daily journal going with this angel and devil.&lt;/p&gt;

</description>
      <category>obsidian</category>
      <category>ai</category>
      <category>showdev</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
