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).

Ir para a instalação

Repositório: robert-chiniquy/dotfiles
Última atividade na origem: 26 de julho de 2026 às 21:20
Idioma detectado do SKILL.md: inglês
Estrelas: 3
Forks: 1

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

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

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

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

Ver todas deste repositório

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

Informações da origem

Opções de instalação

Revise os arquivos de origem

Mais deste repositório

Mais deste repositório

Technical Writing Voice

Technical Writing Voice