# Inteligir Writing

> How an inteligir note should read — leading with the answer, choosing structure that fits the information, and knowing when to stop.

- Skill: `kyh/inteligir-writing` (Agent Skill)
- Install (CLI): `npx skillmds@latest add kyh/inteligir-writing`
- Raw SKILL.md: https://api.skillmd.com/api/skills/kyh/inteligir-writing/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: kyh (https://skillmd.com/u/kyh)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/kyh/inteligir-writing

---


# inteligir Writing

Write for someone who skims first and reads only if the skim earns it. This
skill owns structure and prose; `inteligir-notes` owns syntax.

## Lead With The Answer

After the H1, the first paragraph states the conclusion, decision, or state —
standing on its own, needing nothing from later sections.

- Conclusions before evidence. Evidence before caveats.
- Sections ordered most to least important, not chronologically.
- Paragraphs of two to four sentences.
- `##` for sections, `###`/`####` beneath. Never a second `#`.

Detail is not the enemy; front-loaded detail is. Move derivations down, do not
delete them.

## Match The Shape To The Information

| The information is                                | Write it as                 |
| ------------------------------------------------- | --------------------------- |
| One connected idea                                | A paragraph                 |
| Related points or ordered steps                   | A list                      |
| Attributes compared across items                  | A table                     |
| Peer views read one at a time                     | Tabs                        |
| Context, caution, or priority worth setting apart | A callout                   |
| A numeric trend                                   | A chart                     |
| A question that needs an answer                   | A comment on the exact text |

Two rules that save the most rework: keep block content out of table cells (a
cell holds inline content only), and give every fact exactly one home — a
requirement restated in a table, a checklist, and a callout will drift into three
different requirements.

## Shapes That Work

- **Decision** — recommendation, options, tradeoffs, next step.
- **Plan** — goal, steps or checklist, owners and state, open questions.
- **Research** — findings first, then evidence by theme, then sources.
- **Reference** — one-line definition, rules, examples.
- **Status** — where it stands, what changed, what happens next.

## Comment, Or Just Fix It

Comment when a person has to decide something, approve something, or answer a
question only they can answer — anchored to the exact evidence.

Fix directly: wording, ordering, duplication, a heading that buries its section.
A comment saying "this is unclear" on text you could have clarified is work
handed back to the reader.

## Before You Finish

- The first paragraph after the H1 stands alone and says the thing.
- Headings plus their opening lines tell the story to someone who reads nothing
  else.
- Each block matches the shape of what it holds.
- Every fact has one home.
- Properties live in frontmatter, not restated as bold labels in the body.