Publish: Untitled

[ComputelessComputer]

Article Ready for Publication

Title: Untitled
Author: John Jeong
Date: 2026-04-07
Category: Product

Branch: blog/test
File: apps/web/content/articles/test.mdx

---

Auto-generated PR from admin panel.

[netlify]

✅ Deploy Preview for char-cli-web canceled.

Name	Link
🔨 Latest commit	d81b515
🔍 Latest deploy log	https://app.netlify.com/projects/char-cli-web/deploys/69d6085bc12a2700096e7eb3

[netlify]

✅ Deploy Preview for hyprnote ready!

Name	Link
🔨 Latest commit	d81b515
🔍 Latest deploy log	https://app.netlify.com/projects/hyprnote/deploys/69d6085bc037fa000859bab7
😎 Deploy Preview	https://deploy-preview-4937--hyprnote.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[github-actions]

Grammar Check Results

Reviewed 1 article.

Untitled

📄 apps/web/content/articles/test.mdx

The article is well-written and clearly structured with helpful practical guidance. The main issues are: (1) multiple em dashes that need to be converted to regular dashes per the style rules, (2) two headings with unnecessary question marks, and (3) one spelling error ('rwo' instead of 'two'). These are all easily correctable issues that do not significantly impact the quality of the content. The technical information, examples, and workflow instructions are accurate and valuable.

Found 10 issues:

🔹 Punctuation Placement

Line 10

How to Use Obsidian to Take Meeting Notes?

Question mark is unnecessary in a heading that is a statement/title, not a direct question to the reader

📋 Suggested fix (click to expand)

# How to Use Obsidian to Take Meeting Notes

Line 33

How to Take Meeting Notes in Obsidian?

Question mark is unnecessary in a heading that is a statement/title, not a direct question to the reader

📋 Suggested fix (click to expand)

## How to Take Meeting Notes in Obsidian

🔸 Em Dashes

Line 21

• A way to get full meeting transcripts and AI summaries into your vault without any copy-pasting — and without your data leaving your machine

Em dash should be replaced with a regular dash per style rules

📋 Suggested fix (click to expand)

- A way to get full meeting transcripts and AI summaries into your vault without any copy-pasting - and without your data leaving your machine

Line 27

• Managing notes for meetings and one-on-ones effectively — The 22k-view thread where the backlinks-as-CRM approach first clicked for a lot of people.

Em dash should be replaced with a regular dash per style rules

📋 Suggested fix (click to expand)

- [Managing notes for meetings and one-on-ones effectively](https://forum.obsidian.md/t/managing-notes-for-meetings-and-one-on-ones-effectively/32049) - The 22k-view thread where the backlinks-as-CRM approach first clicked for a lot of people.

Line 28

• What to do with processed meeting notes? — Decisions vs. raw notes. When to keep, when to extract, when to let go.

Em dash should be replaced with a regular dash per style rules

📋 Suggested fix (click to expand)

- [What to do with processed meeting notes?](https://forum.obsidian.md/t/what-to-do-with-processed-meeting-notes/4480) - Decisions vs. raw notes. When to keep, when to extract, when to let go.

Line 29

• Need Help with Dataview for Meeting Notes — Pulling meeting references into person notes automatically.

Em dash should be replaced with a regular dash per style rules

📋 Suggested fix (click to expand)

- [Need Help with Dataview for Meeting Notes](https://forum.obsidian.md/t/need-help-with-obsidian-dataview-for-meeting-notes/90648) - Pulling meeting references into person notes automatically.

Line 30

• Automate Base Fill-in for Meeting Notes — Using Bases to auto-surface meetings in person notes.

Em dash should be replaced with a regular dash per style rules

📋 Suggested fix (click to expand)

- [Automate Base Fill-in for Meeting Notes](https://forum.obsidian.md/t/automate-base-fill-in-for-meeting-notes/103433) - Using Bases to auto-surface meetings in person notes.

Line 31

• From Daily Note, Create a New Note with a Template — One-click meeting note creation from your daily note using Meta Bind buttons.

Em dash should be replaced with a regular dash per style rules

📋 Suggested fix (click to expand)

- [From Daily Note, Create a New Note with a Template](https://forum.obsidian.md/t/from-daily-note-create-a-new-note-with-a-template/87160) - One-click meeting note creation from your daily note using Meta Bind buttons.

Line 75

That's a person note. The role and company properties are there so you can search for them later — [company:Acme] finds everyone at Acme. The ## Meeting history section is going to fill itself. We'll get to that.

Em dash should be replaced with a regular dash per style rules

📋 Suggested fix (click to expand)

That's a person note. The role and company properties are there so you can search for them later - [company:Acme] finds everyone at Acme. The ## Meeting history section is going to fill itself. We'll get to that.

🔤 Spelling

Line 276

You search task-todo:"Sarah Chen" and it shows rwo open items from last week.

Spelling error: 'rwo' should be 'two'

📋 Suggested fix (click to expand)

You search task-todo:"Sarah Chen" and it shows two open items from last week.

---

Powered by Claude Haiku 4.5

---

AI Slop Check Results

Reviewed 1 article for AI writing patterns.

Untitled

apps/web/content/articles/test.mdx

Score: 24/50 (NEEDS REVISION)

Dimension	Score
Directness	5/10
Rhythm	4/10
Trust	6/10
Authenticity	5/10
Density	4/10

This post is heavily written in LLM-generated patterns. The dominant issues are metronomic rhythm (especially staccato anaphoric lists like 'No X. No Y.' and 'You do X. You do Y.'), binary antithesis framing ('You need X. But if you chose Y, you need X that works like Y'), and conversational announcements that preview content before showing it ('Here's what X looks like...', 'Look at what just happened'). The technical content itself is sound, but the rhetoric is templated. Every section builds dramatic momentum through repetition and short parallel sentences, which signals AI composition. The Char integration section in particular reads like product marketing copy masquerading as technical explanation. The workflow narrative (lines 263-271) is pure LLM storytelling—scene-setting followed by metronomic staccato actions. Remove the rhetoric, tighten overexplanations, kill the announcements, and collapse repetitive sentence structures. The guide would be 30% shorter and read far more human if you removed the rhythm-building and spoke directly about the mechanism.

Found 36 issues (7 high, 15 medium, 14 low)

HIGH — Obvious AI Tell

Line 12 — antithesis-binary

You're already in Obsidian. You have a vault with projects, people notes, maybe a daily notes practice. What you don't have is meeting notes that connect to any of it. That's the specific problem this guide solves: building a meeting notes system inside an existing Obsidian PKB, where notes actually link to projects and people.

Antithesis/binary framing: 'What you don't have is X. That's the problem this guide solves' is textbook AI rhetorical move. Also includes 'that's the specific problem' which is significance inflation + testimonial framing ('this guide solves'). Rewrite states the actual purpose directly.

Suggested rewrite

This guide covers building a meeting notes system inside an existing Obsidian vault so notes link to projects and people.

Line 159 — conversational-announcement

Look at what just happened:

Pure conversational announcement. 'Look at what just happened' is throat-clearing that adds zero information. The bullets are the content; they don't need an introduction that tells the reader to pay attention.

Suggested rewrite

Delete this line entirely and begin the bullet list.

Line 245 — anaphoric-repetition

Everything up to this point relies on what you managed to type. In a 30-minute meeting, that's maybe 15% of what was said. The decision that was made at minute 22. The exact phrasing someone used when they pushed back on a deadline. The side comment that turns out to be the most important thing said all week. It's gone unless you happened to write it down.

Anaphoric repetition + staccato fragments for dramatic effect ('The decision... The exact phrasing... The side comment...'). This is a classic AI pattern: building rhetorical momentum through repetition. Also 'It's gone unless you happened to write it down' is conversational but redundant. Tighten to the actual problem.

Suggested rewrite

Everything above relies on manual notes. In a 30-minute meeting, you capture maybe 15% of what's said. Critical decisions and exact phrasing are lost without transcription.

Line 247 — antithesis-binary

You need transcription. And if you're the kind of person who chose Obsidian — you chose it because your files live on your machine, in a format you control, with no lock-in — you need transcription that works the same way.

Binary antithesis ('You need transcription. And if you're the kind of person who chose Obsidian — you chose it because...') + em-dash reframe + testimonial framing ('the kind of person who'). The repetition of 'you chose' and 'you need' is metronomic. Rewrite connects the ideas directly without the setup.

Suggested rewrite

You need transcription that keeps files on your machine and avoids vendor lock-in—the same principles that drove your choice of Obsidian.

Line 249 — anaphoric-repetition

Most meeting transcription tools don't. They store your data on their servers. They require monthly subscriptions. They join your call as a bot. They lock your transcripts in a proprietary format you can't move.

Staccato anaphoric repetition. 'Most meeting transcription tools don't. They [verb]. They [verb]. They [verb]. They [verb].' is textbook LLM rhythm-building through anaphora + short sentences. One complex sentence is more natural.

Suggested rewrite

Most tools store data on their servers, require subscriptions, insert a bot into calls, and lock transcripts in proprietary formats.

Line 277 — anaphoric-repetition

In the 1:1, you reference the specific thing she said in the sprint planning meeting. You know the exact phrasing because it's in the transcript. You're not guessing. You're not paraphrasing from memory. You're reading her words back from a file in your vault.

Metronomic rhythm + anaphoric negation. 'You're not guessing. You're not paraphrasing... You're reading...' builds rhythm through parallel negation followed by affirmation. This is a classic AI turn: setting up what you're NOT doing before revealing what you ARE doing. Collapse to the single actionable difference.

Suggested rewrite

In the 1:1, you reference the exact phrasing from the sprint planning transcript instead of paraphrasing from memory.

Line 279 — metronomic-rhythm

That's the system. Templates give you structure. Links connect everything. Backlinks surface history. Search finds anything. Char fills the gap between what you typed and what was actually said. Download Char now and try it on your next meeting.

Metronomic staccato list ('Templates give... Links connect... Backlinks surface... Search finds...') followed by a call-to-action pitch. The list is artificial rhythm-building. The final CTA 'Download Char now' is marketing/testimonial framing. Summarize the system concept and remove the pitch.

Suggested rewrite

That's the system: templates, links, backlinks, search, and transcription—with one source of truth in your vault.

MEDIUM — Likely AI Pattern

Line 16 — conversational-announcement

By the end of this guide you'll have:

Conversational announcement/preview. 'By the end of this guide you'll have' is throat-clearing that delays getting to the point. The list itself is the content; the announcement is unnecessary.

Suggested rewrite

You'll build:

Line 45 — staccato-fragments

That's it. You don't need subfolders by month or year yet. If you end up with hundreds of meeting notes and want to organize by date later, Obsidian's search doesn't care about folder depth, it searches everything. Start flat.

Staccato fragments + metronomic rhythm ('That's it.' as standalone sentence for emphasis + 'Start flat.' as punchy ending). The second part is repetitive explanation dressed up in fragments. Collapse into direct instruction.

Suggested rewrite

Start with a flat structure. Obsidian's search ignores folder depth, so you can reorganize later if needed.

Line 75 — conversational-announcement

That's a person note. The role and company properties are there so you can search for them later — [company:Acme] finds everyone at Acme. The ## Meeting history section is going to fill itself. We'll get to that.

Conversational tone + em-dash reveal. 'That's a person note. ... We'll get to that.' is announcement + preview. Em-dash before the example. Rewrite cuts the framing and states the mechanism directly.

Suggested rewrite

The role and company properties let you search by organization. The Meeting history section populates automatically via backlinks.

Line 115 — conversational-announcement

Here's what a meeting note looks like after a meeting. The key habit: write names and topics as [[wikilinks]].

Conversational announcement with colon preview. 'Here's what X looks like' + 'The key habit:' are preview patterns that delay showing the content. Restate by leading with the actionable instruction.

Suggested rewrite

Write names and topics as `[[wikilinks]]`. This example shows how it looks in practice:

Line 169 — metronomic-rhythm

Open Sarah Chen.md in People/. Click the backlinks icon in the right sidebar. Every meeting where you wrote [[Sarah Chen]] shows up with surrounding context. You can see what was discussed, what she decided, what she owes — all without maintaining anything.

Overexplanation + metronomic repetition. 'You can see what was discussed, what she decided, what she owes' repeats the same idea three times for emphasis. Em-dash before 'all without maintaining anything' is a reveal pattern. Tighten by removing the list and the false ending.

Suggested rewrite

Open Sarah Chen and click the backlinks icon. Every meeting mentioning her appears with context, fully automatic.

Line 171 — anaphoric-repetition

This is the approach from the Managing notes for meetings thread that resonated with the most people. No plugins. No queries. Just links and backlinks doing the work.

Metronomic staccato ('No plugins. No queries. Just links...') + anaphoric repetition (three-item list for rhythm). 'Resonated with the most people' is marketing framing. Tighten to the mechanism.

Suggested rewrite

This approach requires no plugins or queries—just backlinks.

Line 251 — marketing-framing

This is exactly the problem Char solves.

Testimonial framing + setup-driven statement. 'This is exactly the problem X solves' is marketing positioning language. Too explicit about the pitch.

Suggested rewrite

Delete or replace with: 'Char is built for this.'

Line 253 — conversational-announcement

Char is an open-source AI notepad for meetings. Here's what it does and why it fits this system:

Conversational announcement with colon preview. 'Here's what it does and why...' delays the content. Lead with the content or the specific claims.

Suggested rewrite

Char is an open-source AI notepad for meetings that solves these specific gaps:

Line 257 — metronomic-rhythm

You point the output folder at your vault. This is the key. Set Char's output folder to your Meetings/ folder (or a subfolder like Meetings/Transcripts/). When Char finishes processing a meeting, the transcript and summary appear in your vault. Obsidian indexes them instantly. They're searchable, linkable, part of your system. No export. No copy-paste.

Metronomic rhythm + staccato emphasis + overexplanation. 'This is the key' is significance inflation. 'No export. No copy-paste.' are staccato fragments for emphasis. The explanation is stretched across five sentences saying one thing. Collapse and remove filler.

Suggested rewrite

Point Char's output folder to your Meetings/ folder. Transcripts and summaries appear in your vault, automatically indexed and searchable—no export step.

Line 259 — staccato-fragments

It records via system audio. No bot joins your Zoom. No calendar permissions. Char captures what your computer hears, which means it works with Zoom, Teams, Google Meet, phone calls, and in-person conversations with a mic. Nobody in the meeting knows it's running.

Staccato anaphoric negation ('No bot joins... No calendar permissions...') followed by positive statements. This alternating pattern is metronomic. The list of platforms is unnecessary detail. 'Nobody knows it's running' is anthropomorphic positioning.

Suggested rewrite

Char records system audio without joining your call or requesting calendar access. It works with any platform and nobody in the meeting needs to know it's active.

Line 261 — metronomic-rhythm

It transcribes in real time and generates structured summaries. Char combines your notes with the full transcript and produces a summary using AI. The summary lands as a file on your computer.

Repetition + metronomic rhythm. Three sentences saying the same idea: it transcribes, it summarizes, it outputs a file. Collapse into one clear statement.

Suggested rewrite

Char transcribes in real time, combines your notes with the full transcript, and produces a summary on your machine.

Line 263 — metronomic-rhythm

You choose the AI. Use Char's managed cloud service if you want simplicity. Bring your own API keys from OpenAI, Deepgram, or Anthropic if your company already has them. Run models locally through Ollama or LM Studio if nothing leaves your machine. Your security team can audit the code. You're not trusting a black box with your meeting recordings.

Metronomic rhythm: staccato imperatives ('You choose... Use... Bring... Run... Your...') followed by a reassurance statement. The multiple options are listed as separate sentences for emphasis. Combine into one structure. 'You're not trusting a black box' is testimonial framing ('trust us').

Suggested rewrite

Choose your LLM: Char's cloud service, your own API keys (OpenAI, Deepgram, Anthropic), or local models (Ollama, LM Studio). You control where data flows and can audit the code.

Line 265 — metronomic-rhythm

There's no lock-in. Every file Char produces is a file on your computer. Stop using Char and every transcript is still there, in your vault, working. There's nothing to export because nothing was ever locked up.

Metronomic reassurance pattern. Four short sentences: negation ('no lock-in'), affirmation ('every file...'), hypothetical ('stop using...'), and conclusion ('there's nothing...'). This rhythm reads as reassurance-building, not explanation. Tighten to the fact.

Suggested rewrite

All files stay on your machine. Stop using Char and your transcripts remain in your vault—nothing was ever locked in a proprietary system.

Line 267 — antithesis-binary

If you use Obsidian, you already made this choice once: files on your machine, open format, your control. Char is the same choice applied to meeting recordings.

Binary antithesis / comparison framing. 'You already made this choice once... Char is the same choice...' positions Char as a continuation of a decision already made. Testimonial framing positioning. Rewrite as a direct statement without the 'you already chose' setup.

Suggested rewrite

Char applies the same principle you chose in Obsidian—files on your machine, open format, your control—to meeting recordings.

Line 274 — staccato-fragments

The meeting starts. You open Char. It starts recording system audio. You take notes in Obsidian: quick bullets, [[wikilinks]] for people and topics as they come up.

Staccato fragments for dramatic effect. 'The meeting starts. You open Char. It starts recording...' builds rhythm through short parallel sentences. Combine into flowing instruction.

Suggested rewrite

During the meeting, you open Char to record and take notes in Obsidian with [[wikilinks]] for people and topics.

LOW — Subtle but Suspicious

Line 10 — clickbait-heading

How to Use Obsidian to Take Meeting Notes?

Clickbait heading formula. Question mark + 'How to' creates a listicle/tutorial feel. Rephrased as a descriptive label without the marketing question.

Suggested rewrite

# Taking Meeting Notes in Obsidian

Line 12 — filler-phrase

where notes actually link to projects and people

The word 'actually' is filler/intensifier suggesting contradiction. It reads as 'despite what you might think, they actually link.' Delete it.

Suggested rewrite

where notes link to projects and people

Line 161 — em-dash-reframe

[[Sarah Chen]] appears in multiple places. Her person note now shows this meeting in backlinks — with the surrounding context of what she said, what she decided, and what she owes.

Repetition + em-dash reveal + overexplanation. The list 'what she said, what she decided, and what she owes' is unnecessary detail. The em-dash before it signals a reframe. Simplify to one sentence.

Suggested rewrite

[[Sarah Chen]] appears in multiple places. Her person note shows every meeting in backlinks, with context of what was discussed and what's outstanding.

Line 162 — metronomic-rhythm

[[PCI audit]] links to a topic note. If that note doesn't exist yet, that's fine. When the PCI audit becomes important enough to have its own page, every meeting that mentioned it is already connected.

Metronomic rhythm + antithesis. 'If that note doesn't exist yet, that's fine. When... every meeting... is already connected' sets up a reassurance + payoff rhythm that feels templated. Rewrite removes the reassurance and states the mechanism directly.

Suggested rewrite

[[PCI audit]] links to a topic note. If it doesn't exist yet, every meeting that mentions it is already connected when the topic becomes important enough to deserve its own page.

Line 163 — filler-phrase

The action items use - [ ] task syntax. Obsidian's search can find these directly, and you can narrow it to a specific person.

Overcomplicated explanation. Breaking down what is essentially one idea into two sentences with repetitive structure. Dense without clarity.

Suggested rewrite

Task syntax makes action items searchable and filterable by person.

Line 195 — marketing-framing

Your daily note becomes a launchpad. Start of the day, you see your calendar, and for each meeting you click a button and you're ready.

Marketing/testimonial framing. 'Your daily note becomes a launchpad' is positioning language. 'you're ready' is an aspirational closing. Simplify to the functional description.

Suggested rewrite

Your daily note becomes a launchpad for meeting creation.

Line 201 — significance-inflation

This is where the system pays off. Every query below has been tested in a live Obsidian vault.

Significance inflation + testimonial framing. 'This is where the system pays off' positions the following content as a payoff moment (marketing tone). 'Has been tested' adds false authority/verification language. Lead with the content.

Suggested rewrite

Here are the search queries:

Line 209 — metronomic-rhythm

Finds every incomplete task across your vault that mentions Sarah by name. Returns the exact task text with context.

Overexplanation with metronomic rhythm. Two sentences saying essentially the same thing: 'Finds... Returns...' breaks one idea into two. Collapse.

Suggested rewrite

Returns incomplete tasks mentioning Sarah with surrounding context.

Line 217 — metronomic-rhythm

Finds meeting notes where the tags property includes "payments." Returns only files inside the Meetings folder.

Same as line 201: metronomic 'Finds... Returns' repetition explaining one idea in two sentences. Unnecessary explanation of folder filtering.

Suggested rewrite

Returns meeting notes tagged with 'payments' only.

Line 225 — filler-phrase

Finds every mention of "PCI audit" across all meeting notes, with surrounding context so you can see what was said about it.

Overexplanation. 'So you can see what was said about it' is talking down to the reader. The word 'every' is significance inflation. Simplify.

Suggested rewrite

Returns every mention of 'PCI audit' in meeting notes with context.

Line 233 — em-dash-reframe

Uses regex on the date property to find all notes with a March 2026 date. Works for any month — change the pattern to match what you need.

Overcomplicated explanation of a simple pattern. Em-dash before a repetitive instruction. The first sentence explains what it does; the second repeats that it's flexible. State once.

Suggested rewrite

Use regex to find notes from any month by changing the pattern.

Line 241 — marketing-framing

Searches the company property across person notes. Useful when you're preparing for a client meeting and want to see all your contacts there.

Overexplanation + marketing positioning ('Useful when...' is setup-driven rather than fact-driven). Tighten to the mechanism and one example.

Suggested rewrite

Search by company across person notes—helpful for preparing client calls.

Line 273 — filler-phrase

You check your calendar and see three meetings today. From your daily note, you create a meeting note for the first one: 2026-04-07 Sprint Planning.

Unnecessary narrative setup. 'You check your calendar and see three meetings' is scene-setting that doesn't add information. The specific action starts with 'you create.' Remove the preamble.

Suggested rewrite

You create a meeting note from your daily note for the first meeting: 2026-04-07 Sprint Planning.

Line 276 — metronomic-rhythm

Before your 1:1 with Sarah that afternoon, you open [[Sarah Chen]] and glance at backlinks. You can see every meeting she's been in this month, what she committed to, what's still open. You search task-todo:"Sarah Chen" and it shows rwo open items from last week.

Metronomic repetition + overexplanation. 'You can see every meeting... what she committed to... what's still open' breaks one idea (viewing history) into multiple items. 'You search...' is a separate action tacked on. Also typo: 'rwo' should be 'two'. Combine the related actions.

Suggested rewrite

Before your 1:1 with Sarah, open her note and check backlinks for recent meetings and open items.

---

Powered by Claude Haiku 4.5 with stop-slop rules

[devin-ai-integration]

Blog Post Review: Humanizer + Stop-Slop

File: apps/web/content/articles/test.mdx

---

Humanizer Check (24 AI writing patterns)

Score: 37/50 (PASS)

Dimension	Score
Naturalness	7/10
Specificity	9/10
Voice	8/10
Rhythm	6/10
Conciseness	7/10

The post scores well on specificity (concrete examples, real forum links, exact UI steps) and voice (opinionated, direct). Main weaknesses are rhythm (repeated tailing negation patterns create choppy cadence) and em dash overuse.

HIGH severity

Line 21 — Em Dash Overuse (#14)

without any copy-pasting — and without your data leaving your machine

Suggested: without copy-pasting or uploading your data

Lines 249-250 — Negative Parallelisms (#9) + Tailing Negations

Most meeting transcription tools don't. They store your data on their servers. They require monthly subscriptions. They join your call as a bot. They lock your transcripts in a proprietary format you can't move.

Suggested: Most tools store data on their servers, require subscriptions, insert a bot into calls, and lock transcripts in proprietary formats.

Line 277 — Negative Parallelisms (#9)

You're not guessing. You're not paraphrasing from memory. You're reading her words back from a file in your vault.

Suggested: You have her exact words from the transcript in your vault.

Line 265 — Negative Parallelisms (#9)

No export. No copy-paste.

Suggested: You don't export or copy-paste anything.

Line 259 — Negative Parallelisms (#9)

No bot joins your Zoom. No calendar permissions.

Suggested: Char doesn't join your Zoom or require calendar access.

MEDIUM severity

Line 12 — Persuasive Authority Tropes (#27)

That's the specific problem this guide solves

Suggested: This guide shows how to build a meeting notes system inside an existing Obsidian vault.

Line 25 — Signposting (#28)

Worth reading on their own:

Suggested: Remove this line; the links speak for themselves.

Line 171 — AI Vocabulary (#7)

resonated with the most people

Suggested: This backlinks approach comes from the Managing notes thread and works without plugins.

Line 75 — Filler Phrases (#23)

That's a person note.

Minor performative simplicity fragment. Consider merging with the next sentence.

Line 75 — Signposting/Meta-commentary (#28)

The ## Meeting history section is going to fill itself. We'll get to that.

Suggested: The ## Meeting history section fills itself through backlinks.

LOW severity

Lines 27-31 — Em Dash Overuse (#14)
All five source list items use em dashes as separators. Replace with regular dashes or colons.

Line 45 — Filler (#23)

That's it.

Remove — the next sentence already explains the simplicity.

Line 267 — Rule of Three edge case (#10)

files on your machine, open format, your control

Borderline, but the three-element pattern is common enough in AI output to note.

Patterns NOT found (clean):

• editor is working #2 Undue notability/media emphasis
• migration to radix primitive #3 Superficial -ing analyses
• Add login page in Tauri #8 Copula avoidance (uses "is/are" naturally)
• Add calendar crate #11 Elegant variation / synonym cycling
• Add how-it-works in landing page #12 False ranges
• Server liveview and auth #15 Boldface overuse
• Initial i18n support #17 Title case in headings
• Add speaker capture audio stream #18 Emojis
• Rust backend server v1 #19 Curly quotes
• Rust server serving React frontend #20 Collaborative artifacts
• Add Clova grpc streaming STT #21 Knowledge-cutoff disclaimers
• Add S3 crate #22 Sycophantic tone
• General STT crate #24 Excessive hedging
• New DB crate using libsql for both admin and user #25 Generic positive conclusions
• Initial audio pipeline design #26 Hyphenated word pair overuse

---

Stop-Slop Check (phrases, structures, rhythm)

Score: 38/50 (PASS)

Dimension	Score
Directness	7/10
Rhythm	8/10
Trust	8/10
Authenticity	8/10
Density	7/10

The post is above the 35/50 threshold. Issues are concentrated in a few recurring patterns: "Here's what" openers, performative simplicity fragments ("That's it", "That's the system"), and meta-commentary about the guide's own structure.

Banned Phrases

Line	Text	Category	Suggested Fix
12	"That's the specific problem this guide solves"	Meta-commentary	Delete; next section already shows what's built
25	"Worth reading on their own:"	Light meta-commentary	Remove; let the links stand alone
115	"Here's what a meeting note looks like"	Throat-clearing ("Here's what")	"A meeting note after the meeting:"
159	"Look at what just happened:"	Meta-commentary + "Look" opener	Delete entirely; start with bullets
200	"This is where the system pays off."	Telling instead of showing	Delete; start with the queries
201	"Every query below has been tested in a live Obsidian vault."	Performative credibility	Delete; queries either work or they don't
253	"Here's what it does and why it fits this system:"	Throat-clearing ("Here's what")	Delete; continue directly
257	"This is the key."	Performative emphasis	Remove; the instruction following it is clear enough
251	"This is exactly the problem Char solves."	Telling instead of showing	"Char solves this." or delete

Structural Cliches

Line	Text	Category	Suggested Fix
12	"What you don't have is meeting notes... That's the specific problem this guide solves"	Binary contrast / antithesis	State the purpose directly
247	"You need transcription. And if you're the kind of person who chose Obsidian — you chose it because..."	Binary antithesis + em-dash reframe	"You need transcription that keeps files local and avoids lock-in, matching why you chose Obsidian."
45	"That's it."	Dramatic fragmentation / performative simplicity	Delete
75	"That's a person note."	Dramatic fragmentation	Merge with next sentence
279	"That's the system."	Dramatic fragmentation	Delete or rework
75	"We'll get to that."	Meta-commentary about structure	"The ## Meeting history section fills itself through backlinks."

Rhythm Patterns

Line	Text	Category	Suggested Fix
249-250	"They store... They require... They join... They lock..."	Anaphoric repetition / metronomic staccato	Collapse into one compound sentence
277	"You're not guessing. You're not paraphrasing... You're reading..."	Anaphoric negation pattern	"You reference the exact phrasing from the transcript instead of paraphrasing from memory."
279	"Templates give... Links connect... Backlinks surface... Search finds..."	Metronomic staccato list	Summarize as a single sentence
245-246	"The decision... The exact phrasing... The side comment..."	Anaphoric repetition / staccato fragments	Tighten to the actual problem in fewer sentences
186	"The decision that was made at minute 22"	Passive voice	"The decision someone made at minute 22"

---

Summary

Both checks pass (37/50 humanizer, 38/50 stop-slop). The tutorial content is strong, specific, and well-structured. The main revision targets are:

1. Kill "Here's what" openers (lines 115, 253) and "Look at" announcements (line 159)
2. Remove performative fragments ("That's it", "That's a person note", "That's the system")
3. Collapse anaphoric repetition — especially the "They [verb]" chain (line 249) and "You're not [X]" chain (line 277)
4. Cut meta-commentary about the guide's own structure (lines 12, 200, 201)
5. Replace em dashes throughout (lines 21, 27-31, 75, 247)