getting-started-guide

getting-started-guide is a skill for Claude Code from wordflowlab/novel-writer-skills. It costs 42 tokens per session (1,406 once invoked), scanned A, original, MIT.

An introduction guide for starting a novel project with a seven-step process: creative rules, story definition, clarification, planning, tasks, writing, and review.

In plain words
What is it for?
Use it when beginning a novel, learning the workflow, deciding where to start, or understanding how the seven stages fit together.
Why use it?
It gives new authors a clear starting point and explains what each stage is meant to decide.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it when beginning a novel, learning the workflow, deciding where to start, or understanding how the seven stages fit together.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wordflowlab/novel-writer-skills/getting-started
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add wordflowlab/novel-writer-skills --skill getting-started
Clone the repo
git clone --depth 1 https://github.com/wordflowlab/novel-writer-skills

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for getting-started-guide

README.md
[![agentmods](https://agentmods.dev/badge/skills/wordflowlab/novel-writer-skills/getting-started/github.svg)](https://agentmods.dev/skills/wordflowlab/novel-writer-skills/getting-started)
Your own site
<a href="https://agentmods.dev/skills/wordflowlab/novel-writer-skills/getting-started"><img src="https://agentmods.dev/badge/skills/wordflowlab/novel-writer-skills/getting-started/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for getting-started-guide

Your own site · 80×15
<a href="https://agentmods.dev/skills/wordflowlab/novel-writer-skills/getting-started"><img src="https://agentmods.dev/badge/skills/wordflowlab/novel-writer-skills/getting-started.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,406 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00042 $0.01406
Opus 5 $0.00021 $0.00703
Sonnet 5 $0.00008 $0.00281
Haiku 4.5 $0.00004 $0.00141

Measured 12d ago against content hash 32335d38934c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

getting-started-guide scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

templates/skills/quality-assurance/getting-started/SKILL.md · 225 lines

How it starts

The opening of the file, as written. The whole thing — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.

新用户入门引导

激活条件

当用户说出以下内容时自动激活:

  • "我想写小说"
  • "我要开始一个新项目"
  • "怎么使用novel-writer"
  • "从哪里开始"

七步方法论引导

欢迎消息

👋 欢迎使用Novel Writer Skills!

我注意到你要开始一个新的小说项目。
Novel Writer使用系统化的七步方法论,帮助你从想法到完稿。

让我带你快速了解流程:

第1步:/constitution - 创建创作宪法
第2步:/specify - 定义故事规格
第3步:/clarify - 澄清模糊点(5个问题)
第4步:/plan - 制定创作计划
第5步:/tasks - 分解任务清单
第6步:/write - 执行章节写作
第7步:/analyze - 质量验证分析

想要详细了解每一步吗?还是直接开始第1步?

步骤详解(根据需要提供)

【第1步:/constitution】
创建你的创作宪法 - 这是最高原则。
- 核心价值观(你想传达什么?)
- 质量标准(什么算好的章节?)
- 禁忌红线(不能写什么?)

为什么重要:后续所有创作都要符合宪法。

【第2步:/specify】
定义故事规格 - 明确你要写什么。
- 故事概念、类型、主题
- 目标读者、字数、结局
- 必须包含的元素(P0)

为什么重要:规格是技术需求,避免写到一半发现偏题。

【第3步:/clarify】
AI提出5个关键问题,帮你澄清模糊点。
- 针对specification中的不明确之处
- 逼迫你想清楚细节

为什么重要:模糊的规格=模糊的故事。

【第4步:/plan】
制定创作计划 - 技术方案。
- 章节架构、节奏设计
- 关键情节点时间线
- 技术难点的解决方案

为什么重要:计划详细,执行才顺畅。

【第5步:/tasks】
分解任务清单 - 可执行的步骤。
- 每个章节一个任务
- 标记状态(pending/in_progress/completed)
- 追踪进度

为什么重要:大目标拆解成小任务,不overwhelm。

【第6步:/write】
执行写作 - 基于任务清单。
- 自动加载所有context
- 遵循宪法、规格、计划
- 质量自检后保存

为什么重要:这是七步方法论的优势集中体现。

【第7步:/analyze】
质量验证 - 确保一致性。
- 框架检查(结构、节奏)
- 内容检查(一致性、质量)
- 发现问题,建议修复

为什么重要:定期分析,及时调整,避免大返工。

常见问题快速解答

Q: 必须按顺序执行吗?

A: 推荐按顺序,但不强制。

推荐流程:1→2→3→4→5→6→7(循环6-7)

允许跳步:
- 有经验的作者可以跳过/clarify
- 短篇可以简化/plan

不推荐:
- 直接跳到/write(缺少规格和计划,容易写乱)

Q: 七步走完要多久?

A: 取决于故事复杂度。

简单故事(5万字短篇):
- 步骤1-5:2-3小时
- 步骤6-7:执行写作,持续进行

复杂故事(50万字长篇):
- 步骤1-5:1-2天
- 步骤6-7:数月

前期投入换来后期顺畅。

Q: 可以中途修改吗?

A: 当然!

发现规格不对:
→ 修改specification.md
→ 重新运行/plan调整计划

计划需要调整:
→ 修改creative-plan.md
→ 更新tasks.md

这是迭代过程,不是一次定死。

第一次使用建议

从简单项目开始

✓ 推荐:
- 5-10万字的中短篇
- 单一类型(言情/悬疑/历史)
- 简单情节(1-2条主线)

⚠️ 不推荐初次就写:
- 50万字+的长篇
- 多类型融合(如言情+悬疑+奇幻+历史)
- 超复杂世界观

先熟悉流程,再挑战复杂项目。

执行第一个命令

准备好了?让我们开始第1步:

执行命令:/constitution

我会引导你创建创作宪法。
准备回答以下问题:
1. 这个故事你想传达什么核心理念?
2. 你对质量的标准是什么?
3. 有哪些内容是绝对不能写的?

准备好了就输入:/constitution

与workflow-guide的配合

getting-started:
- 初次使用时激活
- 提供完整流程概览
- 回答入门问题

workflow-guide:
- 整个创作过程中持续激活
- 偏离流程时温和提醒
- 提供最佳实践建议

两者互补:
getting-started = 入门教程
workflow-guide = 持续顾问

Read the full file on GitHub · 225 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 225 lines · 42 tokens per session scan A 32335d38934c

Subscribe to this mod's changes

getting-started-guide is a skill published in the GitHub repository wordflowlab/novel-writer-skills (258 stars, last pushed 10mo ago), licensed MIT. It adds 42 tokens to every session and 1,406 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens