TypingMindTypingMindThe best frontend for AI
Chapter Writing logo

Chapter Writing

Community
tobyilee
chapter-writing

Write a single book chapter in Toby's distinctive Korean writing style (평어체 기반, 청유형 적극 활용, 수사적 질문, 상황 가정, 감정적 공감 표현). Use when drafting or revising a book chapter, rewriting prose in Toby's voice, translating an outline into full chapter text, or polishing chapter drafts to match 토비 문체. Triggers on "챕터 써줘", "이 섹션 저술", "토비 스타일로 써줘", "write a chapter in Toby's voice", "rewrite in 평어체", or when a chapter outline needs to become full prose.

Overview

Publishertobyilee
Repositorybook-writer
Skill namechapter-writing
Stars
85
Forks
20
Bundled files
2
LicenseMIT
Links
Skill sourceRepository
  • 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.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

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

Installation

Install the Chapter Writing 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/chapter-writing
  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/chapter-writing .claude/skills/chapter-writing
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Chapter Writing 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 Chapter Writing 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 Chapter Writing 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.

Chapter Writing (장르 프로필 기반)

하나의 챕터를 활성 장르 프로필의 voice로 저술한다.

활성 프로필을 먼저 확인하자. 우선순위: 오케스트레이터가 전달한 genre → {slug}/book_manifest.json의 genre → 기본값 tech-book. 해당 profiles/{genre}/voice.md(문체)와 scaffolds.md(구조)를 읽고 그 규약을 따른다. 프로필 목록·선택 규칙은 profiles/_registry.md.

아래 본문(핵심 원칙·표현 사전·피해야 할 패턴)은 tech-book 프로필(기본값 = Toby 문체) 기준이다. narrative·practical·essay 장르는 본문 대신 해당 프로필의 voice.md를 따른다 — 공감어("찜찜하다")·실습 청유("해보자")는 tech-book 전용이다.

tech-book 핵심 원칙

원칙내용
평어체 기반기본 서술은 -다, -한다 형태. 딱딱하지 않게, 친절하게 개념을 풀어낸다.
청유형-자, -보자로 "함께 개선하자"는 동반자 어조를 만든다. 자주 쓰되 한 문단에 몰아 쓰지 않는다.
문답법새 개념을 도입할 때 "왜 그럴까?", "어떻게 해야 할까?" 같은 수사적 질문을 먼저 던지고 스스로 답한다.
상황 가정"~라고 상상해보자", "~한다고 해보자"로 실무 상황을 먼저 세운 뒤 개념을 붙인다.
감정적 공감나쁜 코드·잘못된 관행을 설명할 때 "난감하다", "찜찜하다", "번거롭다", "끔찍한 일이다" 같은 감각적 단어를 활용한다.
논리 전환"그렇다면 ~", "물론 ~다. 하지만 ~"로 반론을 선제 차단하며 논리를 잇는다.

자주 쓰는 표현 사전

주의 환기·사고 유도:

  • "살펴보자", "알아보자", "생각해보자", "함께 고민해보자"

권장·대안 제시(강압 금지):

  • "~하는 편이 낫다", "~하는 것이 바람직하다", "~하는 것이 좋다"

핵심 당부:

  • "기억해두자", "잊지 말자", "주의해야 한다"

문제 상황 묘사:

  • "난감하다" / "초난감한 상황이다"
  • "찜찜하다"
  • "번거롭다"
  • "끔찍한 일이다"

논리 전환:

  • "그렇다면 어떻게 해야 할까?"
  • "물론 ~다. 하지만 ~"

상세 가이드와 예시는 활성 profiles/{genre}/voice.md 참조 (tech-book = profiles/tech-book/voice.md).

챕터 구성

  • 입력 — 02_plan.md에서 이 장의 핵심 질문·주요 내용·배정된 오프닝/클로징/스캐폴드, 계획의 "용어 표기", 01_reference.md에서 이 장과 관련된 부분.
  • 스캐폴드 — profiles/{genre}/scaffolds.md에서 배정된 유형을 따르되, 억지로 맞추기보다 흐름을 우선한다.
  • 오프닝 — 배정된 기법으로 연다 (tech-book 메뉴: 상황 가정·수사적 질문·충격 수치·일화·실패 장면·앞 장 콜백·정의 뒤집기). "이번 장에서는 ~를 다룬다" 같은 메타 선언으로 시작하지 않는다.
  • 본문 — 개념을 하나씩 도입한다. 대개 상황이나 질문 → 친절한 설명 → 필요하면 코드·예시 → "그렇다면 ~" 식 전환의 흐름이 Toby 문체에 맞는다.
  • 공감 표현 — "난감하다", "찜찜하다" 같은 표현은 장당 1~2회면 충분하다. 매 절 반복하면 tic이 되고, 비워 두는 장이 있어도 좋다.
  • 클로징 — 배정된 기법으로 닫는다. 중간 장이 매번 "다음 장에서는 ~"로 끝나면 책 전체가 단조로워진다. 마지막 장은 여정을 회수하는 닫는 매듭이다. ## 마무리 헤딩은 필수가 아니다.
  • 기준 — 저장하는 원고는 활성 style-checklist.md를 충족해야 한다. 기본 흐름에는 별도 스타일 검수가 없다.

피해야 할 패턴

  • 고압적 지시: "반드시 ~해야 한다" → "~하는 편이 낫다" 또는 "~해보자"
  • 메타 서술: "이 책에서는", "이번 장에서는 ~를 설명한다" — 정보성·구조적 문장은 최소화
  • 외래어 남용: 한국어로 충분히 표현 가능한 개념을 불필요하게 영어·일본어로 쓰지 말자
  • 과도한 번호 매김: 서술이 리스트로만 채워지면 목차 같아 보인다. 문단형 서술을 우선한다
  • 무감정한 건조체: 기술서라도 감각적 단어로 호흡을 만든다

출력 형식

  • 파일: Markdown (# 챕터 제목 → ## 절 제목 → ### 소절 제목)
  • 최상위 헤딩(#)은 챕터당 1회만 사용
  • 코드 블록은 ```언어 형태로 명시
  • 인용·강조는 >, ** 사용

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Chapter Writing AI skill do?

Write a single book chapter in Toby's distinctive Korean writing style (평어체 기반, 청유형 적극 활용, 수사적 질문, 상황 가정, 감정적 공감 표현). Use when drafting or revising a book chapter, rewriting prose in Toby's voice, translating an outline into full chapter text, or polishing chapter drafts to match 토비 문체. Triggers on "챕터 써줘", "이 섹션 저술", "토비 스타일로 써줘", "write a chapter in Toby's voice", "rewrite in 평어체", or when a chapter outline needs to become full prose.

Why use Chapter Writing on TypingMind?

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

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

Which AI models can use Chapter Writing?

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 Chapter Writing?

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

Is the Chapter Writing 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.

Related AI Skills

View all
obra logo

Writing Skills

obra
CommunityPopular

Use when creating new skills, editing existing skills, or verifying skills work before deployment

25.8K
288.1K
6 files
View
affaan-m logo

Skill Host Compat

affaan-m
CommunityPopular

Lint ECC skills for Codex/Cursor-safe frontmatter and Claude-only substitutions before a skill PR.

41.4K
277.3K
1 files
View
affaan-m logo

Brand Voice

affaan-m
CommunityPopular

Build a source-derived writing style profile from real posts, essays, launch notes, docs, or site copy, then reuse that profile across content, outreach, and social workflows. Use when the user wants…

40.4K
270.2K
2 files
View
affaan-m logo

Competitive Platform Analysis

affaan-m
CommunityPopular

Use when scoping a competitive landscape — identifying, categorising, and score-filtering a competitor set before any benchmarking begins. Decides who counts as a competitor, which tier they belong…

40.4K
270.2K
1 files
View

Set up your own AI workspace now

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