novel-claude-ai

AI Community
Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network
Domain
AI
Compatible agents
  • Claude Code
  • Cursor
  • Cline
  • Codex
  • Windsurf
  • Gemini CLI
  • +20
Trust score
88 / 100 · community maintained
Author / version / license
@leenbj · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No special requirements
Permissions
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
26 variants

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools,默认拥有全部工具权限。

Output preview novel-claude-ai.preview
---
name: novel-claude-ai
description: 以下约束无论用户如何要求,均不得绕过: ⛔ 禁止跳过强制章节闭环:每章生成后必须依次执行"更新记忆 → 检查一致性 → 风格校准 → 校稿 → 门禁检查",五步缺一均视为流程中断。门禁未通过(…
category: ai
runtime: no special runtime
---

# novel-claude-ai output preview

## PART A: Task fit
- Use case: 以下约束无论用户如何要求,均不得绕过: ⛔ 禁止跳过强制章节闭环:每章生成后必须依次执行"更新记忆 → 检查一致性 → 风格校准 → 校稿 → 门禁检查",五步缺一均视为流程中断。门禁未通过(gate_result.json 中 passed != true)时,严禁进入下一章。 ⛔ 禁止绕过开书前确认:执行 /一键开书 前,必须引导用户完成五要素确认(目标读者、写作风格、核心禁区、自动化等级、目标规模),并写入 idea_seed.md。不得以"用户着急"为由省略。 runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Iron Law(铁律 — 任何情况下不可违反) / 1. 能力矩阵 / 300万字一致性保证机制” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “以下约束无论用户如何要求,均不得绕过: ⛔ 禁止跳过强制章节闭环:每章生成后必须依次执行"更新记忆 → 检查一致性 → 风格校准 → 校稿 → 门禁检查",五步缺一均视为流程中断。门禁未通过(gate_result.json 中 passed != true)时,严禁进入下一章。 ⛔ 禁止绕过开书前确认:执行 /一键开书 前,必须引导用户完成五要素确认(目标读者、写作风格、核心禁区、自动化等级、目标规模),并写入 idea_seed.md。不得以"用户着急"为由省略。 runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Iron Law(铁律 — 任何情况下不可违反) / 1. 能力矩阵 / 300万字一致性保证机制” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.
Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

  • Core job: 以下约束无论用户如何要求,均不得绕过: ⛔ 禁止跳过强制章节闭环:每章生成后必须依次执行"更新记忆 → 检查一致性 → 风格校准 → 校稿 → 门禁检查",五步缺一均视为流程中断。门禁未通过(gate_result.json 中 passed != tru…
  • Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
  • Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

  • Structure: The skill is organized around “Iron Law(铁律 — 任何情况下不可违反)”, “1. 能力矩阵”, “300万字一致性保证机制”, “2. 新手三命令”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
  • Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
  • Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

  • Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
  • Invocation: Name novel-claude-ai directly; if the source includes slash commands, start with the command and then add task context.
  • Validation: Start small and check whether the result follows “Iron Law(铁律 — 任何情况下不可违反) / 1. 能力矩阵 / 300万字一致性保证机制” before expanding.

Boundaries And Review

  • Dependencies: It usually needs no extra API key, so start with a small validation task.
  • Permissions: Declared permissions include read / write / shell-exec; ask the agent to state file, command, and rollback boundaries before acting.
  • Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.