Files
skills/harry-writing-style-skill
2026-06-03 21:28:18 +01:00
..
2026-06-03 21:28:18 +01:00
2026-06-03 21:28:18 +01:00
2026-06-03 21:28:18 +01:00
2026-06-03 21:28:18 +01:00
2026-06-03 21:28:18 +01:00
2026-06-03 21:28:18 +01:00
2026-06-03 21:28:18 +01:00
2026-06-03 21:28:18 +01:00
2026-06-03 21:28:18 +01:00
2026-06-03 21:28:18 +01:00
2026-06-03 21:28:18 +01:00

Harry Writing Style Skill

A reusable style skill built from local opencode, Claude Code, and Codex user-authored messages.

It is intentionally conservative. It should edit Harry's drafts with minimal disruption and avoid turning them into polished assistant prose.

Privacy note: examples are redacted and shortened. Long pasted code/log blocks, URLs, local paths, emails, and secret-shaped strings were removed or replaced.

Modes:

  • technical-review: plans, architecture, implementation criticism.
  • spec-direction: agent instructions and implementation asks.
  • casual-opinion: short blunt takes.
  • debugging-help: errors, commands, broken behaviour.
  • formal-public: blog posts, public arguments, Popdog-style roundups.

Most important file after SKILL.md: PRESERVE_DRAFT.md. The safest behaviour is usually a minimal edit, not a rewrite.

Useful operational files:

  • SOURCE_PRIORITY.md: which examples to trust for each task.
  • MODE_EVALUATION.md: mode-specific rejection checks.
  • EVAL_PROMPT.md: reusable prompt for scoring drafts/outputs.

Example policy:

  • Prefer curated examples over the held-out/generated test set.
  • The generated extraction was useful for coverage, but final examples should be manually selected.
  • If a mode has weak evidence, say so instead of pretending.
  • Source priority: use opencode/Codex/Claude examples for agent instructions, Popdog roundups for company updates, and hjb.dev posts for public/longform prose.