Public-Domain Mystery Books: 50 With Checked Links

Data catalog, not an instruction skill: 50 romance novels from Project Gutenberg, each with title, author, Gutenberg number, download count and an EPUB address that answered on 2026-10-28. Rights are the United States only. Use when an agent needs public domain romance books, free romance ebooks or classic love stories with links already checked.

Data catalog, not an instruction skill: 50 science fiction books from Project Gutenberg, each with title, author, Gutenberg number, download count and an EPUB address that answered on 2026-10-28. Rights are the United States only. Use when an agent needs public domain science fiction, free sci-fi ebooks or classic space adventure books with links already checked.

Checks ONE Google Analytics 4 tracking plan (events, their parameters, and the custom dimensions to register with their scope) against the published collection limits and naming rules, and lists only the breaches, one line each with a fixed code, the item, the rule it breaks and the fix - or exactly No findings. It catches an event or parameter name longer than allowed, more parameters on one event than GA4 collects, a reserved event name or a reserved parameter name or prefix, a name that breaks the format rules, and a custom dimension whose values are nearly unique. It leaves out names that sit exactly on a limit and events that use exactly the allowed number of parameters. Use before a plan goes to developers or to Google Tag Manager, to audit a plan that someone else wrote, or to find out why an event or a parameter never shows up in reports.

Checks the written readout of ONE A/B test (a paragraph, an email, a table or a slide transcript) for the five statistical mistakes that turn a no-effect test into a "win", and lists only those, one line each with a fixed code, the place, the evidence with the arithmetic and the fix - or exactly No findings. It catches stopping the moment a result looks significant, many metrics or variants judged without correction, a split of users that differs from the planned split by more than chance allows (the sample ratio check, calculated step by step), a sample too small for the effect the team wants to detect, and a relative lift reported without the absolute numbers behind it. It leaves out the safe look-alikes, such as a pre-registered single primary metric, guardrail metrics that only monitor, and a split of 50.2 to 49.8 on a small sample. Use before a test result is shipped, when an analyst or an agent writes a readout, or to review a result someone else announced.

Describes a table you were given (pasted Markdown, CSV, TSV or spreadsheet cells) in a short paragraph that uses only figures the table itself prints. Every number is copied as written with its unit, currency and qualifier. Nothing is added up, averaged, rounded, turned into a percent or a ratio, or extended into a trend, a cause or a forecast. A blank or n/a cell is reported as not given, never as zero. A total the table prints is quoted, not checked. Use when asked to describe a table, summarize a table, explain what a data table shows, write a caption or a sentence for a table, or put the rows of a report table into words without inventing a single number.

Repairs broken YAML and Markdown front matter so a program can parse it, without changing any value's text or type, and answers with the YAML only, no code fence. Fixes tabs used as indentation, indentation that fits no parent, a missing closing quote or bracket, values that need quotes (a colon inside, a leading star or at sign), and output cut off in the middle, where the cut value is kept as cut and never completed. Yes, no, on, off and NO stay strings, 1,250 stays a string, 1.10 and 01234 stay as written. Duplicate keys, input that is not YAML, and input with two readings get a fixed one-line answer instead of a guess. Use when a tool, an API or another model returned YAML or front matter that does not parse, or when asked to fix, clean up or close invalid or truncated YAML.