Agent skill
writing-assistant
Use this skill when the user needs help with personal writing — either starting a new piece from scratch (inspiration/brainstorming) or reviewing and polishing an existing article (proofreading/editing). Invoke immediately when: the user shares an article and asks for feedback, wants to improve their writing style, feels stuck on what to write, wants help structuring a travel piece/TIL note/personal essay, or asks to review Chinese writing quality. Trigger phrases: 帮我改文章, 检查一下, 润色, 校对, 不知道写什么, 帮我构思, 写游记, 记录 TIL, 写点什么. NOT for diary writing (use diary-assistant) or formal business communications.
Install this agent skill to your Project
npx add-skill https://github.com/niracler/skill/tree/main/skills/writing/writing-assistant
Metadata
Additional technical details for this skill
- openclaw
-
{ "emoji": "\u270f\ufe0f", "requires": { "anyBins": [ "markdownlint-cli2" ] } }
SKILL.md
Writing Assistant
写作助手，两种模式：构思引导（从零开始写）和审校打磨（改已有文章）。
注意：日记写作请使用 diary-assistant skill。
Prerequisites
| Tool | Type | Required | Install |
|---|---|---|---|
| markdownlint-cli2 | cli | No | npx markdownlint-cli2 (no install needed, used in proofreading step 6) |
| markdown-lint | skill | No | Included in npx skills add niracler/skill (for repo setup) |
Do NOT proactively verify these tools on skill load. If a command fails due to a missing tool, directly guide the user through installation and configuration step by step.
Mode Selection
| User Intent | Mode | Section |
|---|---|---|
| 「不知道写什么」「帮我构思」「写游记」「记录 TIL」「写点什么」 | Inspiration | Inspiration Mode |
| 「帮我改文章」「检查一下」「润色」「校对一下」「看看文章」 | Proofreading | Proofreading Mode |
If unclear, ask the user.
Inspiration Mode
帮助用户在不知道写什么或如何写下去时，通过启发式提问引导写作。
Core Principles
| Principle | Description |
|---|---|
| One question at a time | Design a TodoList of prompts, ask one by one |
| Confirm before next | User thinks -> writes -> revises -> confirms -> next question |
| Inspire, don't ghostwrite | Use questions to spark thinking, don't decide content direction |
Article Type Detection
| User Intent | Type | Framework |
|---|---|---|
| 「写游记」「记录旅行」 | Travel | Departure -> Journey -> Reflection |
| 「记录 TIL」「今天学到」 | TIL | Context -> Process -> Solution -> Takeaway |
| 「写点什么」「帮我构思」 | General | Trigger -> Viewpoint -> Develop -> Close |
Flow
Detect article type -> List prompt questions -> Ask one by one -> User answers -> Confirm -> Next -> Compose
Pacing
Claude: "Why did you want to visit this place?"
User: [writes answer]
Claude: [confirm/follow-up] -> "OK, next question: what was the first thing you saw when you arrived?"
Frameworks
Each type has a detailed framework with structure and prompt questions. See writing-frameworks.md for full reference.
After the draft is complete, suggest switching to Proofreading Mode for review.
Proofreading Mode
文章审校，提供 6 步审校流程，帮助打磨中文文章。
Core Principles
| Principle | Description |
|---|---|
| Discuss before editing | Propose changes for user to choose, don't edit directly |
| Review by section | Use Markdown headings as checkpoints, 1-2 headings at a time |
| Inspire, don't decide | Use questions to guide draft content, don't decide for user |
6-Step Review Flow
1. Structure -> 2. Reader Context -> 3. Language -> 4. Source Verification -> 5. Style -> 6. Markdown Format
Step 1: Structure Diagnosis
Goal: Ensure clear structure and focused topic
- Break down paragraphs, identify themes
- Propose 2-3 reorganization options, discuss before editing
- Move deleted content to a separate "material.md" file
See structure-review.md
Step 2: Reader Context Check
Core question: "Would a reader be confused here?"
| Issue | Symptom | Fix |
|---|---|---|
| Background assumption | Uses jargon/acronyms without explanation | Add explanation or footnote |
| Self-referential | "It's like that thing..." without explaining | Make description concrete |
| Logic gap | Jumps from A to C | Add transitional explanation |
| Implicit emotion | "It was so..." without setup | Add context first |
| Information gap | Assumes reader knows the backstory | Briefly provide background |
See structure-review.md
Step 3: Language Standards
Based on Yu Guangzhong's "How to Improve Europeanized Chinese":
| Issue | Example |
|---|---|
| Abstract noun as subject | Bad: Income reduction changes life -> Good: He changed his life due to income reduction |
| Verbose phrasing | Bad: Based on this reason -> Good: Therefore |
| Weak verbs | Bad: Make a contribution -> Good: Contribute |
| Preposition pileup | Reduce overuse of linking words |
| Passive voice abuse | Bad: The problem was solved -> Good: The problem is solved |
See chinese-style.md
Step 4: Source Verification
Source priority: Government official > Authoritative media > Industry media > Avoid personal blogs
Pacing: Verify one -> discuss -> write one -> confirm -> next
See source-verification.md
Step 5: Style Consistency
Check against personal writing style:
| Check | Description |
|---|---|
| Signature expressions | "How to put it", "Actually", "A bit..." |
| Tone | Self-deprecating openings, parenthetical commentary |
| Quantification | Use specific numbers for persuasion |
| Bold restraint | Max 3 bold phrases per heading section |
Avoid:
- "Not X... but Y..." pattern (AI-flavored)
- Quoted "humor" metaphors
- Emoji or numbered list openings
- Frequent dashes
---horizontal rules (use headings or numbers for natural transitions)
See personal-style.md
Step 6: Markdown Formatting
npx markdownlint-cli2 article.md # Check
npx markdownlint-cli2 --fix article.md # Auto-fix
Additional manual checks:
- Heading levels are logical (H2->H3, no skipping)
- List format is consistent (all
-or all*) - Code blocks have language labels
Review Pacing
1. Read current section
2. Check against 6 steps
3. Propose suggestions (don't edit directly)
4. Wait for user confirmation
5. After confirmation, move to next section
Key: Wait for confirmation after each section review.
Writing Style Quick Reference
| Element | Requirement |
|---|---|
| Language | Conversational, like chatting with a friend |
| Paragraphs | One topic per paragraph |
| Bold | Only at important turns/insights, max 3 per section |
| Data | Weave into experience, put detailed sources in footnotes |
| Honesty | Admit gaps, mark unfinished parts, keep thinking traces |
Detailed References
- writing-frameworks.md - Inspiration frameworks for travel, TIL, and general articles
- chinese-style.md - Chinese language standards
- structure-review.md - Structure diagnosis and reader context
- source-verification.md - Source verification and footnotes
- personal-style.md - Personal style guide
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
niracler/skill
pinboard-manager
Use this skill for ALL Pinboard bookmark management tasks — this is the go-to skill whenever Pinboard (pinboard.in) is involved. Invoke immediately when the user wants to: audit or reorganize messy tags, check for broken/dead links, identify stale or outdated bookmarks, clean up their bookmark collection, or manage their Pinboard account in any way. Also use when the user says 整理书签, 检查死链, 整理 tag, 书签管理, pinboard cleanup, bookmark audit, tag consistency, timeliness check, pinboard 过时检测. Do NOT trigger for: browser bookmark management, Raindrop.io, or general URL checking without Pinboard context.
niracler/skill
yunxiao
Use this skill for all Alibaba Cloud 云效 (Yunxiao) DevOps operations on codeup.aliyun.com. Invoke IMMEDIATELY when the user wants to: create or manage Merge Requests (MR) on codeup, update work items/tasks in 云效, query MR lists or task status, create version tags via 云效 API, or push code to a codeup remote. Key triggers: 创建 MR, 提交评审, 云效, yunxiao, codeup, 更新任务, 查看任务, 发布版本, 打 tag. Handles both MCP tool mode and aliyun CLI fallback. Do NOT use for GitHub PRs (use git-workflow), Jira, GitLab, or non-Alibaba platforms.
niracler/skill
weekly-report
Use this skill whenever the user wants to write or generate a structured weekly work report (软件研发周报) — the formal 3-section corporate format with 本周工作总结, 下周工作计划, and 其他事项. This skill automatically collects data from git logs, Obsidian diary Work Log entries, schedule YAML files, GitHub PRs, and 云效 MRs/tasks to draft the report. Invoke when the user says 周报, 软件研发周报, 本周工作总结, 写周报, weekly report, end-of-week summary, or asks to prepare a work summary for their manager/team. Do NOT use for personal diary entries, monthly reviews, OKR summaries, meeting notes, or quarterly retrospectives.
niracler/skill
code-sync
Use this skill to batch-sync all git repos across machines — pushing uncommitted changes at end of day or pulling latest at start of day. Invoke when the user wants to sync all repos (not just one), mentions 「下班同步」「上班更新」 「code-sync」, or describes end-of-day push / morning pull across ~/code. Triggers on: "sync all my repos", "end of day sync", "morning update", "push all dirty repos", "pull all projects", 「同步代码」「下班同步」「上班更新」. Do NOT trigger for: single-repo git operations, committing specific files (use git-workflow), general git push/pull questions, or workspace template updates.
niracler/skill
ha-integration-reviewer
Strict Home Assistant integration code review for PR preparation. Covers Quality Scale rules, code style, Config Flow, test coverage, and docs. Invoke immediately when the user says "review my HA integration", "check HA compliance", "HA code review", "HA Quality Scale check", "home assistant PR review", "审查我的 HA 集成", "检查我的代码是否符合 HA 规范", "帮我 review 一下准备提交的代码". Launches parallel check agents across 5 dimensions. Do NOT use for: non-HA code review, configuring HA automations, HACS plugins, or Lovelace card development.
niracler/skill
schedule-manager
(macOS only) Use this skill for ALL Apple Calendar and Reminders management tasks using osascript and reminders-cli, following GTD methodology. Invoke immediately when the user wants to: schedule a meeting or event, add a todo or reminder, check today's agenda, plan the week ahead, do a weekly review, or capture any task they don't want to forget. Also use when the user says 安排会议, 创建提醒, 查看日程, 规划下周, 添加待办, 记一下, 别忘了, 今天要做什么, 周回顾. This is the right skill any time the user wants to interact with macOS Calendar or Reminders apps.
Didn't find tool you were looking for?