technical-writing-voice

Long-form technical writing voice for blog posts, deep dives, architecture explanations, and conference talks. Use when writing technical articles, blog posts, or any long-form content for external audiences. Distinct from dry-witted-engineering (terse work comms) and casual-slack-tone (chat).

Jump to install

Repository: robert-chiniquy/dotfiles
Last source activity: July 26, 2026 at 21:20
Detected SKILL.md language: English
Stars: 3
Forks: 1

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/robert-chiniquy/dotfiles --skill technical-writing-voice

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

find-delegation-pebbles

Sweep open issue trackers, TODOs, active branches, and source evidence to find narrowly scoped, independent, verifiable tasks suitable for remote agents or parallel delegation. Use when asked to find pebbles, small delegatable work, fire-and-forget candidates, backlog slices, ready items, or pool/task combinations.

2026-07-29

readiness-scorecard

Write a scorecard — a dark, skimmable one-screen readout of the current situation in the user's work, rendered as a terminal (TUI) artifact by the `scorecard` binary from a structured markdown file. Use ONLY when the user explicitly asks for a scorecard (or a "readiness card" / "go/no-go card" / "coverage snapshot card"). A plain "status", "status?", or other status/situation question gets a prose answer, never this skill. NOT a web page — output is the dark TUI. Preserves older scorecards by datestamp. Triggers on: scorecard, readiness card, go/no-go card, coverage snapshot card.

2026-07-27

bar-chart-comparison

Present comparisons as narrow ASCII bar charts in the terminal. Use when user asks to compare items, metrics, counts, or coverage between things.

2026-07-26

View all from this repository

name	technical-writing-voice
description	Long-form technical writing voice for blog posts, deep dives, architecture explanations, and conference talks. Use when writing technical articles, blog posts, or any long-form content for external audiences. Distinct from dry-witted-engineering (terse work comms) and casual-slack-tone (chat).

Technical Writing Voice

Style guide for long-form technical content: blog posts, deep dives, architecture explanations, conference talks. The voice of someone who reads textbooks on weekends and can't believe this stuff actually works.

Distinct from dry-witted-engineering (terse work communication) and casual-slack-tone (chat). This is the explaining voice -- when the audience is broader, the subject is deep, and the goal is to bring people along.

For full reference, see the body of this skill. Key principles: relentless optimism, learner-who-builds identity, enthusiasm for the domain, honest about scope. Discovery framing ("It turns out that..."), understatement for emphasis, direct address, casual authority. Never academic, never marketing, never tutorial, never lecture, never sententious.

technical-writing-voice

Source facts

Install options

Review the source files

More from this repository

More from this repository

Technical Writing Voice

Technical Writing Voice