Skill-Details

interactive-writing-assistant

Generic writing workflow with optional PKM integration.

ÜbereinstimmungMöglichGeprüft für obsidian
Quellejykim/claude-obsidian-skillsExterne Quelle
Gemeldete Installationen58Nur Popularitätssignal

Vor Nutzung prüfen

Die automatische Prüfung bewertet Relevanz, nicht Sicherheit oder Empfehlung. Lies vor der Nutzung die Quellanweisungen.

Gespeicherte Quellvorschau

SKILL.md

Dieser Auszug wurde bei der Prüfung gespeichert. Die externe Quelle enthält die vollständige und aktuelle Version.

---
name: interactive-writing-assistant
description: This skill provides comprehensive support for the writing process from ideation through revision. Use this skill when helping users write essays, articles, or creative pieces through interactive collaboration. The skill supports co-evolving outline and prose, voice-based input processing, multiple writing styles, and connection to the user's PKM system for enriched content.
allowed-tools:
  - Read
  - Write
  - Edit
  - Glob
  - Grep
license: MIT
---

# Interactive Writing Assistant

## Overview

This skill supports all stages of the writing process through interactive collaboration with the user. The key principle is to develop outline and prose together (Co-evolving Outline+Prose), maintaining synchronization between high-level structure and detailed content while leveraging the user's knowledge base.

## Core Principles

### Co-evolving Outline+Prose (COP)

Develop outline and prose together for any piece to evolve both the big picture (via outline) and details (prose) while keeping them in sync.

Format structure:
```
## Section Title
%%
- Outline point 1
- Outline point 2
%%

Detailed prose goes here...
```

**COP Guidelines:**
- When given work with only outline (or prose), fill in the other
- When updating outline, also update corresponding prose (and vice versa)
- Place prose immediately below its outline (never separate them)

### Voice-based User Input (VUI)

User input may come via voice interface, combining commands and content that need parsing before action.

**VUI Examples:**
```
Let's continue writing:
    [content to be processed via IVT]

Let's improve this:
1. Remove all references of XYZ from writing
2. Change the style to the like of Haruki
```

**VUI Processing:**
- Parse commands from content
- Process voice content through Improve Voice Transcript (IVT) prompt
- Find user comments within markdown or HTML comments (%% %%)
- Mark comments as `RESOLVED` when addressed

### Connected and Living Document (CLD)

Every piece is written as part of a PKM system, connected to other knowledge notes. Tap into this rich Information and Knowledge (INK) throughout the writing process, particularly in:
- Ideation Helper (IDH)
- Outline Expander (OEX)
- Devil's Advocate (DAV)

Keep the outcome document up-to-date as new INK is received.

### Style References

Apply specific writing styles when requested. You can create style guides in `references/` folder:
- Style guides describe tone, vocabulary, sentence structure preferences
- Load the appropriate style guide when user requests a specific style

## Writing Process Prompts

### Ideation Helper (IDH)

**Purpose:** Find and add relevant content from the knowledge base to enrich current draft.

**Process:**
1. Search for relevant experiences in Journal folder
2. Search for relevant readings in Reading/Articles folders
3. Search for relevant topics in Topics folder
4. Insert findings in Markdown blockquotes (>)

**Usage:** Apply when user needs inspiration or wants to connect draft to existing knowledge.

---

### Outline Expander (OEX)

**Purpose:** Enrich and improve the outline itself to prepare for writing.

**Process:**
1. Fill logical gaps to create natural flow
2. When possible, pull related content from knowledge base (as Wiki links)
3. When needed, suggest ideas for improvement

**Usage:** Apply to strengthen outline before writing prose or when outline feels incomplete.

---

### Improve Voice Transcript (IVT)

**Purpose:** Process and improve voice-transcribed content.

**Process:**
1. Fix grammar or transcript errors
   - Remove extra/duplicated newlines
2. Add chapters (approximately one per page)
   - Use heading3 (###)
3. Add formatting
   - Add lists (bullet point / numbered)
   - Highlight quotes to save in summary
   - Limit to essence (one highlight per chapter)
4. Otherwise keep existing prose
   - Overall length should equal the original

**Usage:** Apply to voice-recorded content or rough transcrip
Vollständige Quelle auf GitHub lesen (öffnet externe Seite)
Kontext

Verwandte Arbeit