story-consistency-monitor

wordflowlab/novel-writer-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/wordflowlab/novel-writer-skills --skill story-consistency-monitor
0 commentsdiscussion
summary

被动监控:当你写作或讨论故事时,我会自动交叉参考:

skill.md

故事一致性监控

自动检查系统

本技能监控什么

角色一致性

  • 物理特征:眼睛颜色、身高、年龄、疤痕
  • 性格:行动符合已建立的角色
  • 知识:角色只知道他们应该知道的
  • 成长:变化与角色弧线一致

世界规则

  • 魔法/科技系统:力量的使用一致
  • 地理:距离和地点保持稳定
  • 社会规则:文化和习俗不矛盾
  • 物理法则:已建立的规则不随机打破

时间线逻辑

  • 事件顺序:A 在逻辑上发生在 B 之前
  • 时间流逝:角色适当地老化
  • 同时事件:多 POV 时间线对齐
  • 历史一致性:过去的引用保持一致

如何工作

被动监控:当你写作或讨论故事时,我会自动交叉参考:

  1. characters/ 目录中的角色档案
  2. worldbuilding/ 目录中的世界构建文档
  3. spec/tracking/timeline.json 中的时间线数据
  4. 之前章节的内容

不需要你采取任何行动 - 监控在后台进行。

当检测到问题时

警报格式

当我检测到潜在不一致时,我会用以下方式提醒你:

⚠️ 一致性检查警报

问题:角色特征不匹配
位置:当前章节,第3段
参考:characters/mary-chen.md,第15行

当前文本:"玛丽的绿色眼睛眯起..."
已建立特征:"眼睛颜色:蓝色"(在第3章中设定)

可能的解决方案:
1. 将当前文本改为"蓝色眼睛"
2. 如果你要修改设定,更新角色档案
3. 这是一个有相似名字的不同角色?

你想让我自动修复这个,还是你更愿意自己处理?

严重程度级别

级别 图标 行动 示例
关键 🔴 立即停止并修复 角色突然知道他们不应该知道的秘密信息
警告 ⚠️ 尽快修复 角色的惯常言语模式改变了
注意 📝 考虑检查 时间线感觉压缩

与 Novel-Writer 命令集成

/write 期间

  • 在生成内容时进行实时一致性检查
  • 对关键问题的即时警报
  • 自动参考规格文档

/analyze 期间

  • 全面的一致性报告
  • 所有累积的警告和注意事项
  • 建议的修复按严重性排序

/track 期间

  • 使用经过验证的信息更新追踪数据
  • 标记不一致以供手动审查
  • 维护一致性历史

配置

严格程度级别

你可以调整一致性检查的严格程度:

严格模式(非奇幻的默认):

  • 标记所有矛盾
  • 执行真实世界物理
  • 时间线必须完全合乎逻辑

灵活模式(推荐用于奇幻/科幻):

  • 允许"酷炫规则"例外
  • 魔法/科技可以弯曲现实
  • 允许艺术许可,但会通知

最小模式

  • 只标记关键矛盾
  • 专注于角色和主要情节点
  • 让小的不一致通过

禁用特定检查

如果某些不一致是有意的:

"请为梦境序列禁用时间线检查 - 
它们有意是非线性的。"

常见误报

有时我会标记实际上正确的东西:

有意的矛盾

示例:角色谎报眼睛颜色 修复:在角色档案中添加评论:"// 眼睛实际上是蓝色的,告诉人们是绿色的"

不可靠的叙述者

示例:第一人称叙述者记错事件 修复:在宪法中注明:"不可靠的叙述者 - 记忆不一致是有意的"

时间跳跃

示例:角色的年龄突然增加 修复:在章节中明确说明时间跳跃:"三年后..."

最佳实践

保持参考文档更新

一致性检查器只能和你的文档一样好:

  • 特征变化时更新角色档案
  • 清楚地记录世界规则
  • 使用 /timeline 命令维护时间线文件

及时处理警报

不要让一致性问题累积:

  • 立即修复关键警报
  • 在写作会话结束时审查警告
  • 在修订阶段批处理注意事项

/track 一起使用

一致性检查 + 追踪系统 = 强大组合:

  • /track --check 运行深度一致性验证
  • /track --fix 可以自动修复简单问题
  • 定期使用两者(每 5-10 章)

检查类别详解

角色一致性检查

物理描述

✓ 检查:身高、体重、年龄、发色、眼色
✓ 检查:疤痕、纹身、独特标记
✓ 检查:服装风格、配饰

行为模式

✓ 检查:言语模式是否一致
✓ 检查:反应是否符合性格
✓ 检查:决策是否符合价值观
✓ 检查:技能/能力是否一致

知识状态

✓ 检查:角色知道什么时候知道的
✓ 检查:他们不知道不应该知道的秘密
✓ 检查:记忆与已建立事实一致

世界规则检查

魔法/科技系统

✓ 检查:力量在已建立限制内使用
✓ 检查:代价/成本一致应用
✓ 检查:规则不为了情节便利而改变
✓ 检查:例外有前期暗示

地理和距离

✓ 检查:地点在地图上保持一致
✓ 检查:旅行时间合理
✓ 检查:气候与地理匹配
✓ 检查:地标不移动

社会和文化

✓ 检查:文化规范一致
✓ 检查:语言和方言保持稳定
✓ 检查:社会结构不随机改变
✓ 检查:宗教/信仰保持一致

时间线检查

事件序列

✓ 检查:原因发生在结果之前
✓ 检查:角色不在他们不能在的地方
✓ 检查:事件在合理的时间范围内发生

时间流逝

✓ 检查:角色适当地老化
✓ 检查:季节按顺序改变
✓ 检查:怀孕/康复需要适当的时间
✓ 检查:技能习得需要练习时间

多POV同步

✓ 检查:同时事件从不同POV匹配
✓ 检查:时间跳跃在POV之间对齐
✓ 检查:没有POV知道其他POV的未来

自动修复功能

对于某些简单问题,我可以提供自动修复:

自动修复类型

拼写变化

检测:角色名字拼写不一致
建议:标准化为最常见的拼写
行动:全局查找并替换(经你批准)

数字不一致

检测:角色年龄在章节间不匹配
建议:基于时间线计算正确年龄
行动:更新到正确数字

时间线冲突

检测:事件日期与已建立时间线冲突
建议:调整日期以适应已知序列
行动:更新时间线参考

报告和追踪

一致性报告

定期(或根据要求),我会生成:

## 一致性报告 - [日期]

### 章节范围:章节 1-15

### 检测到的问题

#### 关键(必须修复)
1. 第12章:角色知道只在第14章揭示的信息
   - 修复:重写第12章场景或移动第14章揭示更早

#### 警告(应该修复)
1. 第8章:角色的眼睛颜色从蓝色变为绿色
   - 修复建议:将第8章更新为蓝色或更新角色档案
   
2. 第10章:从首都到边境的旅行只用了1天(之前建立为3天)
   - 修复建议:添加时间跳跃或调整天数

#### 注意事项(考虑检查)
1. 第5章:角色反应似乎不符合特征
   - 审查:这是有意的成长还是不一致?

### 统计
- 总检查:456
- 问题发现:8
- 自动修复:3
- 需要审查:5

### 一致性得分:94%

追踪历史

我维护发现和修复的一致性问题的历史:

  • 有助于识别模式
  • 防止重复错误
  • 显示随时间的改进
  • 对修订有用

与其他技能协作

配合 Writing Techniques Skills

对话一致性

  • 检查角色声音是否保持
  • 验证言语模式
  • 标记不符合特征的对话

场景一致性

  • 验证设定细节
  • 检查物理可能性
  • 确认时间流逝

配合 Genre Knowledge Skills

类型惯例一致性

  • 确保类型规则应用一致
  • 检查陷阱是否一致避免
  • 验证节奏模式

记住:一致性不是关于完美 - 它是关于读者的信任。当世界规则可靠时,读者沉浸其中。当规则似乎随意改变时,他们被拉出体验。我在这里帮助维持这种信任。

你总是有最后的决定权 - 如果不一致是艺术选择,告诉我,我会停止标记它。

how to use story-consistency-monitor

How to use story-consistency-monitor on Cursor

AI-first code editor with Composer

1

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 story-consistency-monitor
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/wordflowlab/novel-writer-skills --skill story-consistency-monitor

The skills CLI fetches story-consistency-monitor from GitHub repository wordflowlab/novel-writer-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/story-consistency-monitor

Reload or restart Cursor to activate story-consistency-monitor. Access the skill through slash commands (e.g., /story-consistency-monitor) 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

GET_STARTED →

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. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 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

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.641 reviews
  • Carlos Dixit· Dec 20, 2024

    I recommend story-consistency-monitor for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • William Yang· Dec 12, 2024

    We added story-consistency-monitor from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Rahul Santra· Nov 19, 2024

    I recommend story-consistency-monitor for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Sakura Khanna· Nov 3, 2024

    Solid pick for teams standardizing on skills: story-consistency-monitor is focused, and the summary matches what you get after install.

  • Carlos Haddad· Oct 22, 2024

    story-consistency-monitor has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Pratham Ware· Oct 10, 2024

    Useful defaults in story-consistency-monitor — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Kabir Agarwal· Sep 13, 2024

    story-consistency-monitor reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Sakshi Patil· Sep 5, 2024

    story-consistency-monitor has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • William Huang· Sep 5, 2024

    Keeps context tight: story-consistency-monitor is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Kabir Ndlovu· Sep 5, 2024

    story-consistency-monitor has been reliable in day-to-day use. Documentation quality is above average for community skills.

showing 1-10 of 41

1 / 5