jcm-article-writing

JCM Article Writing

This skill is used to clearly organize the materials, rules, and writing direction before article writing, and is especially suitable for "Jinchenma-style AI practical writing": aimed at beginners, speaking plainly, solving specific problems, and ultimately delivering article materials and structure that can be saved/bookmarked and followed step by step.

Core principles:

Material sources must be clear.
Writing rules must match the article type.
Material organization keeps only the currently valid results and does not record the discussion process.
Outline collaboration keeps only the currently valid structure and constraints and does not record the back-and-forth discussion process.
When there is no material address explicitly provided by the user, ask for the address first and do not make assumptions.
When there is no save directory explicitly provided by the user, by default use the one under the user's current project directory jcm-article-writing-workspace/articles/。
The public version reads the public reference files within this skill by default; if the user has their own style document, you can use the one under the user's current project directory jcm-article-writing-workspace/style/ to save and read.
Do not write user-generated materials, indexes, outlines, first drafts, revisions, or personal style documents into the skill installation directory.

Capability boundaries

This skill is currently responsible for:

Confirming the article topic and writing goal.
Clarifying the material sources used for this writing task.
Reading local materials according to the material address provided by the user.
Conducting online searches as needed and organizing the materials.
Generating material cards and a material index.
Collaboratively generating or updating the result-state outline based on materials and user feedback.
Reading public style references in AI practical writing scenarios.
Providing a clean material foundation for subsequent outlines, first drafts, and revisions.
After the first draft is completed, with user confirmation, conducting one independent review based on public style references.

This skill does not complete by default:

Directly generating a complete final draft.
Automatically entering revision.
Automatically publishing to any platform.
Automatically selecting a local directory as the material source.
Automatically starting review before user confirmation.
Doing social media dissemination annotations.

If the user requests an outline, first draft, revision, illustrations, or publishing, you can continue to assist, but you must first confirm the material source and output target.

Applicable scenarios

Use this skill to handle these tasks:

The user has an article topic and wants to organize materials first.
The user requests searching for guides, tutorials, cases, or materials and saving them.
The user provides a note, a directory, a material index, or a set of links and wants them organized into writing materials.
The user already has materials and wants to discuss the title, structure, chapter choices, writing angle, or outline.
The user wants to write an AI practical article, especially emphasizing that it is aimed at beginners, speaks plainly, is actionable, and has save/bookmark value.
The user is looking for style, structure, low-AI-flavor, or writing constraint materials for an AI practical article.

Do not use this skill for these tasks:

Turn source material into a candidate pool of short social media content.
Publish to X, WeChat Official Account, Substack, LinkedIn.
Organize diaries, notes, or task lists.

Source Material Rules

Before entering source material organization, outlining, first draft, or revision, you must first confirm which source material is being used this time.

Source material can be:

A single note path.
A directory path.
A source material index path.
Raw text pasted by the user.
A set of links provided by the user.
Sources obtained through web search requested by the user.

If the user asks to write based on existing source material but does not clearly provide the source material address, you must first ask:

这次写作要基于哪份素材？请给我笔记路径、目录路径、素材索引路径，或者直接粘贴原始素材。

If the user asks to "search the whole web," "search for source material first," or "find materials," this itself is a source material source, so there is no need to ask again for a local source material address; go directly to search.

Do not guess the source of existing source material on your own.

Do not read any local private directory by default.

Do not automatically select an existing file just because the title is similar.

Default Project Workspace

The public version provides a default project workspace to lower the barrier to use for ordinary users.

The default workspace location is under the user's current project directory:

./jcm-article-writing-workspace/

Here, ./ refers to the project directory the user is currently working in, not the installation directory of this skill. If the current project directory cannot be determined, first ask the user where they want to save the writing project.

Default structure:

jcm-article-writing-workspace/
  articles/
    {选题目录}/
      素材/
        00-素材索引.md
        01-{来源或主题简名}.md
      01-文章大纲.md
      02-文章初稿.md
  style/
    user-writing-style.md

Usage rules:

If the user provides a save directory, use the directory provided by the user first.
If the user does not provide a save directory, by default create it under the user's current project directory: jcm-article-writing-workspace/articles/{选题目录}/。
{选题目录} Use the topic title to generate it, remove symbols unsuitable for file names, and keep it short and readable.
Source material cards are saved by default to jcm-article-writing-workspace/articles/{选题目录}/素材/。
The source material index is saved by default as jcm-article-writing-workspace/articles/{选题目录}/素材/00-素材索引.md。
The outline is saved by default as jcm-article-writing-workspace/articles/{选题目录}/01-文章大纲.md。
The first draft is saved by default as jcm-article-writing-workspace/articles/{选题目录}/02-文章初稿.md。
If the user wants to add their own writing style rules but has no existing path, by default have the user write or paste the rules into jcm-article-writing-workspace/style/user-writing-style.md。
If the default workspace or subdirectory does not exist, it can be created directly without asking again.
Do not create user article projects under skills/jcm-article-writing/ .

Execution Flow

1. Confirm the writing goal

First confirm what is to be written this time and who it is written for.

If the user has already clearly stated the topic and target readers, go directly to the next step.

If the topic is unclear, ask only one question:

这篇文章的选题标题你想暂定为什么？

2. Confirm the source material source

Check whether the user has already provided a source material address, raw text, or links.

If not, first ask for the source material source.

If the user requests a whole-web search, first break the topic into 2-5 search directions, then search.

Common search directions:

Official features and product rules.
Hands-on tutorials and beginner steps.
Cases, templates, prompts.
Risks, limitations, privacy, and common misconceptions.
Research papers or industry background.

3. Read or search source material

Read local source material according to the path provided by the user.

Online retrieval adopts a layered strategy of "Web Search first, then XCrawl":

First use your own Web Search / ordinary web page opening capability to retrieve and read sources.
If Web Search can find results and can also open them and obtain sufficient body text, organize the material directly based on Web Search without additionally calling XCrawl.
If Web Search can only see search snippets, cannot open the body text, the body text is empty, you encounter dynamically rendered pages, anti-scraping/verification pages, script fragments, login walls, regional restrictions, or you cannot confirm key facts, then escalate to use xcrawl。
When using xcrawl , prioritize crawling specific URLs rather than performing a new broad search; for output format, prioritize markdown、summary、links, and if necessary then use json to extract structured information.
If xcrawl still cannot obtain the body text, explain in the "Writing Notes" of the material card or material index: where ordinary Web Search / XCrawl respectively got stuck, and whether the current judgment comes from search snippets, other cross-referenced sources, or still requires manual browser verification.

Follow these priorities during online retrieval:

Official documentation, help centers, developer documentation, product announcements.
Authoritative media, research papers, credible industry reports.
High-quality personal tutorials, practical case studies, tool guides.
Community discussions serve only as supplements and cannot be the sole basis.

For product features, prices, entry points, and model capabilities that change, the latest sources must be verified.

Do not save low-quality SEO collage articles.

Do not copy large passages of copyrighted web content.

4. Confirm or create a save location

Before saving the material card or index, check whether the user has provided a save directory.

If the user has already provided a save directory, use the location specified by the user.

If the user has not provided a save directory, create and use by default:

./jcm-article-writing-workspace/articles/{选题目录}/素材/

Do not stall the process just because the user did not provide a save directory.

5. Save material cards

Save each valid source as a Markdown material card.

File naming:

NN-{来源或主题简名}.md

Material card Front Matter:

---
created: YYYY-MM-DD HH:mm:ss
title: {素材卡标题}
categories: []
tags: []
source: {来源方}
source_url: {来源链接}
---

If the source is text pasted by the user or a local file,source_url can be omitted, and the body text must note the source type.

Material card body structure:

# {素材卡标题}

## 来源信息

- 来源：{来源方}
- 链接：{URL}
- 适用章节：{这条素材适合支撑文章哪个部分}

## 核心信息

用自己的话概括来源内容。不要整段复制网页原文。

## 对选题有用的点

列出这条素材能支撑的判断、步骤、例子或反面提醒。

## 可转化成文章段落

写 1-3 段可直接启发后续写作的中文表达。可以给示例说法，但不要冒充最终成稿。

## 小白操作提示

如果来源适合教程化，整理成步骤、模板或 checklist。不适合教程化时可以省略本节。

## 写作注意

记录来源限制、版本差异、隐私风险、需要二次核验的信息。

6. Save the material index

The material index is used to quickly determine how to write later, and does not record the intermediate discussion process.

Index file naming:

00-素材索引.md

Front Matter：

---
created: YYYY-MM-DD HH:mm:ss
title: {选题}：素材索引
categories: []
tags: []
content_role:
  - 选题
---

Body structure:

# {选题}：素材索引

## 选题定位

用 2-5 句话说明这篇文章面向谁、解决什么问题、核心切入点是什么。

## 核心写作判断

只保留当前有效判断，不保留被否决的候选。

## 建议行文逻辑

给出适合当前选题的阅读路径。不要写成资料目录。

## 已整理素材

- [[01-...]]
- [[02-...]]

## 可直接复用的模板或清单

如果本选题适合干货写作，整理可收藏、可照抄、可执行的内容。

## 后续动作

说明下一步可以进入大纲、初稿、改稿、配图或发布适配。

7. Outline collaboration stage

When the user begins discussing titles, structure, chapter trade-offs, writing angles, reader positioning, or outlines, enter the outline collaboration stage.

The goal of outline collaboration is not to generate a perfect outline in one go, but to continuously converge the material and user feedback into a final-state outline.

Execution principles:

First read the material index, material cards, and loaded writing rules specified by the user.
If the user has already given a clear direction, directly update the outline and do not repeatedly ask follow-up questions.
Each round of user feedback must be absorbed into the same current outline.
Keep only the currently valid titles, positioning, structure, writing constraints, and follow-up actions.
Do not keep rejected titles, chapters, angles, and judgments in the body text.
Do not write the discussion process, revision history, or points of disagreement into the outline unless the user explicitly requests it.

Suggested outline file naming:

01-文章大纲.md

Outline Front Matter:

---
created: YYYY-MM-DD HH:mm:ss
title: {选题或标题}：文章大纲
categories: []
tags: []
content_role:
  - 大纲
---

The outline body should at least include:

# {选题或标题}：文章大纲

## 文章定位

说明目标读者、核心问题、文章承诺和不展开的范围。

## 标题

保留当前确认的标题。如果用户明确确认了标题，不要擅自改动。

## 素材双链索引

按用途列出本大纲实际参考的素材卡，方便后续 AI 或人工写作回溯来源。

- {用途}：[[素材卡 1]]、[[素材卡 2]]

## 核心主张

只保留当前有效判断。

## 正文结构

按阅读路径列出章节，每节写清楚要解决的问题、要保留的判断和可用素材。

## 文章可复用组件

只列真正能降低读者行动成本的模板、清单、提示词或流程。不要为了显得“干货”机械堆工具。

## 写作注意

记录用户明确确认或纠正过的标题偏好、语气、表达边界、读者假设和章节取舍原则。

## 后续动作

说明下一步可以进入初稿、继续补素材、改标题或改结构。

Outline collaboration check:

Target reader check: whether each section serves the target reader and the main thread of the article.
Reader burden check: whether content has been added that would make the target reader feel it is complex, off-topic, or not immediately useful.
Reusable component check: whether templates, checklists, and prompts actually reduce the cost of taking action.
Constraint inheritance check: whether the title, format, tone, and structural preferences the user has explicitly corrected have been written into "Writing Notes".
Material traceback check: whether the material double links in the outline can be matched to real material cards.

Title collaboration rules:

When the user discusses titles, do not only evaluate accuracy; also identify the title function the user wants: attracting clicks, creating a sense of benefit, lowering the threshold, building identity, highlighting a result promise, and so on.
After the user explicitly confirms a title, do not change words, add spaces, change punctuation, or replace expressions without authorization.
By default, the main title (H1 + the title field in Front Matter) does not add spaces between Chinese and English, Chinese and numbers, or Chinese and English words. Example: write "沉淀为skill，让AI替你打工", not "沉淀为 skill，让 AI 替你打工". Body paragraphs, subheadings, and code blocks still add spaces according to general typography conventions. The reason for this preference is that the main title is more like a slogan and promotional text, and compact rhythm and visual continuity matter more than standardized typography.

Pause point:

After the outline is confirmed, stop first and ask whether to proceed to the first draft. Do not automatically jump from outline to finished draft.

8. Quality check

After completion, check:

All material sources specified by the user have been processed.
The save location specified by the user has been followed.
All Markdown has valid Front Matter.
All material cards have source descriptions.
The double-link filenames in the material index match the real filenames.
The material double-link filenames in the outline match the real material cards.
The outline only retains the currently valid structure and judgments, and does not record rejected candidates or the discussion process.
The writing notes in the outline have incorporated the preferences and constraints the user explicitly corrected.
There is no large-scale copying of copyright-protected web content.
Clearly distinguish between "source-confirmed information" and "writing judgments derived from the materials".

AI practical writing rules loading

When the user wants to write an AI practical article, especially when the following signals appear, load the writing rules first:

Aimed at non-technical beginners, AI beginners, and ordinary people.
Requires speaking plainly, staying grounded, and not piling on jargon.
Requires being concise and hitting the point.
Requires being practical, solid, and something readers can follow to get started.
Requires making readers want to save it.
Requires reducing the AI flavor and preserving real human judgment.

Prioritize reading the public style references within this skill:

references/writing-style.md

If the user has their own style document, platform guidelines, or writing samples, you can ask the user to provide additional paths; only read them when the user explicitly provides them.

If the user does not have an existing style document but wants to develop their own writing style, use by default:

./jcm-article-writing-workspace/style/user-writing-style.md

When this file does not exist, you can create an empty template in the user's current project directory for the user to fill in later. Do not guess a private directory on the fly, and do not read any local materials outside this repository by default.

After loading, judge by the "practical beginner-friendly article" standard:

Do not aim for broad and comprehensive; just explain one small point clearly.
Each article solves one specific problem.
Prioritize providing collectible content such as templates, checklists, prompts, processes, and pitfall-avoidance standards.
When a term appears for the first time, it must be translated into plain language.
Structure serves understanding and action; do not write it as an encyclopedia, manual, or training courseware.
When revising, use low-AI-flavor rules for quality checks to avoid smoothness, formulaic patterns, misunderstandings by fictional readers, and excessive completeness.

Draft review (triggered after user confirmation)

After the draft is completed, the main agent must proactively ask the user once whether a review is needed.

You can copy this wording exactly:

初稿已经写完。要不要让另一个 agent 独立审一稿，按照公开文风规则做一次质检？

Only enter the review process after the user explicitly confirms. If the user does not confirm or refuses, skip this section.

Review basis

The review is based only on these materials:

The current skill's references/writing-style.md。
Materials, material indexes, or links provided by the user.
The currently confirmed outline.
The current draft.
Style documents, platform requirements, or rules already filled in under jcm-article-writing-workspace/style/user-writing-style.md in the user's current project directory that are additionally provided by the user.

Do not read local directories not provided by the user. Do not use private knowledge bases, private samples, or other undisclosed files as the default review basis.

Review method

If the environment supports sub-agents, another agent can perform an independent review; if not, the current agent should self-check according to the same basis, but must clearly state that the review basis comes from public style references and user materials.

The review prompt can be written according to the following structure:

你是一个独立审稿 agent，不参与本文写作过程。请按下面流程做一次审稿：

1. 读当前初稿：{初稿文件路径或用户粘贴的初稿}
2. 读当前 skill 的公开文风参考：references/writing-style.md
3. 读用户提供的素材、素材索引、大纲和额外风格要求。
4. 按公开文风参考自行判断要审查哪些方向。如果遇到具体路径、产品功能、价格、入口、模型能力等需要核验的信息，要么读用户提供的来源核实，要么在报告里标“待核实”，不要凭推测下结论。
5. 关注但不限于这些大方向：
   - 信息取舍与一篇只讲一件事。
   - 小白可执行性、减负原则、操作准确性。
   - 标题、小标题、开头、结尾是否服务读者行动。
   - 低 AI 味信号：空泛、套路、过度完整、假装共情、虚构读者误解。
   - 排版规范：短段落、清晰列表、术语翻译、中文标点统一。
   - 真人判断、取舍理由和真实限制。
6. 返回结构化报告，格式如下：

   ## 审稿结论
   一句话总体评价。

   ## 必改（命中硬规则）
   - 位置：{小节/段落/句子定位}
   - 命中规则：{公开文风参考中的规则}
   - 建议改法：{具体改法}

   ## 建议改（可商榷）
   - 位置：{...}
   - 问题：{...}
   - 建议：{...}

   ## 可保留的判断点
   如果发现有的地方表面上像问题但实际服务表达，列出来说明，避免主 agent 误改。

报告必须具体到段落或句子，不要泛泛说“风格有问题”。每条问题都要给改法建议，不要只指出问题。

After receiving the review report

The main agent organizes the report into a concise list for the user, distinguishing two categories: "must change / suggested change."

The user decides which items to implement; do not revise the draft yourself before the user confirms.

If there is content in "judgment points that can be retained," the main agent must restate it to the user to avoid mistakenly changing the user's original judgment.

Output to the user

Keep the final reply concise and explain:

Which material sources were used.
Which directory it was saved to.
The number of material cards.
Which material types were covered.
Whether there are points that could not be verified or need follow-up checking.

Do not paste the full text of all materials in the final reply.