Writing Tool Integrations

May 6, 2026 ยท View on GitHub

Writer's Loop does not need a plugin to be useful in writing tools. This repo ships copy-ready instructions and templates that work with tools that can hold project instructions, reference files, Markdown pages, or AI-accessible docs.

Support levels here are conservative:

  • Native instruction workspace: the tool has project instructions and files.
  • AI-connected workspace: the tool can be used by an AI assistant through an official connector, MCP server, or CLI.
  • Template workspace: the tool can host Writer's Loop templates, but the AI work happens in a connected assistant or by copy/paste.

Supported Tools

ToolSupport levelWhat users getIntegration files
ChatGPT Projects / GPTsNative instruction workspaceProject/GPT instructions plus uploaded Writer's Loop reference filesintegrations/chatgpt/project-instructions.md
Claude ProjectsNative instruction workspaceProject instructions plus project knowledge filesintegrations/claude/project-instructions.md
ObsidianTemplate workspaceLocal Markdown templates for briefs, critique, and style packsintegrations/obsidian/templates/
NotionAI-connected workspaceA page template that works with Notion AI or Notion MCPintegrations/notion/writers-loop-page-template.md
Feishu / Lark DocsAI-connected workspaceA doc template usable manually or through Feishu CLI's document skillintegrations/feishu/writers-loop-doc-template.md
LogseqTemplate workspaceAn outliner template for Frame, Plan, Decisions, and Revisionintegrations/logseq/templates/writers-loop.md

Quick Setup

Use these from the repository root after cloning https://github.com/xxsang/writers-loop.

Obsidian:

VAULT="$HOME/Documents/Obsidian/MyVault"
mkdir -p "$VAULT/Templates/Writers Loop"
cp integrations/obsidian/templates/*.md "$VAULT/Templates/Writers Loop/"

Logseq:

GRAPH="$HOME/Documents/Logseq/MyGraph"
mkdir -p "$GRAPH/pages"
cp integrations/logseq/templates/writers-loop.md "$GRAPH/pages/writers-loop-template.md"

Notion, Feishu/Lark Docs, ChatGPT Projects, and Claude Projects do not install local files. Paste or upload the integration file listed in the table, then keep the decision log in the target workspace.

ChatGPT Projects Or GPTs

Use this when you want Writer's Loop to stay available across repeated writing sessions in ChatGPT.

  1. Create a ChatGPT Project or GPT.
  2. Paste integrations/chatgpt/project-instructions.md into project/GPT instructions.
  3. Add these files as project files or GPT knowledge:
    • skills/writers-loop/SKILL.md
    • skills/writers-loop/references/artifact-types.md
    • skills/writers-loop/references/technical-writing.md
    • skills/writers-loop/references/business-writing.md
    • skills/writers-loop/references/fiction-narrative.md
    • skills/writers-loop/references/critique-rubrics.md
    • skills/writers-loop/references/checkpoints.md
    • skills/writers-loop/references/preference-signals.md
    • skills/writers-loop/references/preference-journal.md
    • skills/writers-loop/references/style-distillation.md
    • skills/writers-loop/references/translation.md
    • skills/writers-loop/references/multi-agent.md
    • docs/prompt-templates.md
  4. Start with:
Use Writer's Loop for this writing task.

Artifact:
Audience:
Goal:
Constraints:
Source material:

Official references: ChatGPT Projects, creating and editing GPTs.

Claude Projects

Use this when you want a Claude workspace dedicated to one book, report, publication workflow, client, research project, or content system.

  1. Create a Claude Project.
  2. Paste integrations/claude/project-instructions.md into project instructions.
  3. Add the same Writer's Loop files listed above to project knowledge.
  4. Ask Claude to use Writer's Loop and stop at plan or proposal checkpoints.

Official references: Claude Projects, creating and managing Claude Projects.

Obsidian

Use this when you want a local writing vault with explicit decision records. Obsidian does not run Writer's Loop as a native skill. The support here is template-based and local-first.

Fast local setup:

VAULT="$HOME/Documents/Obsidian/MyVault"
mkdir -p "$VAULT/Templates/Writers Loop"
cp integrations/obsidian/templates/*.md "$VAULT/Templates/Writers Loop/"

Then:

  1. Replace MyVault with your vault path.
  2. Enable the Obsidian Templates core plugin.
  3. Set the template folder to Templates/Writers Loop.
  4. Create a note for each writing artifact.
  5. Insert writers-loop-brief.md before asking an AI assistant for help.
  6. Use critique-and-revision.md to record accepted, rejected, and adjusted changes.
  7. Use style-pack.md only after the source style pack has been reviewed.

Official references: Obsidian Templates, Obsidian URI, Obsidian community plugins.

Notion

Use this when the writing artifact already lives in Notion or when a team uses Notion AI/MCP as its writing surface.

  1. Create a Notion page.
  2. Paste integrations/notion/writers-loop-page-template.md.
  3. Fill in Frame, Source Material, and Constraints.
  4. Use Notion AI or an external assistant connected through Notion MCP to draft from the page.
  5. Keep decisions in the Decision Log section before deriving preferences.

Official references: Notion AI for docs, Notion MCP, Notion AI Connectors.

Feishu / Lark Docs

Use this when a team writes in Feishu/Lark Docs and wants an AI agent to create or update Writer's Loop documents.

Manual path:

  1. Create a new Feishu/Lark doc.
  2. Paste integrations/feishu/writers-loop-doc-template.md.
  3. Fill in the Frame and Decision Log.
  4. Ask the team's AI assistant to draft, critique, and revise from that doc.

Agent path:

  1. Install the official Feishu/Lark CLI and AI agent skills.
  2. Authenticate with least-privilege scopes.
  3. Use the CLI document skill to create or update docs from Markdown.

Example:

npm install -g @larksuite/cli
npx skills add larksuite/cli -y -g
lark-cli config init
lark-cli auth login --recommend
lark-cli docs +create --title "Writer's Loop Brief" --markdown "$(cat integrations/feishu/writers-loop-doc-template.md)"

Official reference: Feishu/Lark CLI.

Logseq

Use this when you want an outliner-based decision log. Logseq does not run Writer's Loop as a native skill. The support here is a reusable block template.

Fast local setup:

GRAPH="$HOME/Documents/Logseq/MyGraph"
mkdir -p "$GRAPH/pages"
cp integrations/logseq/templates/writers-loop.md "$GRAPH/pages/writers-loop-template.md"

Then:

  1. Replace MyGraph with your graph path.
  2. Keep the template:: writers-loop block.
  3. Insert it with Logseq's template workflow when starting a writing artifact.
  4. Paste the filled brief into ChatGPT, Claude, Codex, or another AI assistant.
  5. Bring accepted/rejected decisions back into the Logseq note.

Official reference: Logseq documentation repository.

What This Is Not

  • Not an Obsidian, Notion, Feishu, or Logseq plugin.
  • Not automatic scraping of private drafts.
  • Not native skill support where the tool does not provide it.
  • Not durable preference storage unless the user explicitly opts in.