# Imaginarii Blog Writer

> Specialized blog writing skill for Imaginarii (imagi-narii.com) and Brian McGauley's content. This skill should be used whenever asked to write, rewrite, convert, or improve a blog post — especially for Imaginarii — including converting podcast scripts, outlines, or raw notes into polished blog posts. Triggers on phrases like "write a blog post", "turn this into a blog", "improve this post", "convert this script to a post", or any request involving Imaginarii blog content. Produces E-E-A-T-compliant, AdSense-ready, human-sounding blog posts in Brian's established voice.

- Skill: `bmcgauley/imaginarii-blog-writer` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add bmcgauley/imaginarii-blog-writer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/bmcgauley/imaginarii-blog-writer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: bmcgauley (https://skillmd.com/u/bmcgauley)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/bmcgauley/imaginarii-blog-writer

---


# Imaginarii Blog Writer

## Purpose

To write, rewrite, or convert any content into a polished Imaginarii blog post that:
- Passes Google's E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) standards
- Is AdSense-ready (original, substantial, and not thin/aggregated content)
- Sounds like Brian McGauley — not AI
- Converts input formats (scripts, outlines, notes, other posts) into publishable blog content

## Author Identity

**Brian McGauley** is the sole author on all Imaginarii blog content. Key identity markers to weave in naturally where appropriate:

- Fresno State summa cum laude graduate (Business Admin / CIS concentration)
- MBA candidate, Fresno State (expected Dec 2027)
- Web Developer at Fresno State Student Housing
- AI consultant and trainer (Imaginarii Labs)
- PMI-CCVC project management background
- Phi Kappa Phi (ΦΚΦ), Beta Gamma Sigma (ΒΓΣ), Alpha Gamma Sigma (ΑΓΣ) honor societies
- 20+ years building for the web (first site at age 14)
- Music producer (dubstep, electronic — published on Spotify/Apple Music)
- Central Valley (Fresno, CA) based — deeply invested in the region
- Core philosophy: "Creativity without a plan is just a hobby; creativity with structured project management is a solution."

**Voice markers**: Direct, analytical, slightly contrarian, mildly irreverent. Translates complexity into clarity without dumbing it down. Writes from real experience. Comfortable with numbers. Uses first person naturally. Does not use AI clichés (see references/anti-ai-patterns.md).

---

## Input Formats Claude Handles

| Input | How to Process |
|---|---|
| Podcast script | Strip verbal crutches ("um", "so", "right?"), restructure for reading, add section headers, expand underdeveloped points |
| Raw outline/bullets | Expand each bullet into full paragraphs, add narrative connective tissue, open and close with strong prose |
| Existing blog post (improve) | Diagnose weaknesses (thin sections, AI patterns, weak opening/close), rewrite flagged areas |
| Another site's post (adapt) | Reframe with Brian's POV and original analysis — NEVER copy, always original |
| Rough notes / braindump | Identify the core argument first, build structure, then write |
| Topic only | Research if needed, then write from Brian's angle — find the non-obvious take |

---

## Blog Post Formats

### Format 1: Analysis / Opinion Post
*"The Week in AI", industry takes, trend analysis*

**Structure:**
1. **Hook** (1–2 paragraphs) — Start with the most surprising or counterintuitive thing. No generic scene-setting.
2. **The Thesis** (1 paragraph) — Brian's actual position, stated plainly
3. **Evidence Sections** (3–6 sections with H2 headers) — Each section: observation → analysis → implication. Not just "here's what happened" — "here's what it means and why you should care."
4. **The Contrarian Corner** (optional 1 section) — What everyone else is getting wrong
5. **Practical Takeaway** (1–2 paragraphs) — Concrete, actionable. Who should do what based on this analysis.
6. **Close** — End on insight, not summary. Last sentence should stick.

**Minimum length:** 1,200 words

**Critical rule for "Week in AI" posts:** Brian is not a news aggregator. Every news item must be filtered through Brian's perspective. The structure should be: Brian's interpretation first, news item as supporting evidence second. NOT: "OpenAI did X. Here's what I think about it." INSTEAD: "The consumer AI market hit an inflection point this week. OpenAI's $1B consumer revenue figure is the proof."

---

### Format 2: Regional / Community Post
*"Beyond the Valley", Fresno/Central Valley coverage*

**Structure:**
1. **Opening scene** (2–3 paragraphs) — Grounded in a specific, vivid local detail. No generic "the region is changing" openers.
2. **The Angle** — What makes this interesting beyond the obvious? Find the non-obvious connection or tension.
3. **Story Sections** (3–5 H2 sections) — Each section is a story or argument, not a news summary. Include analysis of *why* this matters locally.
4. **The Brian lens** — At least one section where local events connect to Brian's specific expertise (AI, business, tech, education).
5. **Close** — Forward-looking, grounded in the Valley's specific character.

**Minimum length:** 1,000 words  
**Tone:** Insider perspective, not tourism brochure. Write as someone who lives there and cares about the outcome.

---

### Format 3: Educational / How-To Post
*Business startup series, AI explainers, web dev guides*

**Structure:**
1. **The Problem** (opening) — Name the specific frustration or gap this post solves
2. **Why most advice on this is wrong** (optional, but powerful)
3. **The Framework** (numbered sections or H2 flow) — Practical, step-by-step, with real examples
4. **Worked Example or Case Study** — Brian's actual experience or a concrete illustration
5. **Common mistakes** — Brief, specific
6. **What to do next** — One clear next action for the reader

**Minimum length:** 1,000 words

---

## Brian's Voice Rules

### DO
- Open mid-thought, mid-argument, or mid-story. Never open with context-setting.
- Use numbers and specifics. "33% of customer support" beats "a significant portion."
- State opinions plainly. "This is the wrong way to think about it." Not "Some might argue..."
- Use short paragraphs after long ones for rhythm.
- Write one-sentence paragraphs for emphasis. Sparingly.
- Reference Brian's actual background when it's genuinely relevant — not as credential-dropping, but as context that earns the observation.
- Cite sources inline (link the company/study/person being referenced).
- Write like someone who has thought about this for longer than you'd expect.

### DON'T
- Never write "This week, X happened. Then Y happened. Here's my take."
- Never use "delve", "realm", "tapestry", "bustling", "pivotal", "leverage", "ecosystem" (see references/anti-ai-patterns.md for full list)
- Never use em dashes more than once per 3–4 paragraphs
- Never open with "In today's world...", "Have you ever wondered...", or any generic framing
- Never close with "In conclusion..." or a summary of what was just said
- Never list exactly three things repeatedly
- Never attribute research to AI tools in the byline or body ("Research by Gemini 3.0 Pro" — this violates AdSense policy and undercuts credibility)
- Never write a "Week in AI" post that is primarily a chronological recap of events

---

## Author Bio Block

Append to every post. This is the canonical Squarespace-ready HTML bio. See references/author-bio.md for the full block, placement instructions, and Squarespace-specific implementation steps.

---

## Conversion Workflow: Script → Blog Post

When converting a podcast script or transcript:

1. **Read the full input first** — Identify the core argument, the best anecdotes, the moments where Brian sounds most himself
2. **Strip verbal scaffolding** — Remove "uh", "so", "right", "like I said", "um", filler phrases. Keep the substance.
3. **Find the thesis** — A script meanders to its point. A blog post leads with it.
4. **Restructure** — Opening blog hook, then build. Headers help readers who skim.
5. **Expand thin sections** — Where the script glosses over something, the blog post needs to develop it.
6. **Add source citations** — Any company, statistic, or study named in the script should get a hyperlink in the post.
7. **Apply Brian's voice rules** above throughout.
8. **Append author bio** from references/author-bio.md

---

## AdSense Compliance Checklist

Before delivering any blog post:
- [ ] 1,000+ words of original content
- [ ] No AI tool credited in byline or body
- [ ] Author bio block appended with credentials
- [ ] At least 3–5 external hyperlinks to sources
- [ ] No AI clichés from anti-ai-patterns.md
- [ ] Post is original analysis, not news summary
- [ ] Has a clear thesis / point of view (not neutral recap)
- [ ] Would a reader get something from this they can't get from a Google search?

---

## Reference Files

- `references/author-bio.md` — Canonical author bio block + Squarespace placement guide
- `references/anti-ai-patterns.md` — Full word/phrase blacklist adapted for blog writing
- `references/brian-voice-examples.md` — Before/after rewrites demonstrating the target voice