writing-assistant

Name: writing-assistant
Author: yunshu0909

Writing Community

Repo stars 656
Author updated Live
Author repo yunshu_skillshub

Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network

Domain: Writing
Compatible agents: Claude Code
Cursor
Cline
Codex
Windsurf
Gemini CLI

+20
Trust score: 88 / 100 · community maintained
Author / version / license: @yunshu0909 · no license declared
Token usage: Lean
Setup complexity: Plug-and-play
External API key: Not required
Operating systems: Unspecified (assume cross-platform)
Runtime requirements: No special requirements
Permissions: Read-only
Write / modify
Network behavior: Local-only
Install commands: 26 variants

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview writing-assistant.preview

---
name: writing-assistant
description: 但根据你对选题的清晰度，会走不同的分支： [阶段00] 诊断：观点清不清楚？ │ ├─ [阶段03] 框架讨论 - 打磨和组织框架 │ └─ [阶段04] 内容产出 - 根据框架写文章 └─→…
category: writing
runtime: no special runtime
---

# writing-assistant output preview

## PART A: Task fit
- Use case: 但根据你对选题的清晰度，会走不同的分支： [阶段00] 诊断：观点清不清楚？ │ ├─ [阶段03] 框架讨论 - 打磨和组织框架 │ └─ [阶段04] 内容产出 - 根据框架写文章 └─→ 模糊（有很多想法但不知道讲什么） runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “核心流程 / 流程概览 / 调度规则” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “但根据你对选题的清晰度，会走不同的分支： [阶段00] 诊断：观点清不清楚？ │ ├─ [阶段03] 框架讨论 - 打磨和组织框架 │ └─ [阶段04] 内容产出 - 根据框架写文章 └─→ 模糊（有很多想法但不知道讲什么） runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “核心流程 / 流程概览 / 调度规则” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.

SKILL.md SKILL.md

---
name: writing-assistant
description: 但根据你对选题的清晰度，会走不同的分支： [阶段00] 诊断：观点清不清楚？ │ ├─ [阶段03] 框架讨论 - 打磨和组织框架 │ └─ [阶段04] 内容产出 - 根据框架写文章 └─→…
category: writing
source: yunshu0909/yunshu_skillshub
---

# writing-assistant

## When to use
- 但根据你对选题的清晰度，会走不同的分支： [阶段00] 诊断：观点清不清楚？ │ ├─ [阶段03] 框架讨论 - 打磨和组织框架 │ └─ [阶段04] 内容产出 - 根据框架写文章 └─→ 模糊（有很多想法但不知道讲什么） 三个关键…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.

## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.

## Execution rules
- Organize steps around “核心流程 / 流程概览 / 调度规则” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.

## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.

Evidence boundary and execution chain

The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.

skill "writing-assistant" {
  input      -> user goal + target files + boundaries + acceptance criteria
  context    -> 核心流程 / 流程概览 / 调度规则
  rules      -> SKILL.md triggers / order / output contract
  runtime    -> no special runtime | read files, write/modify files | mostly runs locally
  guardrails -> usually needs no extra API key + small-sample validation + diff/log review
  output     -> copyable result + checklist + next iteration
}

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: 但根据你对选题的清晰度，会走不同的分支： [阶段00] 诊断：观点清不清楚？ │ ├─ [阶段03] 框架讨论 - 打磨和组织框架 │ └─ [阶段04] 内容产出 - 根据框架写文章 └─→ 模糊（有很多想法但不知道讲什么）三个关键步骤：选题 → 框架…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “核心流程”, “流程概览”, “调度规则”, “文件结构”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name writing-assistant directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “核心流程 / 流程概览 / 调度规则” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

写作助手

核心流程

三个关键步骤：选题 → 框架 → 内容

但根据你对选题的清晰度，会走不同的分支：

用户提出主题或想法
    │
    ↓
[阶段00] 诊断：观点清不清楚？
    │
    ├─→ 清晰（知道要讲什么）
    │    ├─ [阶段03] 框架讨论 - 打磨和组织框架
    │    └─ [阶段04] 内容产出 - 根据框架写文章
    │
    └─→ 模糊（有很多想法但不知道讲什么）
         ├─ [阶段01] 思维挖掘 - 把想法倒出来
         ├─ [阶段02] 选题确定 - 从想法中找核心
         ├─ [阶段03] 框架讨论 - 打磨和组织框架
         └─ [阶段04] 内容产出 - 根据框架写文章

流程概览

阶段	名称	触发条件	目标	详细文件
00	诊断	用户提出想法	快速判断观点清晰度	`stages/00-diagnosis.md`
01	思维挖掘	观点模糊	把零散想法倒出来，记录成洞察	`stages/01-mining.md`
02	选题确定	洞察足够	从洞察中锁定核心选题和灵魂句	`stages/02-topic.md`
03	框架讨论	选题确定（无论哪个分支）	打磨和组织文章框架，确保逻辑清晰	`stages/03-framework.md`
04	内容产出	框架确定	根据框架写成1000字左右的文章	`stages/04-writing.md`

调度规则

当前阶段如何判断：

进入阶段00（诊断） — 用户刚开始，说出了想法或选题
进入阶段01（思维挖掘） — 诊断判断：观点还不够清晰，有很多想法但不知道讲什么
进入阶段02（选题确定） — 洞察收集足够，需要从中提炼出核心选题
进入阶段03（框架讨论） — 选题已经清晰，需要打磨框架结构
进入阶段04（内容产出） — 框架已经确定，准备写文章

每个阶段开始时：

告诉用户当前在哪个阶段
读取对应的阶段文件，按照里面的步骤执行
这个阶段的目标是什么、会做什么事

文件结构

writing-assistant/
├── SKILL.md                    # 主文件（触发、流程、调度规则）
├── stages/
│   ├── 00-diagnosis.md         # 诊断阶段
│   ├── 01-mining.md            # 思维挖掘（仅当观点模糊时）
│   ├── 02-topic.md             # 选题确定（仅当观点模糊时）
│   ├── 03-framework.md         # 框架讨论（通用）
│   └── 04-writing.md           # 内容产出（通用）
└── templates/
    ├── framework-template.md   # 框架讨论的记录模板
    └── article-template.md     # 内容产出时参考

核心原则

不浪费时间：观点清晰就不挖掘，直接框架
保证质量：框架讨论是必须的，确保逻辑和表达
模块化复用：框架和内容两个模块通用，无论哪个分支都会用到
用户掌控：用户随时可以说"继续"或"停止"，进度由用户控制

注意事项

阶段00的诊断要快速，3-5个问题就能判断清晰度
思维挖掘不要急，让用户尽量倒干净想法
框架讨论时，重点是打磨"读者为什么要读"和"逻辑顺序"
内容产出时，保持用户的原话风格和口吻

Install command

One-click installPick a runner, click Copy, paste into your terminal, press enter

npx skills add yunshu0909/yunshu_skillshub/writing-assistant -y

Open general install guide

View skill source

Works with

Claude Code
Cursor
Cline
Codex
Windsurf
Gemini
OpenCode
Roo Code
AAide
+Augment
GitHub Copilot
OpenClaw
KKiro
Junie
WWarp
Goose
Trae
Kilo Code
OpenHands
Amp
Zencoder
CContinue
AIAider
CodeBuddy
CodeGeeX
Replit Agent

Security audit

88 / 100

Community

未声明 license/许可。
未声明 version。
未限定 allowed-tools，默认拥有全部工具权限。

Metadata

Source: github
yunshu0909/yunshu_skillshub
中文

More by @yunshu0909

Category & tags

Category Writing