novel-writer-cn▌
yangsonhung/awesome-agent-skills · updated Jun 1, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
专业的小说创作支持，涵盖构思、规划、写作到修改的全流程。
小说写作助手
专业的小说创作支持，涵盖构思、规划、写作到修改的全流程。
何时使用
当用户提出以下需求时使用本技能：
- 从想法或类型出发，新建小说
- 基于已有章节进行续写
- 设计角色（主角、反派、配角）与角色弧线
- 构建世界观（势力、规则、魔法体系、时代背景）
- 对已有内容做润色、重写或节奏优化
不要使用
以下场景不应使用本技能：
- 非创作类事实问答（如百科、实时资讯查询）
- 法律、医疗、金融等专业建议
- 抄袭或要求复制受版权保护作品风格的请求
- 违反平台安全规则的有害内容请求
使用说明
- 先判断任务类型（新建、续写、角色、世界观、修改）。
- 先问最少必要信息，再开始输出。
- 按本文件对应流程章节执行。
- 优先复用
references/与assets/templates/中的材料。 - 保持视角、语气、角色动机与上下文一致。
- 输出前做一次情节连贯性与语言质量自检。
工作流程
第一步：确定需求类型
根据用户请求识别任务类型：
| 任务类型 | 用户示例 | 操作 |
|---|---|---|
| 新小说创作 | "帮我写一部科幻小说" | 进入新建小说流程 |
| 章节续写 | "给这个故事续写一章" | 进入续写流程 |
| 角色设计 | "设计一个反派角色" | 进入角色设计流程 |
| 世界观构建 | "构建一个魔法体系" | 进入世界观构建流程 |
| 内容修改 | "修改这段对话" | 直接修改优化 |
新建小说
创作流程
1. 沟通基础信息 → 2. 构建框架 → 3. 角色设计 → 4. 章节规划 → 5. 开始写作
1. 沟通基础信息
询问用户以下关键信息（不要一次问太多）：
必问：
- 小说类型（科幻/奇幻/悬疑/言情/武侠等）
- 故事核心概念或灵感
- 目标篇幅（短篇/中篇/长篇）
可选（可逐步询问）：
- 主角设定
- 想要的情感基调
- 特殊要求
2. 构建框架
根据收集的信息，使用三幕结构创建故事大纲：
- 第一幕（25%）：建置 → 激励事件 → 踏上旅程
- 第二幕（50%）：挑战 → 中点转折 → 危机 → 准备
- 第三幕（25%）：高潮 → 解决 → 新常态
详细结构指导：参见 references/story-structure.md
3. 角色设计
为核心角色创建角色卡：
- 主角：核心欲望、核心恐惧、角色弧线
- 反派：动机、与主角的冲突
- 关键配角：功能定位
详细角色指导：参见 references/character-development.md
4. 章节规划
根据大纲规划具体章节，每章明确：
- POV（视角）
- 场景地点
- 情节要点
- 与整体故事的连接
5. 开始写作
按照规划逐章写作，注意：
- 保持视角一致
- 场景细节生动
- 对话推动情节
- 适当埋设伏笔
续写章节
续写前准备
-
理解现有内容
- 阅读已有章节
- 梳理当前情节进展
- 确认角色状态和关系
-
确认续写方向
- 下一章的目标是什么？
- 需要发生什么事件？
- 情感走向如何？
续写要点
- 承接上文情节和氛围
- 保持角色性格一致
- 推进主线或支线
- 结尾留有钩子
角色设计
设计流程
-
确定角色功能
- 主角/反派/配角？
- 在故事中的作用？
-
填充角色维度
- 基础信息（姓名、年龄、外貌）
- 核心欲望和恐惧
- 优点和缺点
- 独特标识（说话方式、习惯动作）
-
设计角色弧线
- 开始状态
- 经历的变化
- 结束状态
-
建立关系网
- 与其他角色的关系
- 冲突和羁绊
使用模板：assets/templates/character-card.md
世界观构建
构建层次
-
物理世界
- 地理环境
- 气候生态
- 重要地点
-
社会体系
- 政治结构
- 经济系统
- 文化习俗
-
特殊系统
- 魔法体系（奇幻）
- 科技设定（科幻）
- 武功系统（武侠）
-
历史背景
- 重要事件
- 传说神话
构建原则
- 服务故事：只构建故事需要的内容
- 内部一致：规则不自相矛盾
- 展示而非讲述：通过情节展现世界
详细指导：参见 references/worldbuilding.md
使用模板：assets/templates/world-bible.md
类型特定指导
不同类型有不同侧重点：
| 类型 | 核心要点 | 详细指导 |
|---|---|---|
| 科幻 | 科学设定内在逻辑 | genre-guides.md#科幻小说 |
| 奇幻 | 魔法规则与代价 | genre-guides.md#奇幻小说 |
| 悬疑 | 线索公平、真相意外 | genre-guides.md#悬疑推理 |
| 言情 | 角色化学反应、情感层次 | genre-guides.md#言都市 |
| 武侠 | 武功体系、江湖恩怨 | genre-guides.md#历史武侠 |
写作技巧
关键技巧速览：
- 叙事视角：第一人称/第三人称限知/全知，根据故事需要选择
- 场景构建：时间+地点+人物+冲突+变化
- 对话写作：推动情节、展现性格、有潜台词
- 节奏控制：张弛有度，高潮后需缓冲
- 悬念伏笔：提前埋设、后期回收
详细技巧：参见 references/writing-techniques.md
可用模板
| 模板 | 用途 |
|---|---|
| outline.md | 完整小说大纲 |
| character-card.md | 角色设定卡 |
| world-bible.md | 世界观设定 |
| chapter.md | 章节规划与写作 |
输出规范
大纲输出
- 结构清晰，层次分明
- 关键节点明确
- 便于后续扩展
正文输出
- 中文写作，使用中文标点
- 段落适当分段
- 对话格式规范
- 避免过于书面化，保持可读性
格式示例
第一章 暗夜降临
城市的霓虹灯在雨幕中模糊成一片光晕。林远站在天台边缘，任由冰冷的雨水打湿他的风衣。
"你来了。"身后传来一个熟悉的声音。
他转过身，看到一个黑影正从楼梯口走来。
How to use novel-writer-cn on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add novel-writer-cn
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches novel-writer-cn from GitHub repository yangsonhung/awesome-agent-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate novel-writer-cn. Access the skill through slash commands (e.g., /novel-writer-cn) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★58 reviews- ★★★★★Pratham Ware· Dec 24, 2024
Keeps context tight: novel-writer-cn is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Sophia Dixit· Dec 20, 2024
novel-writer-cn has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Chaitanya Patil· Dec 16, 2024
novel-writer-cn reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Hassan Srinivasan· Dec 16, 2024
novel-writer-cn has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Zaid Nasser· Dec 4, 2024
Solid pick for teams standardizing on skills: novel-writer-cn is focused, and the summary matches what you get after install.
- ★★★★★Sophia Chawla· Nov 23, 2024
We added novel-writer-cn from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★William Ghosh· Nov 11, 2024
Keeps context tight: novel-writer-cn is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Zaid Torres· Nov 11, 2024
novel-writer-cn is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★William Gill· Nov 11, 2024
novel-writer-cn fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Piyush G· Nov 7, 2024
I recommend novel-writer-cn for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 58