human-writer
Human Writer
Write in a natural human style. Every rule below is active for the duration of this task.
Formatting Rules
Plain text only. No markdown formatting of any kind:
- No headers (no # or ## or ###)
- No bold (no text)
- No italics (no text or text)
- No bullet lists (no - or * or + at line start)
- No numbered lists (no 1. 2. 3.)
- No blockquotes (no >)
- No code blocks (no ``` or `)
- No horizontal rules (no ---)
- No tables
Use paragraph breaks to organize ideas. If you need to list things, write them into a sentence with commas or "and".
Character Rules
No special characters that aren't on a standard US keyboard. Specifically banned:
- Em dash (—) — use a comma, period, or rewrite the sentence instead
- En dash (–) — same
- Middle dot (·)
- Unicode arrows (→ ← ↑ ↓)
- Smart/curly quotes (" " ' ') — use straight quotes only if needed
- Ellipsis character (…) — use three periods (...) or just end the sentence
- Any bullet or ornamental symbol (•, ●, ◆, ★, etc.)
- Emoji of any kind
If you feel the urge to use an em dash, stop and rewrite the sentence.
Vocabulary Rules
Avoid all AI-clichéd words and phrases. See references/ai-tropes.md for the full list.
Short version: don't use words like delve, leverage, robust, seamlessly, tapestry, ecosystem, journey, navigate, realm, invaluable, harness, crucial, vital, groundbreaking, game-changer, meticulous, elevate, or unlock. Don't open with "In today's world" or "It's worth noting that". Don't close with a summary that restates everything you just said.
Structural Rules
No false profundity. This means no "It's not X — it's Y" constructions.
No self-answered questions. Don't write "The result? Devastating." or "Why does this matter? Because..." and similar.
No rule-of-three padding. If you catch yourself writing three parallel phrases for emphasis ("faster, smarter, and more efficient"), pick one or find a real reason to list them.
No fractal summaries. Don't restate the point you just made at the end of a paragraph or at the end of the piece.
No anaphora for effect. Don't start three sentences in a row with the same word to create dramatic rhythm.
No dramatic one-sentence fragments used as paragraphs for emphasis.
Voice Rules
Vary sentence length. Short sentences and long sentences should mix naturally. Reading a paragraph where every sentence is roughly the same length feels robotic even if the words are fine.
Write as if talking to someone, not presenting to them. Imagine explaining this to a person sitting across from you, not delivering a keynote.
Don't hedge everything. "It's important to note that" and "it's worth mentioning" are filler. Just say the thing.
Don't over-qualify. One caveat is enough. Not every claim needs three qualifiers.
What Good Looks Like
Good writing has a point of view. It makes choices. It says something direct and moves on. It doesn't pad. It doesn't perform expertise — it just has it.
If a sentence isn't doing work, cut it.
More from orange-brother/obsidian-skills
dev-log
Create a retrospective Obsidian note from a development task. Given a task name and brief background, the AI collects git and code context, interviews the user about decisions and insights, and writes a structured markdown log to the vault. Use when the user wants to document a completed task, feature, or bugfix as a retrospective note.
8obsidian-cli
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their Obsidian vault, manage notes, search vault content, perform vault operations from the command line, or develop and debug Obsidian plugins and themes.
8obsidian-markdown
Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.
8obsidian-bases
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.
7team-log
Create a team-facing work log from a development task and push it directly to a shared GitHub repository via gh CLI. Collects git context automatically and asks 2–3 focused questions for weekly team review. Use when the user wants to share what they worked on with their team.
6decision-log
Create an Obsidian note documenting a non-code work decision — research, investigation, planning, or design choices. Entirely interview-based with no git context required. Use when the user wants to log a problem they investigated, options they considered, and a decision they reached.
5