Token导航 LogoToken导航

Agent Skill · 研究检索

writing-mentor(写作导师)

用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写。它适合让 Agent 提炼结构、补齐章节、统一术语、检查链接或把零散材料整理成可读文档。使用时应保留项目已有事实、命令和路径,不要把未确认的信息写成确定结论;涉及对外文案时,还需要控制语气,避免过度营销或夸大能力。

writing-mentor 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证为 MIT,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 17,625。

总安装 6,496周安装 224GitHub Stars 85下载 2,475核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:writing-mentor(写作导师)
来源仓库:https://github.com/lyndonkl/claude
仓库路径:skills/writing-mentor
安装命令:
npx skills add https://github.com/lyndonkl/claude --skill 'Writing Mentor'
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/lyndonkl/claude --skill 'Writing Mentor'

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于提供写作指导和反馈建议。writing-mentor 属于研究检索类 Skill,可作为该场景下的辅助能力补充。适合帮助改进表达技巧和内容组织能力。可针对具体段落或全文提出优化方向。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

需结合写作目标和受众特点给出建议。输出结果应作为参考而非唯一解决方案。

来源仓库内路径:skills/writing-mentor

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/lyndonkl/claude --skill 'Writing Mentor';命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

writing-mentor 怎么安装?

在终端执行 npx skills add https://github.com/lyndonkl/claude --skill 'Writing Mentor'。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

writing-mentor 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

writing-mentor 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

writing-mentor 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

writing-mentor 用的人多吗?

公开数据是累计安装 6,496 次,近一周安装 224 次,下载 2,475 次,GitHub 85 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

writing-mentor 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
writing-mentor

写作导师 · 本页

6,49685只读MIT通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Writing Mentor

Table of Contents

Start Here

Workflows

Understand the Situation

Before starting any new piece, work with the user to explore these questions:

  • What are you writing? (genre, length, purpose)
  • Who is your primary audience?
  • What is your reader's state of mind? (what do they know? what do they expect?)
  • What is your core promise in ≤12 words?
  • What must the reader remember if they forget everything else?
  • What's at stake emotionally for the reader?
  • What's at stake practically for the reader?
  • What is your commander's intent? (the single essential goal)
  • Why should the reader care?

Work together to document the intent brief before proceeding.

Full Writing Process (New Piece)

For: User starting from scratch

Copy this checklist and track your progress:

Full Writing Process:
- [ ] Step 1: Plan structural architecture
- [ ] Step 2: Draft with discipline
- [ ] Step 3: Revise in three passes
- [ ] Step 4: Enhance stickiness
- [ ] Step 5: Pre-publishing check

Step 1: Plan structural architecture

Work with user to select and diagram the appropriate structure type (List, Chronological, Circular, Pyramid, etc.). See resources/structure-types.md for complete workflow with 8 structure types, diagrams, and selection criteria.

Step 2: Draft with discipline

Review intent brief and structure diagram together. Remind user that shitty first drafts are good (Lamott)—write without editing. Guide to favor concrete nouns, strong verbs, sensory detail (King), and short declarative sentences (Klinkenborg). Encourage flow—don't stop to perfect, just get words on paper.

Step 3: Revise in three passes

Apply systematic revision: Pass 1 cuts clutter (Zinsser/King), Pass 2 reduces cognitive load (Pinker), Pass 3 improves rhythm (Clark). See resources/revision-guide.md for complete three-pass workflow with specific techniques for each pass.

Step 4: Enhance stickiness

Apply SUCCESs framework (Simple, Unexpected, Concrete, Credible, Emotional, Stories) to make message memorable. See resources/success-model.md for complete workflow, stickiness scorecard (0-18 points), and before/after examples.

Step 5: Pre-publishing check

Run through comprehensive checklist covering content, structure, clarity, style, polish, and final tests. See Pre-Publishing Checklist below for all items before sharing or publishing.

Revision & Polish (Existing Draft)

For: User has draft, needs improvement

Copy this checklist and track your progress:

Revision & Polish:
- [ ] Step 1: Three-pass revision
- [ ] Step 2: Enhance stickiness (optional)

Step 1: Three-pass revision

Apply systematic revision in three passes: Pass 1 cuts clutter (Zinsser/King) by removing weak constructions and cutting 10-25%; Pass 2 reduces cognitive load (Pinker) by fixing garden-paths and improving readability; Pass 3 improves rhythm (Clark) by varying sentences, adding gold-coins, and enhancing flow. See resources/revision-guide.md for complete workflow with specific techniques for each pass.

Step 2: Enhance stickiness (optional)

Apply SUCCESs framework (Simple, Unexpected, Concrete, Credible, Emotional, Stories) to make message more memorable. See resources/success-model.md for complete workflow, stickiness scorecard, and before/after examples.

Structure Planning

For: User has ideas but unsure how to organize

Copy this checklist and track your progress:

Structure Planning:
- [ ] Step 1: Select appropriate structure type
- [ ] Step 2: Create structure diagram
- [ ] Step 3: Place gold-coins strategically

Step 1: Select appropriate structure type

Work with user to understand their content and choose from 8 structure types (List, Chronological, Circular, Dual Profile, Pyramid, Parallel Narratives, etc.). See resources/structure-types.md for philosophy, structure selection criteria, and diagrams for each type.

Step 2: Create structure diagram

Follow the 5-step process to diagram the chosen structure with user's specific content. See Creating Your Own Structure Diagram for step-by-step guidance.

Step 3: Place gold-coins strategically

Identify where to place narrative rewards (gold-coins) to maintain reader engagement, especially in middle sections. See Gold-Coin Placement Strategy for techniques.

Stickiness Enhancement

For: User wants message to be more memorable

Copy this checklist and track your progress:

Stickiness Enhancement:
- [ ] Step 1: Rate current stickiness
- [ ] Step 2: Apply SUCCESs framework
- [ ] Step 3: Re-rate and refine

Step 1: Rate current stickiness

Use the stickiness scorecard to rate the current message on 6 dimensions (0-18 points total). This establishes baseline. See resources/success-model.md for complete scorecard and rating guidance.

Step 2: Apply SUCCESs framework

Work through all 6 principles systematically: Simple (find core), Unexpected (break schemas), Concrete (sensory details), Credible (testable claims), Emotional (make people care), Stories (simulate experience). See detailed guidance on all 6 principles for specific techniques.

Step 3: Re-rate and refine

Score the revised message using the same scorecard. Aim for 12+ points for good stickiness. See before/after examples for transformation patterns.

Pre-Publishing Checklist

Use before sharing or publishing.

Content

  • Core message is crystal clear
  • All facts checked for accuracy
  • Examples are relevant and appropriate
  • Arguments are sound and complete
  • No missing information

Structure

  • Opening hooks readers
  • Flow is logical and smooth
  • Transitions work smoothly
  • Middle section has gold coins
  • Conclusion satisfies

Clarity

  • No jargon (or all jargon explained)
  • No ambiguous pronouns
  • No garden-path sentences
  • Technical accuracy maintained
  • Appropriate for target audience

Style

  • Tone is consistent
  • Voice is appropriate
  • Sentence variety is good (score 7+/10)
  • No clutter remains
  • Active voice predominates

Polish

  • Spelling checked
  • Grammar correct
  • Punctuation proper
  • Formatting consistent
  • Links work (if applicable)

Final Tests

  • Read aloud - does it sound good?
  • Fresh eyes review (if possible)
  • Achieves stated intent
  • Satisfies target audience needs
  • You're proud of it

平台分布

Claude Code

30.74%
按下载量换算761

Codex

23.45%
按下载量换算580

Gemini CLI

18.57%
按下载量换算460

Antigravity

13.5%
按下载量换算334

OpenCode

7.32%
按下载量换算181

Cursor

3.18%
按下载量换算79

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

继续浏览同类 Skills