mostlyright-data 0.19.2__tar.gz → 0.19.3__tar.gz

{mostlyright_data-0.19.2 → mostlyright_data-0.19.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mostlyright-data
-Version: 0.19.2
+Version: 0.19.3
 Summary: Mostly Right hosted CLI for reviewed datasets
 Project-URL: Homepage, https://mostlyright.md/
 Project-URL: Documentation, https://mostlyright.md/docs/guides/cli/

{mostlyright_data-0.19.2 → mostlyright_data-0.19.3}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "mostlyright-data"
-version = "0.19.2"
+version = "0.19.3"
 description = "Mostly Right hosted CLI for reviewed datasets"
 readme = "README.md"
 requires-python = ">=3.13"

{mostlyright_data-0.19.2 → mostlyright_data-0.19.3}/skills/mr-data-build/SKILL.md

@@ -637,8 +637,8 @@ seconds -- not a paragraph, and not a report. Use exactly this shape, in this or
 section out only when there is genuinely nothing to say (shown indented here; the document
 itself carries the headings at column one):
 
-    Two or three plain sentences: what the data is about, why it is worth a look, and what a
-    reader can see or do with it.
+    Two or three plain sentences: what the data is about, why it is worth a look, and what is
+    in it.
 
     ## Coverage
     - **Window:** the exact dates and the time zone.
@@ -664,12 +664,11 @@ That is six sections: the opening paragraph, and the five headings under it.
 
 Two or three short sentences, 120 to 280 characters, written for somebody who has never heard of
 the source, the venue or the format. Sentence one says what the data is about and what makes it
-worth a look, in at most 110 characters. The rest says, in the same plain words, what a reader can
-see or do with it.
+worth a look, in at most 110 characters. The rest says, in the same plain words, what is in it.
 
-1. No tickers, station codes, series codes, format names, publisher names, row definitions or row
-   counts here. Every one of those facts is in the sections below, which is where a reader who
-   wants it will look.
+1. No tickers, station codes, series codes, format names, publisher names, row definitions (the
+   sentence that begins `Each row is`) or row counts here. Every one of those facts is in the
+   sections below, which is where a reader who wants it will look.
 2. No Markdown: no bold, no links, no bullets, no code.
 3. A hook is an interesting fact stated plainly, never a pitch. Banned outright: comprehensive,
    rich, valuable, powerful, unlock, explore, dive into, perfect for, insights, "this dataset", a
@@ -679,6 +678,9 @@ see or do with it.
 5. The stranger test, before anything else is written: read sentence one alone under the title. If
    a curious non-specialist could not say what the data is about and would not want the next line,
    rewrite it.
+6. Plain and short. Every sentence under about twenty words, every sentence a fact: the venue, the
+   subject, the horizon, the cadence, the window. Nothing about what a reader might do with it: no
+   "so you can", "a way to", "ready to", "for seeing". Say what is there and stop.
 
 One airport weather table, the shape to avoid and the shape to write. To avoid:
 
@@ -688,17 +690,15 @@ One airport weather table, the shape to avoid and the shape to write. To avoid:
 
 To write:
 
-    Beijing's weather about every half hour since 2020, with each day's official high and low on
-    the same row. Temperature, wind, pressure and visibility as the airport recorded them, ready
-    to test a forecast against what actually happened.
+    Beijing airport weather since 2020, a report about every half hour, with the day's high and
+    low on each row. Temperature, wind, pressure and visibility as the airport recorded them.
 
 The station code, the report types, the publisher and the count all moved down to Coverage and to
 Source and rights, where a reader who wants them looks. "About every half hour" stays only because
-Coverage puts a month at 1,302 to 1,591 rows, which is one row every 27 to 33 minutes. "On the same
-row" stays because it says what a reader can see; the row definition rule 1 bans is the sentence
-that begins `Each row is`. Two ways to fail: the pitch (`Unlock real-time insights into how
-prediction markets price the weather!`) and the bare subject with no reason to care (`Beijing
-weather data.`).
+Coverage puts a month at 1,302 to 1,591 rows, which is one row every 27 to 33 minutes. Three ways
+to fail: the pitch (`Unlock real-time insights into how prediction markets price
+the weather!`), the promise (`ready to test a forecast against what actually happened`) and the
+bare subject with no reason to care (`Beijing weather data.`).
 
 **Body rules** (the five sections under the headings)
 1. Every sentence must stay true and complete when quoted alone, away from the page. Never
@@ -721,9 +721,9 @@ revision, not a style choice. Give `table.description` the grain and the window.
 **Check before writing.** Fix and re-check until every line passes:
 - title: at most 60 characters, contains the place, contains no colon, pipe or exclamation mark,
   no brand, no "dataset" or "data", no version number, no run date
-- opening paragraph: two or three sentences, 120 to 280 characters, first full stop before
-  character 110, no Markdown, no identifier, publisher name, row count or row definition, no
-  banned word
+- opening paragraph: two or three sentences, each under about twenty words, 120 to 280 characters,
+  first full stop before character 110, no Markdown, no identifier, publisher name, row count or
+  row definition, no banned word, no clause about what a reader might do
 - category: exactly one fixed ID saved and verified before recipe registration
 - topics: 3 to 8 descriptive tags, no duplicates, lowercase, at most 40 characters each
 - licence: an SPDX identifier the sources actually grant, or `--license` left off