Let me explore your vault's actual structure, templates, and conventions more deeply first so I can write skills that are grounded in how you *actually* work, not guesses. Listed directory %C2%A7%20Inbox Listed directory -tmp Listed directory --tmp Listed directory 1%20Focus Listed directory OTD Listed directory 2%20Commonplace Listed directory bb Listed directory from Listed directory tmp Viewed Note%20Composer%20Template.md:1-13 Viewed --%20PPL%20File.md:1-47 Viewed --Change%20File%20Status.md:1-14 Viewed --tmp.md:1-61 Viewed toggle-publication.md:1-7 Viewed ensure-publication.md:1-6 Viewed FULL%20Bear%20Blog%20Metadata%20Pack.md:1-14 Viewed from-Chat.md:1-3 Viewed from-Wikipedia.md:1-3 Viewed Current%20Status.md:1-32 Now let me look at a few more things to understand your conventions fully — specifically the Bear Blog templates and some sample notes: Listed directory bb Viewed launch-tmp.md:1-25 Viewed strip-tags.md:1-6 Searched for files: * Searched for files: app.json Viewed app.json:1-34 Viewed --bb%20Post%20wm.xyz%20Metadata%20&%20Footer.md:1-20 Viewed --bb%20Post%20wm.foo%20Metadata%20&%20Footer.md:1-24 Viewed --%20New%20Bill%20Questionnaire%20Data%20Collector.md:1-42 Now let me look at a few sample notes from Focus areas to understand typical note shapes: Searched for files: *.md Viewed --%20@%2001%20H1%20Title.md:1-3 Searched for files: *.md Viewed ideas.md:1-19 Viewed always%20remember.md:1-9 Now I have a thorough understanding of your vault. Let me also check if there's an existing `.claude` directory where these skills could logically live: Listed directory .claude Good. Now I have the full picture. Let me create a set of skills tailored to how your vault actually works. I'll place them in a `.agent/skills/` directory at the vault root — this is where Antigravity looks for them. Created SKILL.md Created SKILL.md Created SKILL.md Created SKILL.md Created SKILL.md Created SKILL.md All six skills are created. Let me write you a summary artifact to meditate on: Created cpb_skills_overview.md Done. Here's the short version of what I built, and things worth meditating on: --- ## Six Skills, Installed at `.agent/skills/` | Skill | What It Does | When You'd Use It | | --------------------- | -------------------------------------------------------------------------- | --------------------------- | | **📥 inbox-triage** | Reads unsorted `§ Inbox/` notes, suggests destinations, moves with your OK | Notes pile up in Inbox | | **📝 note-creation** | Creates notes with correct frontmatter, placement, and body conventions | "Make me a note about X" | | **🔍 vault-health** | Audits for broken links, missing frontmatter, orphans, tag hygiene | Periodic maintenance | | **📰 bear-blog-prep** | Converts Obsidian notes → Bear Blog format for wm.xyz or wm.foo | "Prep this for publishing" | | **🔗 link-and-tag** | Finds unlinked mentions of existing notes, suggests tags | After writing something new | | **📊 status-update** | Adds a timestamped micro-blog entry to `Current Status.md` | "Post a status" | Every skill was written by reading your actual templates, folder structure, frontmatter conventions, and Bear Blog metadata — not generic guesses. ### Key thing to understand These skills are instruction files *I* read — they're not Obsidian plugins and they don't replace your Templater/QuickAdd workflows. Those run inside Obsidian when you're working directly. These run when you're working *with me*. They just make sure I already know how your vault works so you don't have to re-explain it every time. You can open, read, and edit any of them in Obsidian at `.agent/skills/[name]/SKILL.md`. If your conventions evolve, just update the skill.