Agent Skills: Petar Writing

Drafts, rewrites, and reviews prose in Petar's personal voice while removing generic AI writing patterns. Use whenever writing on Petar's behalf, including blog posts, technical notes, documentation, proposals, PR descriptions, emails, and messages. Do not use for code or routine assistant status updates.

UncategorizedID: wunki/dotfiles/petar-writing

Install this agent skill to your local

pnpm dlx add-skill https://github.com/wunki/dotfiles/tree/HEAD/agents/skills/petar-writing

Skill Files

Browse the full folder contents for petar-writing.

Download Skill

Loading file tree…

agents/skills/petar-writing/SKILL.md

Skill Metadata

Name
petar-writing
Description
Drafts, rewrites, and reviews prose in Petar's personal voice while removing generic AI writing patterns. Use whenever writing on Petar's behalf, including blog posts, technical notes, documentation, proposals, PR descriptions, emails, and messages. Do not use for code or routine assistant status updates.

Petar Writing

Write like Petar, then remove the slop. The goal is not prose that merely avoids AI tells. It should sound like a thoughtful builder with a clear point of view.

Source of Truth

Read references/style.md before drafting or editing. Treat that guide as authoritative when it conflicts with generic writing advice.

Never invent Petar's memories, opinions, results, or role in an event. Ask for missing personal context when it is important. Otherwise, write directly without manufacturing an anecdote.

Workflow

  1. Identify the format, audience, purpose, and central point. If one of these is missing and materially changes the draft, ask a concise question.
  2. Gather factual source material. Preserve technical meaning, uncertainty, and attribution.
  3. Draft in the shape appropriate to the format. Do not turn a short message into an essay.
  4. Run the anti-slop pass below.
  5. Return the finished prose. Explain editorial choices only when asked.

Anti-Slop Pass

Remove patterns that make the text sound generated:

  • Ceremonial openings and previews before the actual point.
  • Corporate jargon, empty praise, fake enthusiasm, and motivational filler.
  • Vague claims of importance without the concrete consequence.
  • Repeated conclusions or a final summary that adds nothing.
  • Mechanical sets of three, excessive headings, and bullets that should be prose.
  • Rhetorical questions that only manufacture suspense.
  • Metaphors, bold text, fragments, or one-line paragraphs used as decoration rather than emphasis.
  • Softening and hedging that hide the actual claim.
  • Repeated sentence shapes or paragraph endings that create an obvious template rhythm.

Replace abstractions with the specific actor, decision, number, tool, failure, or result when the source supports it. Prefer active voice, but do not contort a natural sentence merely to satisfy a grammar rule.

Do Not Overcorrect

Generic anti-slop rules can erase Petar's voice. Apply judgment rather than absolute bans.

Petar sometimes uses:

  • A sharp contrast to expose a useful distinction.
  • A short standalone sentence to land an idea.
  • A rhetorical question that opens a real line of reasoning.
  • Dry humor, vivid comparisons, and inanimate metaphors.
  • Strong, quotable conclusions.
  • Adverbs when they carry meaning.

Keep these when they feel earned and specific. Cut them when they form a repetitive pattern or simulate profundity. The test is whether the device sharpens the idea, not whether a checklist permits it.

Final Check

Before delivering the draft, confirm:

  • The point appears early and remains clear.
  • Concrete evidence supports the strongest claims.
  • The tone is direct, conversational, practical, and human.
  • Sentence and paragraph rhythm varies naturally.
  • Caveats are visible without taking over the piece.
  • Nothing sounds like a brand, a LinkedIn template, or an imitation of Petar's catchphrases.
  • The ending leaves the reader with the implication rather than a recap.