Writing Core logo

Writing Core

CommunityPopular
Norman-bury
writing-core

Use when writing or revising academic papers, especially Chinese journal manuscripts, that need natural prose, de-AI-ification, Markdown formatting, or quality checks

Overview

PublisherNorman-bury
Repositoryresearch-writing-skill
Skill namewriting-core
Stars
3.2K
Forks
214
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 Norman-bury on GitHub. Read the source before you install it.

Installation

Install the Writing Core 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.
  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/Norman-bury/research-writing-skill.git /tmp/research-writing-skill
mkdir -p .claude/skills
cp -r /tmp/research-writing-skill/skills/writing-core .claude/skills/writing-core
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

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

核心写作规范

本技能用于控制论文写作质量,重点是中文学术论文的自然表达、去AI化改写与可提交的Markdown排版。

一、去AI化语言规范

1.1 禁用表达

类型禁用词/句
机械过渡词首先、其次、最后、此外、另外、接下来、总之
空壳强调句值得注意的是、需要指出的是、重要的是、必须强调的是、显而易见
空洞修饰词非常、极其、十分、相当(无数据支撑时)
主观引导句我认为、我觉得、我个人看法是(论文正文禁用)

1.2 推荐表达

  1. 用语义衔接替代模板衔接
  2. 用数据和事实替代形容词
  3. 长短句交替,避免等长句连续出现
  4. 用"本文""实验结果表明""表X显示"等客观主语,但避免连续重复同一模板
  5. 保留必要的限定、承接和少量重复,使段落读起来像正常研究者的中文正文

1.3 句法与信息密度

  1. 列表转段落时补足主语、谓语和连接成分
  2. 一句话围绕一个主要关系展开,必要时保留条件、范围和解释,不要强行压成短句
  3. 保留方法、条件、对象和数据,不用"很多""较大提升"等模糊表述
  4. 去AI化不等于压缩。若改短后丢失数据口径、实验边界、评价对象或结论限制,应恢复必要说明

1.4 中文期刊论文的自然行文原则

中文期刊论文不追求每句话都极度精简。更自然的写法通常是先交代研究对象、资料范围或问题背景,再说明处理方法、结果现象和判断边界。句子可以略长,段落中可以有必要的承接、限定和少量重复,只要主语明确、关系清楚、读者能够顺着研究过程理解即可。

去AI化的重点是减少模板化、翻译腔、过度概括和空泛拔高,而不是删除所有修饰语。能够说明对象、时间范围、样本口径、方法条件、指标含义、实验边界和因果关系的成分应当保留。不要把段落改成机械的"背景-方法-结果-意义"句组,也不要让每句话都呈现"对象-动作-结论"的功能句。

当用户反馈"太AI""太精简""像翻译"时,先检查是否存在过度压缩、英文语序、模板化总结、审稿回复式表达或空泛拔高。处理顺序是补回必要信息,调整为中文自然语序,再收束过强判断。不要继续简单删词。

1.5 常见AI化症状与处理

症状处理方式
句式像英文直译改为中文常用语序,先说明对象和现象,再给判断
段落过度模板化取消固定的"背景-方法-结果-意义"节奏,保留解释句和承接句
改写后信息变少补回研究对象、数据范围、方法条件、指标口径和结论边界
审稿回复口吻将"该指标反映的是""不能理解为"改成正文叙述,如"本文将...作为参照"
空泛拔高用具体指标、现象或限定替代"显著""关键""重要意义"等泛化词

二、输出排版规范

2.1 Markdown正文规范

  1. 正文默认不使用加粗和斜体
  2. 段落之间必须空一行
  3. 正文段落优先连续叙述,不用项目符号堆叠观点
  4. 同一段尽量保持单一中心观点
  5. 避免把一个完整观点拆成过多短段

2.2 允许使用列表的场景

仅以下场景可用列表:

  • 计划文档(plan/*.md
  • 检查清单
  • 参数配置
  • 操作步骤

论文正文默认不用列表。

三、段落构建规则

一个标准段落包含:

  1. 主题句:本段核心结论
  2. 支撑句:依据、证据、解释
  3. 收束句:过渡或小结

建议长度:

  • 中文正文:150-300字
  • 英文正文:100-200词

四、列表转段落规则

错误写法

本研究贡献如下:
- 提出新方法
- 完成自动化流程
- 验证有效性

推荐写法

本研究提出了一种新方法,并将其整合为可执行的自动化流程。
实验结果显示,该方法在目标任务上具有稳定增益,验证了其可行性与应用价值。

五、引用与事实

六、三轮质量检查

第一轮:结构检查

  • 是否存在正文列表化
  • 段落是否围绕单一中心
  • 章节逻辑是否连续
  • 是否把正文写成机械的"背景-方法-结果-意义"模板段

第二轮:语言检查

  • 是否出现禁用过渡词
  • 是否出现禁用强调句式
  • 是否存在无信息量形容词堆积
  • 是否出现主观化表述
  • 是否存在翻译腔、英文语序或审稿回复式表达
  • 是否因过度压缩丢失研究对象、数据范围、方法条件、指标口径或结论边界
  • 是否用具体数据和现象支撑"提升""有效""稳定"等判断

第三轮:排版检查

  • 是否有无意义加粗
  • 段间是否统一空一行
  • 标点与中英文空格是否一致

七、风格自检脚本

写作完成后,运行风格检查脚本:

macOS/Linux:

bash
bash research-writing-skill/scripts/style_check.sh <文件.md>

Windows PowerShell:

powershell
powershell -ExecutionPolicy Bypass -File research-writing-skill/scripts/style_check.ps1 -FilePath <文件.md>

八、执行约束

  1. 长任务开始前必须读取或创建 plan/
  2. 每次完成写作后,更新 plan/progress.mdplan/notes.md
  3. 若用户明确要求保留特定风格,以用户要求优先

Frequently asked questions

What does the Writing Core AI skill do?

Use when writing or revising academic papers, especially Chinese journal manuscripts, that need natural prose, de-AI-ification, Markdown formatting, or quality checks

Why use Writing Core on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Norman-bury/research-writing-skill/tree/main/skills/writing-core. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Writing Core?

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

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

Is the Writing Core AI skill free?

Yes. It is published on GitHub by Norman-bury 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 👇