Markdown to HTML Report
MegaSuperKitty/WeClaw
Drafts a report in Markdown with numbered inline citations and a references section, then renders it to a styled HTML file through a Jinja2 template on Windows.
A skill your agent uses when writing or revising academic papers, especially Chinese journal manuscripts, that need natural prose, de-AI-ification, Markdown formatting, or quality checks
Install Writing Core
$ npx skills add Norman-bury/research-writing-skill --skill writing-core -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Norman-bury/research-writing-skill writing-core --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Norman-bury/research-writing-skill.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/writing-core .claude/skills/writing-core && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "writing-core" agent skill from https://github.com/Norman-bury/research-writing-skill/tree/main/skills/writing-core into .claude/skills/writing-core/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-core", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Norman-bury/research-writing-skill/tree/main/skills/writing-coreType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Norman-bury/research-writing-skill --skill writing-core -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Norman-bury/research-writing-skill writing-core --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Norman-bury/research-writing-skill.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/writing-core .agents/skills/writing-core && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "writing-core" agent skill from https://github.com/Norman-bury/research-writing-skill/tree/main/skills/writing-core into .agents/skills/writing-core/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-core", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Norman-bury/research-writing-skill --skill writing-core -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Norman-bury/research-writing-skill writing-core --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Norman-bury/research-writing-skill.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/writing-core .cursor/skills/writing-core && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "writing-core" agent skill from https://github.com/Norman-bury/research-writing-skill/tree/main/skills/writing-core into .cursor/skills/writing-core/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-core", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Norman-bury/research-writing-skill.git --path skills/writing-core--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Norman-bury/research-writing-skill --skill writing-core -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Norman-bury/research-writing-skill writing-core --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Norman-bury/research-writing-skill.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/writing-core .gemini/skills/writing-core && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "writing-core" agent skill from https://github.com/Norman-bury/research-writing-skill/tree/main/skills/writing-core into .gemini/skills/writing-core/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-core", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Norman-bury/research-writing-skill writing-coreInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Norman-bury/research-writing-skill --skill writing-core -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Norman-bury/research-writing-skill.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/writing-core .github/skills/writing-core && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "writing-core" agent skill from https://github.com/Norman-bury/research-writing-skill/tree/main/skills/writing-core into .github/skills/writing-core/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-core", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Norman-bury/research-writing-skill --skill writing-core -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Norman-bury/research-writing-skill writing-core --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Norman-bury/research-writing-skill.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/writing-core .opencode/skills/writing-core && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "writing-core" agent skill from https://github.com/Norman-bury/research-writing-skill/tree/main/skills/writing-core into .opencode/skills/writing-core/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-core", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
writing-core- GitHub stars
- 3.4k
- Token cost
- ~709 tokens
- SKILL.md length
- 137 words
- Files
- 1
- Skills in repo
- 20
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when writing or revising academic papers, especially Chinese journal manuscripts, that need natural prose, de-AI-ification, Markdown formatting, or quality checks
- Works in 5 steps: 用语义衔接替代模板衔接 → 用数据和事实替代形容词 → 长短句交替，避免等长句连续出现 → …
- Revising academic papers
- SKILL.md covers 一、去AI化语言规范, 二、输出排版规范, 三、段落构建规则 and 四、列表转段落规则, plus 4 more sections
- Calls bash
What it does
Writing Core is an agent skill from Norman-bury/research-writing-skill. Use when writing or revising academic papers, especially Chinese journal manuscripts, that need natural prose, de-AI-ification, Markdown formatting, or quality checks
Its SKILL.md is about 710 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Documents & Office, covering Markdown. The repository describes itself as: 科研写作助手 (Research Writing Assistant). The licence is MIT.
When your agent uses it
- Revising academic papers
- Especially Chinese journal manuscripts
- That need natural prose
- De-AI-ification
Example prompts
- “/writing-core”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- 用语义衔接替代模板衔接
- 用数据和事实替代形容词
- 长短句交替，避免等长句连续出现
- 用"本文""实验结果表明""表X显示"等客观主语，但避免连续重复同一模板
- 保留必要的限定、承接和少量重复，使段落读起来像正常研究者的中文正文
What it can do on your machine
Read from SKILL.md and the folder at commit 6f79595. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
bash
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Writing Core loads about 709 tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 137 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Norman-bury/research-writing-skill at commit 6f79595, republished under its MIT licence (© Norman-bury). 137 words, ~709 tokens.
Download SKILL.mdSave it as
.claude/skills/writing-core/SKILL.md (or your agent's skills folder).- name
- writing-core
- description
- Use when writing or revising academic papers, especially Chinese journal manuscripts, that need natural prose, de-AI-ification, Markdown formatting, or quality checks
核心写作规范
本技能用于控制论文写作质量，重点是中文学术论文的自然表达、去AI化改写与可提交的Markdown排版。
<EXTREMELY-IMPORTANT>
以下规范必须严格遵守，不得因为"效率"或"简化"而跳过。
</EXTREMELY-IMPORTANT>一、去AI化语言规范
1.1 禁用表达
| 类型 | 禁用词/句 |
|---|---|
| 机械过渡词 | 首先、其次、最后、此外、另外、接下来、总之 |
| 空壳强调句 | 值得注意的是、需要指出的是、重要的是、必须强调的是、显而易见 |
| 空洞修饰词 | 非常、极其、十分、相当（无数据支撑时） |
| 主观引导句 | 我认为、我觉得、我个人看法是（论文正文禁用） |
1.2 推荐表达
- 用语义衔接替代模板衔接
- 用数据和事实替代形容词
- 长短句交替，避免等长句连续出现
- 用"本文""实验结果表明""表X显示"等客观主语，但避免连续重复同一模板
- 保留必要的限定、承接和少量重复，使段落读起来像正常研究者的中文正文
1.3 句法与信息密度
- 列表转段落时补足主语、谓语和连接成分
- 一句话围绕一个主要关系展开，必要时保留条件、范围和解释，不要强行压成短句
- 保留方法、条件、对象和数据，不用"很多""较大提升"等模糊表述
- 去AI化不等于压缩。若改短后丢失数据口径、实验边界、评价对象或结论限制，应恢复必要说明
1.4 中文期刊论文的自然行文原则
中文期刊论文不追求每句话都极度精简。更自然的写法通常是先交代研究对象、资料范围或问题背景，再说明处理方法、结果现象和判断边界。句子可以略长，段落中可以有必要的承接、限定和少量重复，只要主语明确、关系清楚、读者能够顺着研究过程理解即可。
去AI化的重点是减少模板化、翻译腔、过度概括和空泛拔高，而不是删除所有修饰语。能够说明对象、时间范围、样本口径、方法条件、指标含义、实验边界和因果关系的成分应当保留。不要把段落改成机械的"背景-方法-结果-意义"句组，也不要让每句话都呈现"对象-动作-结论"的功能句。
当用户反馈"太AI""太精简""像翻译"时，先检查是否存在过度压缩、英文语序、模板化总结、审稿回复式表达或空泛拔高。处理顺序是补回必要信息，调整为中文自然语序，再收束过强判断。不要继续简单删词。
1.5 常见AI化症状与处理
| 症状 | 处理方式 |
|---|---|
| 句式像英文直译 | 改为中文常用语序，先说明对象和现象，再给判断 |
| 段落过度模板化 | 取消固定的"背景-方法-结果-意义"节奏，保留解释句和承接句 |
| 改写后信息变少 | 补回研究对象、数据范围、方法条件、指标口径和结论边界 |
| 审稿回复口吻 | 将"该指标反映的是""不能理解为"改成正文叙述，如"本文将...作为参照" |
| 空泛拔高 | 用具体指标、现象或限定替代"显著""关键""重要意义"等泛化词 |
二、输出排版规范
2.1 Markdown正文规范
- 正文默认不使用加粗和斜体
- 段落之间必须空一行
- 正文段落优先连续叙述，不用项目符号堆叠观点
- 同一段尽量保持单一中心观点
- 避免把一个完整观点拆成过多短段
2.2 允许使用列表的场景
仅以下场景可用列表：
- 计划文档（
plan/*.md） - 检查清单
- 参数配置
- 操作步骤
论文正文默认不用列表。
三、段落构建规则
一个标准段落包含：
- 主题句：本段核心结论
- 支撑句：依据、证据、解释
- 收束句：过渡或小结
建议长度：
- 中文正文：150-300字
- 英文正文：100-200词
四、列表转段落规则
错误写法
本研究贡献如下：
- 提出新方法
- 完成自动化流程
- 验证有效性推荐写法
本研究提出了一种新方法，并将其整合为可执行的自动化流程。
实验结果显示，该方法在目标任务上具有稳定增益，验证了其可行性与应用价值。五、引用与事实
<HARD-GATE>
1. 不编造文献或数据
2. 引用格式与全文统一
3. 含有结论性表述时，优先给出处或数据
</HARD-GATE>六、三轮质量检查
第一轮：结构检查
- 是否存在正文列表化
- 段落是否围绕单一中心
- 章节逻辑是否连续
- 是否把正文写成机械的"背景-方法-结果-意义"模板段
第二轮：语言检查
- 是否出现禁用过渡词
- 是否出现禁用强调句式
- 是否存在无信息量形容词堆积
- 是否出现主观化表述
- 是否存在翻译腔、英文语序或审稿回复式表达
- 是否因过度压缩丢失研究对象、数据范围、方法条件、指标口径或结论边界
- 是否用具体数据和现象支撑"提升""有效""稳定"等判断
第三轮：排版检查
- 是否有无意义加粗
- 段间是否统一空一行
- 标点与中英文空格是否一致
七、风格自检脚本
写作完成后，运行风格检查脚本：
macOS/Linux：
bash research-writing-skill/scripts/style_check.sh <文件.md>Windows PowerShell：
powershell -ExecutionPolicy Bypass -File research-writing-skill/scripts/style_check.ps1 -FilePath <文件.md>八、执行约束
- 长任务开始前必须读取或创建
plan/ - 每次完成写作后，更新
plan/progress.md与plan/notes.md - 若用户明确要求保留特定风格，以用户要求优先
© Norman-bury, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/writing-core of Norman-bury/research-writing-skill.
Open the folder on GitHubat commit 6f79595
Compare with similar skills
Writing Core next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Writing Core this skillNorman-bury/research-writing-skill | 3.4k | — | ~709 | Automated safety check: Pass | MIT | |
| Markdown to HTML ReportMegaSuperKitty/WeClaw | 370 | — | ~456 | Automated safety check: Pass | MIT | |
| Paper Interpretationdigoal/blog | 8.6k | — | ~1.5k | Automated safety check: Pass | GPL-2.0 | |
| Suikonwiizo/suiko | 114 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Deepxiv Baseline TableDeepXiv/deepxiv_sdk | 804 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Mindmap Renderai4s-research/ai4s-skills | 237 | 1 repos | ~3.1k | Automated safety check: Pass | MIT |
Similar skills
Paper Interpretation
digoal/blog
从论文 PDF 文件或论文 PDF URL 生成通俗易懂、图文并茂、带批判性评估的中文 Markdown 解读，并保存到当前项目的 markdown 目录。Use when the user asks to interpret,精读,解读,summarize,explain,analyze, or write an article from an academic paper PDF…
Suiko
nwiizo/suiko
日本語文書のAI由来の均一さ、翻訳調、不自然さ、論旨、読解負荷を、決定的なRust CLIと目視で診断し、依頼に応じて書く・直す。日本語の学術論文・研究報告では、中心命題、用語、論証、DOCX/PDF納品を監査契約で確認する。Use when the user explicitly mentions suiko, asks whether Japanese text looks…
Deepxiv Baseline Table
DeepXiv/deepxiv_sdk
Build a markdown baseline table for a research topic using deepxiv search, brief, head, and experiment-section reads, extracting paper title, URL, open-source status, datasets, benchmark scores, and…
Mindmap Render
ai4s-research/ai4s-skills
Generate beautiful, high-resolution mindmaps from Markdown unordered lists.
Marker
benchflow-ai/skillsbench
Convert PDF documents to Markdown using markersingle. An agent skill from benchflow-ai/skillsbench.
More from Norman-bury/research-writing-skill
All 20 skills in this repoEvidence Driven Writing
Norman-bury/research-writing-skill
A skill your agent uses when writing or revising Introduction, Related Work, background, literature synthesis, or any section where references must drive claims
Environment Setup
Norman-bury/research-writing-skill
A skill your agent uses when Python environment setup is needed for data visualization or conda installation is required
Experiment Results Planning
Norman-bury/research-writing-skill
A skill your agent uses when designing experiments, result tables, mock planning data, evaluation protocols, or results sections before real data are final
Figures Diagram
Norman-bury/research-writing-skill
A skill your agent uses when creating flowcharts, architecture diagrams, or conceptual diagrams - generates prompts for image AI
Figures Python
Norman-bury/research-writing-skill
A skill your agent uses when creating data visualizations for papers - generates publication-quality plots with top-journal color schemes
Latex Output
Norman-bury/research-writing-skill
A skill your agent uses when user requests LaTeX format output or has provided school/journal LaTeX templates
Related
Categories
Questions about Writing Core
What does Writing Core do?
A skill your agent uses when writing or revising academic papers, especially Chinese journal manuscripts, that need natural prose, de-AI-ification, Markdown formatting, or quality checks. Writing Core is an agent skill from Norman-bury/research-writing-skill.
When should I use Writing Core?
Writing Core fits situations like: revising academic papers; especially Chinese journal manuscripts; that need natural prose; de-AI-ification.
How do I install Writing Core in Claude Code?
Run `npx skills add Norman-bury/research-writing-skill --skill writing-core -a claude-code`. Or copy the skill folder (skills/writing-core in Norman-bury/research-writing-skill) into .claude/skills/writing-core in your project. Claude Code loads it when a task matches its description.
How do I install Writing Core in Codex?
Run `npx skills add Norman-bury/research-writing-skill --skill writing-core -a codex`. Or copy the skill folder (skills/writing-core in Norman-bury/research-writing-skill) into .agents/skills/writing-core in your project. Codex loads it when a task matches its description.
Can I use Writing Core in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Norman-bury/research-writing-skill --skill writing-core -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/writing-core, .gemini/skills/writing-core, .github/skills/writing-core and .opencode/skills/writing-core in your project.
What does Writing Core need to run?
Going by SKILL.md and its folder, Writing Core needs the command-line tools its instructions call (bash).
Does Writing Core access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Writing Core safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Writing Core use?
Writing Core is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Writing Core use?
About 709 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Writing Core?
Skills that share tags, products or a category with Writing Core: Markdown to HTML Report (MegaSuperKitty/WeClaw, 370 stars), Paper Interpretation (digoal/blog, 8.6k stars), Suiko (nwiizo/suiko, 114 stars) and Deepxiv Baseline Table (DeepXiv/deepxiv_sdk, 804 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Writing Core?
Norman-bury (a GitHub user) maintains it in Norman-bury/research-writing-skill, which has 3,384 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on June 10, 2026.
Source: Norman-bury/research-writing-skill on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.