Style Review logo

Style Review

Community
tobyilee
style-review

Review chapter drafts against the active genre profile's style checklist (defaults to tech-book = Toby's voice) — detects voice deviations and applies or proposes concrete before/after rewrites. Use when reviewing a chapter for style consistency, enforcing the genre voice, or polishing prose.

Overview

Publishertobyilee
Repositorybook-writer
Skill namestyle-review
Stars
85
Forks
20
Bundled files
Instructions only
LicenseMIT
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 tobyilee on GitHub. Read the source before you install it.

Installation

Install the Style Review 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/tobyilee/book-writer/tree/main/.claude/skills/style-review
  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/tobyilee/book-writer.git /tmp/book-writer
mkdir -p .claude/skills
cp -r /tmp/book-writer/.claude/skills/style-review .claude/skills/style-review
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Style Review 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 Style Review 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 Style Review 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.

Style Review

챕터를 활성 장르 프로필의 문체 기준으로 점검하고 구체적 대체 문장으로 고친다. 기준은 profiles/{genre}/style-checklist.md와 voice.md다 (genre는 오케스트레이터 전달값 → {slug}/book_manifest.json → 기본 tech-book). 체크리스트 항목과 우선순위는 프로필에만 있다 — 여기에 복사하지 않는다.

점검 방식

  • 빈도 항목은 하한이 아니라 범위로 본다. 부족함만큼 과포화(같은 말버릇이 한 장에 과다하거나 모든 장에 기계적으로 반복)도 결함이다. 반복 횟수는 grep으로 센다.
  • 고칠 곳마다 원문을 인용하고, 대체 문장과 짧은 이유를 적는다. "청유형이 부족하다"가 아니라 "3.2절 두 번째 문단의 '~이다'를 '~해보자'로".
  • 장당 5~10곳, 톤을 가장 크게 흔드는 곳부터. 저술가의 의도적 변주(리듬·강조)는 인정한다.
  • 사실 주장·출처 단서의 내용은 바꾸지 않는다.

로그 형식 ({slug}/style_log.md)

markdown
## {NN}장 (라운드 {N})

### Critical
1. [원문] "..." → [수정] "..." — 이유: {짧게}
### Should
1. ...
### Nice
1. ...

전체 톤: {한 줄 — "토비 목소리가 살아 있지만 2.3절 중반이 딱딱함" 등}

장마다 끝나는 즉시 append한다.

통합 원고 점검

04_manuscript.md를 대상으로 하면 장 경계의 톤 단절, 서문·에필로그와 본문의 어울림, 그리고 장별 오프닝·클로징·최다 말버릇 표로 통권 반복을 함께 본다. 결과는 ## 통합 원고 섹션으로 같은 로그에 남긴다.

Frequently asked questions

What does the Style Review AI skill do?

Review chapter drafts against the active genre profile's style checklist (defaults to tech-book = Toby's voice) — detects voice deviations and applies or proposes concrete before/after rewrites. Use when reviewing a chapter for style consistency, enforcing the genre voice, or polishing prose.

Why use Style Review on TypingMind?

Because you install it once and use it with any model. Style Review 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 Style Review in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/tobyilee/book-writer/tree/main/.claude/skills/style-review. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Style Review?

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 Style Review?

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

Is the Style Review AI skill free?

Yes. It is published on GitHub by tobyilee under the MIT 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 👇