novel-reader
Skill0 starsChanged 6 months agoMITView on GitHub
Convert a generated chapter from markdown into a beautifully styled HTML page and open it in the browser for proper reading.
In this repository5 other files it gives its agents.
- novel-researchSkill
- novel-reviewSkill
- novel-setupSkill
- novel-wikiSkill
- novel-writeSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Read the chapter markdown.
- Very specific: line 26
Create ./output/html/ if it does not exist.
- Very specific: line 31
Use the open-gstack-browser skill to launch the browser, then navigate to the saved HTML file using its absolute path as a file:// URL.
- Distinctive: line 33
If the browser is already open, navigate directly.
- Very specific: line 44
If the rendering looks wrong (broken layout, missing styles), invoke design-html again with corrections.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Novel Reader
Convert a generated chapter from markdown into a beautifully styled HTML page and open it in the gstack browser for proper reading.
Step 1: Find chapter
Accept --chapter N or a file path. If no argument, use the most recent file in ./output/ by modification time.
Read the chapter markdown. Read ./wiki/project.md for the novel title and genre.
Step 2: Generate HTML
Invoke the design-html skill with this brief:
"Convert this chapter of [TITLE] (dark epic fantasy) into a standalone HTML reading page. Design: aged parchment background (#f5efe0), dark ink text (#1a1209), serif body font (Georgia or similar), generous line-height (1.9), max-width 680px centered. Chapter number as a large styled header. Drop-cap on the first letter of the first paragraph. Pull the most powerful single line from the chapter and display it as a styled pull quote mid-page. No navigation, no UI chrome — just the chapter as a beautiful reading experience. Fully self-contained HTML with all CSS inline."
Pass the full chapter text as the content to style.
Step 3: Save HTML
Create ./output/html/ if it does not exist.
Save the generated HTML to ./output/html/chapter-[N].html.
Step 4: Open in browser
Use the open-gstack-browser skill to launch the browser, then navigate to the saved HTML file using its absolute path as a file:// URL.
If the browser is already open, navigate directly.
Take a screenshot to confirm the page rendered correctly. Show it to the user.
Step 5: Report
Tell the user:
- Which chapter was rendered
- Where the HTML file was saved
- Confirm the browser is open and showing the chapter
If the rendering looks wrong (broken layout, missing styles), invoke design-html again with corrections.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

