Novel Lite logo

Novel Lite

Community
alfredxw
novel-lite

Fast continuation, exploratory drafts, and low-latency prose generation performed directly by the main Agent without review or revision subprocesses.

Overview

Publisheralfredxw
Repositorydenova
Skill namenovel-lite
Stars
906
Forks
143
Bundled files
Instructions only
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by alfredxw on GitHub. Read the source before you install it.

Installation

Install the Novel Lite AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/alfredxw/denova/tree/master/skills/novel-lite
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/alfredxw/denova.git /tmp/denova
mkdir -p .claude/skills
cp -r /tmp/denova/skills/novel-lite .claude/skills/novel-lite
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Novel Lite in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Novel Lite on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Novel Lite is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

novel-lite

Use this Skill for fast prose generation by the Writing Agent.

Determine the writing scope

  • Infer the scope from the user's actual request, such as continuing a passage, writing a scene, one chapter, three chapters, a story arc, or a custom target.
  • Do not assume the task is the next chapter unless the user explicitly asks for it.
  • There is no writing_scope field. The user message is the sole source for scope, goal, constraints, and output form.
  • When the user requests multiple chapters, do only a lightweight internal breakdown: determine the overall direction and chapter boundaries, then write at the requested scale.

Workflow

main Agent -> final output

Tool requirements

  • When continuity matters, first use read for the relevant workspace files, such as CREATOR.md, setting/outline.md, setting/progress.md, setting/character-states.md, the current chapter-group plan, and recent chapters. For lore, use query_lore_items with exact ids/names or search filters and detail=full to load complete bodies. Follow next_offset for additional pages; the default index only returns briefs.
  • If the user asks only for a passage, exploratory draft, or example in chat, output the prose directly and do not write workspace files.
  • When the user asks to create or update workspace prose, use write for a new file or complete rewrite and edit for localized replacement. old_string must match the current file exactly and uniquely and must not contain line-number prefixes returned by read.
  • Inspect every write or edit result. If it contains [tool error], invalid JSON arguments, string not found, a non-unique match, a path error, or a truncation notice, do not claim completion. Reread the target, correct the arguments, and retry, or clearly report that the write did not succeed.
  • After user-visible file changes, use read to verify key excerpts from the final file. If verification is impossible, say so in the final response.
  • After writing a complete chapter or materially changing its plot, finish the prose self-review and final revision, then update setting/progress.md and setting/character-states.md in the same turn. Chapter status in the UI does not affect synchronization. Pure typo, punctuation, or wording edits that do not change narrative facts need no state update.
  • Treat setting/progress.md only as a summary. Determine the next chapter from actual chapter paths and non-empty prose, and correct progress in the same turn when they conflict.

Rules

  • The main Agent produces the final result directly.
  • Do not start reviewer, fixer, task, General SubAgent, or configured subagent workflows.
  • A lightweight internal check for continuity, user requirements, and obvious prose issues is allowed, but do not expose the review process.
  • Preserve user control. Do not over-plan, over-explain, or turn the requested draft into a different story.
  • Use workspace context, selected text, lore references, and style rules only when relevant to this turn's writing scope.

Output

  • Return the creative result the user requested directly.
  • Add a brief explanation only when the user asks for one or an important constraint cannot be satisfied.

Frequently asked questions

What does the Novel Lite AI skill do?

Fast continuation, exploratory drafts, and low-latency prose generation performed directly by the main Agent without review or revision subprocesses.

Why use Novel Lite on TypingMind?

Because you install it once and use it with any model. Novel Lite is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Novel Lite in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/alfredxw/denova/tree/master/skills/novel-lite. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Novel Lite?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Novel Lite?

As many as you like. As long as a model supports skills, you can use Novel Lite with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Novel Lite AI skill free?

Yes. It is published on GitHub by alfredxw under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇