Run any Skill in Manus with one click

book-author

Stars1

Forks0

UpdatedJuly 20, 2026 at 02:49

Render surviving research findings into a book chapter through the typed findings-to-artifact contract. An OPTIONAL channel pack (enable the `book` pack to use it), supporting the full genre range. Use this skill when the user wants to author a book, write a chapter from the research, turn the corpus into long-form, or build a manuscript. Triggers on 'write a book', 'author a chapter', 'book from research', 'turn this into a chapter', 'long-form from the corpus', 'manuscript'.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

modeled-information-format

modeled-information-format/research-harness-template

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Technical WritersArts, Design, Entertainment, Sports, and Media Occupations·SOC 27-3042

File Explorer

2 files

SKILL.md

readonly

name	book-author
description	Render surviving research findings into a book chapter through the typed findings-to-artifact contract. An OPTIONAL channel pack (enable the `book` pack to use it), supporting the full genre range. Use this skill when the user wants to author a book, write a chapter from the research, turn the corpus into long-form, or build a manuscript. Triggers on 'write a book', 'author a chapter', 'book from research', 'turn this into a chapter', 'long-form from the corpus', 'manuscript'.
version	0.4.3
argument-hint	[--topic <id>] [--genre <genre>] [--chapter <n>] [--out <path.md>]
allowed-tools	Read, Bash, Edit, Glob, Grep

book-author — research → book chapter

Book is an optional channel pack (SPEC §6d): enable the bundled book channel pack to author long-form — it is not an always-on core output (blog is the first-class published channel). It renders a chapter from the surviving findings through the same typed findings→artifact contract (schemas/artifact.schema.json) the blog output uses — so a research corpus drives both a post and a book from one synthesis, and the citation gates run uniformly across both.

The book pipeline supports its full genre range (technical / children's / fiction / history / non-fiction) via the genre passed to the synthesizer, and the chapter carries front/endnote matter. The citation-leak gate is the manuscript invariant: a chapter must read as if written from public primary sources alone.

Pipeline

Resolve the finding set for the chapter — the topic's surviving findings (verdict ≠ falsified).

Synthesize the artifact (the report-synthesizer substrate):

scripts/synthesize-artifact.sh reports/<topic>/findings <genre> reports/<topic>/artifact.json

Render the chapter from the same artifact the blog uses. Every output lives under reports/<topic>/, never a top-level book/ directory — the book's own chapters/front-matter/appendices structure nests one level deeper instead:
```
scripts/render-artifact.sh reports/<topic>/artifact.json book reports/<topic>/book/chapters/<n>.md
```
<n> is a numeric chapter index for a single manuscript authored this way, chapter by chapter. The research-deliverables.js multi-genre routing workflow drives this same render step differently: since a numeric index doesn't map onto "N independent genre-shaped chapters" rendered in one run, it uses the genre string itself as the chapter slug instead (reports/<topic>/book/chapters/<genre>.md) — a deliberate override for that caller, not a different convention this skill itself follows.
Gate the manuscript. The bundled check-citation-leak.sh hook guards reports/*/book/chapters/*.md (and the matching appendices//front-matter/ paths): no finding ids, urn:mif: ids, or reports/<slug>/ paths may appear. Re-author any flagged passage from the primary source.

Non-negotiables

Never include a falsified or quarantined finding — the synthesizer filters them.
Manuscript prose carries no internal-research references. The chapter cites only the public sources in its endnotes.
The chapter is a projection of the artifact; change the findings or synthesis, not the rendered Markdown in place.
book is a MIF-exempt channel (declared mifExempt: true in harness.config.json outputs[]): its public prose is orthogonal to MIF, so the MIF Level-3 source of truth lives in the generic report channel (reports/<topic>/<slug>.md), not the chapter. The MIF I/O conformance gate skips and logs the chapter; it does not require an L3 projection of it.

More from this repository

same repository

continuous-monitor

modeled-information-format/research-harness-template

Unattended, scheduled monitoring of external sources (arXiv, OpenAlex, Crossref, Semantic Scholar, PubMed, bioRxiv/medRxiv, GDELT, Hacker News) for operator-selected current-events DOMAINS (monitoringDomains[], weighted, momentum-ranked, digest output) or for a research topic (the topic-bound special case), gated end to end through a mandatory human Editorial Gate before anything publishes. An OPTIONAL methodology pack (enable the `continuous-monitor` pack AND configure a domain or a topic's continuousMonitoring block). Use this skill when the user wants to enable, inspect, or manually run continuous monitoring for a domain or topic, review a run's digest or candidate recommendations, or check the Continuity Log for a skipped/failed source. Triggers on 'continuous monitoring', 'monitor this domain', 'monitor this topic', 'monitoring digest', 'schedule research monitoring', 'check for new sources', 'run the monitoring pipeline', 'review monitoring recommendations'.

2026-07-213

publish-blog

modeled-information-format/research-harness-template

Render surviving research findings into a publishable blog post through the typed findings-to-artifact contract. A first-class harness output (not a pack). Use this skill when the user wants to turn research into a blog post, publish findings, draft an article from the corpus, or write up what the research found. Triggers on 'publish blog', 'blog post from research', 'write up these findings', 'draft an article', 'turn this into a post'.

2026-07-203

ontology-manager

modeled-information-format/research-harness-template

Create, validate, inspect, and convert MIF ontology definition files. Use when the user asks to: create a new ontology, scaffold an ontology, validate an ontology YAML, inspect ontology contents (entities, traits, relationships, namespaces, discovery patterns), convert between YAML and JSON formats, convert to JSON-LD, or get guidance on MIF ontology structure. Triggers on: "ontology", "create ontology", "validate ontology", "inspect ontology", "convert ontology", "ontology schema", "entity types", "traits", "discovery patterns", "namespace hierarchy".

2026-07-143

diataxis-docs

modeled-information-format/research-harness-template

Render a research topic's entire surviving findings corpus into a COMPLETE Diátaxis documentation set — a reference page per finding, a per-dimension explanation, how-to, and guided tutorial, plus landing/index pages — every page carrying MIF Level-1 frontmatter and a diataxis_type marker. An OPTIONAL channel pack (enable the `diataxis` pack). Use this skill when the user wants documentation for a research topic, a full docs set from the findings, or to publish the corpus as Diátaxis docs. Triggers on 'diataxis docs', 'documentation channel', 'render docs from research', 'document the findings', 'reference and explanation docs', 'generate the docs site'.

2026-07-143

ai-spec

modeled-information-format/research-harness-template

Render a topic's surviving findings into an AI-ready, agent-executable architecture spec. A genre-shaping of the artifact -> Markdown pipeline (not a new mechanism) — finding_refs become grounded evidence sections, the goal's completion checks become EARS acceptance criteria, and the artifact sections become the document structure. Use to turn research into a buildable spec a downstream coding agent executes.

2026-07-123

modeled-information-format/research-harness-template

Search the MIF research index — find findings by free-text query or by structured filters over the index fields (dimension, tags, namespace, verdict). Use this skill when the user wants to find research findings, look up what is known about a subject, query findings, or asks 'what do I have on X', 'find findings about Y', 'search research for Z', 'what research', 'what findings'. Reads the projected index, not raw tag files.

2026-07-053

name	book-author
description	Render surviving research findings into a book chapter through the typed findings-to-artifact contract. An OPTIONAL channel pack (enable the `book` pack to use it), supporting the full genre range. Use this skill when the user wants to author a book, write a chapter from the research, turn the corpus into long-form, or build a manuscript. Triggers on 'write a book', 'author a chapter', 'book from research', 'turn this into a chapter', 'long-form from the corpus', 'manuscript'.
version	0.4.3
argument-hint	[--topic <id>] [--genre <genre>] [--chapter <n>] [--out <path.md>]
allowed-tools	Read, Bash, Edit, Glob, Grep

book-author — research → book chapter

Pipeline

Resolve the finding set for the chapter — the topic's surviving findings (verdict ≠ falsified).

Synthesize the artifact (the report-synthesizer substrate):

scripts/synthesize-artifact.sh reports/<topic>/findings <genre> reports/<topic>/artifact.json

Render the chapter from the same artifact the blog uses. Every output lives under reports/<topic>/, never a top-level book/ directory — the book's own chapters/front-matter/appendices structure nests one level deeper instead:
```
scripts/render-artifact.sh reports/<topic>/artifact.json book reports/<topic>/book/chapters/<n>.md
```
<n> is a numeric chapter index for a single manuscript authored this way, chapter by chapter. The research-deliverables.js multi-genre routing workflow drives this same render step differently: since a numeric index doesn't map onto "N independent genre-shaped chapters" rendered in one run, it uses the genre string itself as the chapter slug instead (reports/<topic>/book/chapters/<genre>.md) — a deliberate override for that caller, not a different convention this skill itself follows.
Gate the manuscript. The bundled check-citation-leak.sh hook guards reports/*/book/chapters/*.md (and the matching appendices//front-matter/ paths): no finding ids, urn:mif: ids, or reports/<slug>/ paths may appear. Re-author any flagged passage from the primary source.

Non-negotiables

Never include a falsified or quarantined finding — the synthesizer filters them.
Manuscript prose carries no internal-research references. The chapter cites only the public sources in its endnotes.
The chapter is a projection of the artifact; change the findings or synthesis, not the rendered Markdown in place.
book is a MIF-exempt channel (declared mifExempt: true in harness.config.json outputs[]): its public prose is orthogonal to MIF, so the MIF Level-3 source of truth lives in the generic report channel (reports/<topic>/<slug>.md), not the chapter. The MIF I/O conformance gate skips and logs the chapter; it does not require an L3 projection of it.