novel-outline-researcher

Other Community
Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network
Domain
Other
Compatible agents
  • Claude Code
  • Cursor
  • Cline
  • Codex
  • Windsurf
  • Gemini CLI
  • +20
Trust score
88 / 100 · community maintained
Author / version / license
@zhengyunhui123-dev · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No special requirements
Permissions
  • Read-only
  • Write / modify
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-outline-researcher.preview
---
name: novel-outline-researcher
description: 本 Skill 专注「调研与规划」,不撰写章节正文。支持言情、古代、悬疑、科幻等各类小说。目标是帮用户理清接下来小说怎么发展,给出提纲挈领的章节方向。核心原则:先读、先问、再给,不被现有大纲误…
category: other
runtime: no special runtime
---

# novel-outline-researcher output preview

## PART A: Task fit
- Use case: 本 Skill 专注「调研与规划」,不撰写章节正文。支持言情、古代、悬疑、科幻等各类小说。目标是帮用户理清接下来小说怎么发展,给出提纲挈领的章节方向。核心原则:先读、先问、再给,不被现有大纲误导。 用户一旦给出项目名、章节范围或文件路径,必须先读取,再给出任何判断或方案。未读完不可输出章节方案。 只问最关键的 1–3 个问题,不要铺开成问卷。例如: runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “1. 边界与输出模式 / 1.1 边界 / 1.2 输出模式(默认 vs 展开)” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “本 Skill 专注「调研与规划」,不撰写章节正文。支持言情、古代、悬疑、科幻等各类小说。目标是帮用户理清接下来小说怎么发展,给出提纲挈领的章节方向。核心原则:先读、先问、再给,不被现有大纲误导。 用户一旦给出项目名、章节范围或文件路径,必须先读取,再给出任何判断或方案。未读完不可输出章节方案。 只问最关键的 1–3 个问题,不要铺开成问卷。例如: runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “1. 边界与输出模式 / 1.1 边界 / 1.2 输出模式(默认 vs 展开)” 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; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files; 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: 本 Skill 专注「调研与规划」,不撰写章节正文。支持言情、古代、悬疑、科幻等各类小说。目标是帮用户理清接下来小说怎么发展,给出提纲挈领的章节方向。核心原则:先读、先问、再给,不被现有大纲误导。 用户一旦给出项目名、章节范围或文件路径,必须先读取,再给出…
  • 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 “1. 边界与输出模式”, “1.1 边界”, “1.2 输出模式(默认 vs 展开)”, “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-outline-researcher 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 “1. 边界与输出模式 / 1.1 边界 / 1.2 输出模式(默认 vs 展开)” 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; 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.