Individual skill

data-table-design

Designs presentation tables that read correctly at a glance - numeric alignment, consistent precision, deliberate sort order, unit-labeled headers, and well-placed totals - and delivers a before/after redesign of the reader's table. Use when someone asks "make this table more readable", "how many decimals should I show", "should totals go at the top or bottom", "this report table is a mess", or is preparing tabular data for an exec deck or published report. Do NOT use for designing database tables, keys, and normalization - use database-schema instead; for narrative structure around the numbers - use data-story instead; for assembling the full multi-section document - use formatted-report-writer instead.

skills/data-table-design/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Data Table Design

A table is not a spreadsheet dump. Every formatting choice either helps or hinders the reader's ability to compare, rank, and interpret - and a misaligned or falsely precise table gets numbers misread in the meetings that matter. The output of this skill is a table a reader can extract the right conclusion from in under ten seconds.

## Operating procedure

### Step 1: Gather inputs

1. The table as it stands (or the raw data), and where it will live: slide, printed report, dashboard, or scrolling web page - the medium changes the density rules in Step 5.
2. The reader's single most likely question. Every subsequent decision serves it. If the owner cannot name the question, that is the first problem to fix.
3. The action the reader takes from the table. Columns that inform no comparison or action are candidates for deletion.
4. Units and the true precision of the data - what the collection method actually supports, not what the export prints.

### Step 2: Set alignment