mostlyright-data 0.19.0__tar.gz → 0.19.1__tar.gz

{mostlyright_data-0.19.0 → mostlyright_data-0.19.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mostlyright-data
-Version: 0.19.0
+Version: 0.19.1
 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.0 → mostlyright_data-0.19.1}/pyproject.toml

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

{mostlyright_data-0.19.0 → mostlyright_data-0.19.1}/skills/mr-data-build/SKILL.md

@@ -596,7 +596,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 plain sentences: what each row is, where it comes from, and the period it covers.
+    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.
 
     ## Coverage
     - **Window:** the exact dates and the time zone.
@@ -618,17 +619,45 @@ itself carries the headings at column one):
 
 That is six sections: the opening paragraph, and the five headings under it.
 
-**Opening paragraph rules** (everything before the first `##` heading)
-1. Two sentences, 150 to 240 characters together. The first sentence ends before character 200
-   and is complete on its own.
-2. Sentence one says what each row is, for where, over what window, from which publisher:
-   `Each row is one hourly METAR observation at Prague Václav Havel Airport (LKPR), January 2000
-   to August 2026, from the Iowa Environmental Mesonet ASOS archive.`
-3. Sentence two gives the size and the measured quantities, as numbers and nouns:
-   `43,812 rows of temperature, dew point, wind, pressure and visibility.`
-4. Full names on first use with the abbreviation in parentheses once. Never "this dataset",
-   "we", "it", "here".
-5. No Markdown in the opening paragraph: no bold, no links, no bullets, no code.
+**Opening paragraph** (everything before the first `##` heading)
+
+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.
+
+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.
+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
+   rhetorical question, an exclamation mark.
+4. Every number in it must be one the run established. "About every half hour" and "thousands of
+   markets" are claims, and a claim that is not on the run does not go here.
+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.
+
+One airport weather table, the shape to avoid and the shape to write. To avoid:
+
+    Each row is one METAR or SPECI weather report from Beijing (ZBAA), since January 2020, via
+    Iowa Environmental Mesonet. 117,876 reports of temperature, wind, pressure, visibility with
+    the day's highest and lowest reading.
+
+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.
+
+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.`).
 
 **Body rules** (the five sections under the headings)
 1. Every sentence must stay true and complete when quoted alone, away from the page. Never
@@ -644,14 +673,16 @@ That is six sections: the opening paragraph, and the five headings under it.
 Rules that keep it readable: short sentences; no sentence over about twenty-five words; bullets
 rather than comma lists; no tables, no code blocks, no links to internal tools, no headings beyond
 the ones above. Spell out the names a reader would search for -- the place, the identifiers in
-every common form, the programme and the publisher -- once each, in the opening sentences and
-never as a keyword list. A one-line description is a defect to fix in the revision, not a style
-choice. Give `table.description` the grain and the window.
+every common form, the programme and the publisher -- once each, under Coverage and under
+Source and rights, and never as a keyword list. A one-line description is a defect to fix in the
+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: 150 to 240 characters, first full stop before character 200, no Markdown
+- 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
 - 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