Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计提醒

cw-brainstorming连续波头脑风暴

Agent Skill

cw-brainstorming 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

3,770

周安装

154

GitHub Stars

147

下载量

1,220
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:cw-brainstorming(连续波头脑风暴)
来源仓库:https://github.com/haowjy/creative-writing-skills
仓库路径:skills/cw-brainstorming
安装命令:
npx skills add https://github.com/haowjy/creative-writing-skills --skill cw-brainstorming
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/haowjy/creative-writing-skills --skill cw-brainstorming

简介

cw-brainstorming 捕获故事构思与创作探索,以工作笔记形式保留模糊选项与灵感标记。

  • 适用于 Codex、Claude、Cursor、Gemini CLI 的创意开发阶段,支持世界构建与角色发展。
  • 记录时不添加未声明细节,保持未来创作灵活性,所有建议均标明来源。
  • 输出为开放式骨架,需用户后续决策转化,避免过度承诺具体情节走向。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Brainstorming Capture

Capture story brainstorming in working note format that preserves creative freedom.

Core Principle

Record brainstorming WITHOUT:

  • Over-elaborating on what was stated
  • Mixing user statements with AI suggestions unmarked
  • Inventing excessive details
  • Constraining future creativity

AI suggestions are valuable but must be clearly marked and kept minimal.

Types of Brainstorming

This skill handles all brainstorming types:

  • Story/plot directions (general narrative exploration)
  • Chapter structure and beats (planning individual chapters)
  • Worldbuilding and lore (magic systems, cultures, history, geography)
  • Character development (motivations, arcs, relationships)
  • Timeline and continuity (chronology, contradictions)

All share core principles (minimal capture, source tagging, preserve vagueness). See references/ for specialized guidance:

  • chapter-planning.md - Capturing beat and scene exploration
  • worldbuilding.md - Exploring fictional world elements (use web search for research)
  • character-development.md - Exploring motivations, arcs, relationships
  • continuity-timeline.md - Timeline tracking and contradiction handling

Critical Rules

1. Minimal Capture Only

Record ONLY what the user explicitly states. Do NOT add elaborations, examples they didn't give, or details to fill gaps.

The problem is mixing, not suggesting:

❌ User: "Character A competes with B" → Capture: "A and B compete for leadership through a tournament with three rounds..." ✅ User: "Character A competes with B" → Capture: "A and B compete" + optional: "Tournament? Political? Trial?"

2. Source Tagging (Simple 3-Tag System)

Default: Untagged = user said it. Most ideas come from the user, so treat them as the default.

ONLY use tags for special context:

  1. <AI>...</AI> - AI suggestions/possibilities (MUST be clearly wrapped)

- Use when offering ideas user didn't state - Keep to 2-3 brief options - Example: <AI>Competition could be: tournament-style, political maneuvering, or trial-based</AI>

  1. <hidden>...</hidden> - Author-only information meant to be revealed later

- Secret character motivations - Planned twists/revelations - Behind-the-scenes reasons unknown to characters/readers yet - Example: <hidden>Z secretly wants them both to fail so he can reclaim leadership</hidden>

When to offer AI suggestions:

  • User asks for ideas
  • User seems stuck
  • Offering brief possibilities to spark creativity

When to stay minimal:

  • User is actively exploring their own ideas
  • Just capturing an ongoing discussion
  • User didn't ask for suggestions

3. Preserve Vagueness

Keep it vague if user leaves it vague:

  • "might create tension" → Record as uncertain
  • "thinking about" → Record as consideration
  • "maybe" → Record as possibility

4. Multiple Options Coexist

Working notes can contain contradictions and multiple possibilities. Don't resolve them - just list the options being considered.

Output Approach

Use whatever structure fits the discussion. Could be:

  • Bullet lists
  • Sections organized by topic
  • Timeline format
  • Character-focused groupings
  • Whatever captures the brainstorm clearly

Essential elements:

  • Minimal capture (user's words, not elaborations)
  • Vagueness preserved
  • AI suggestions wrapped in <AI> tags
  • Author-only info wrapped in <hidden> tags when relevant

Optional sections based on discussion:

  • Open questions to explore
  • Multiple options being considered
  • AI suggestions (if offered)
  • Contradictions to resolve later

Teaching Example: The Distinction

User Says:

"I'm thinking character X and character Y compete for leadership. Maybe this creates tension with character Z who was the previous leader."

✅ Good Capture:

# Leadership Competition Notes

- X and Y compete for leadership
- Z was previous leader
- May create tension with Z (uncertain)

Open questions:
- Form of competition?
- How does Z respond?
- Outcome?

❌ Bad Capture:

# Leadership Competition Arc

X and Y compete for leadership after Z steps down. Z feels threatened by the challenge to his authority.

The competition unfolds in three stages:
1. Announcement and initial positioning
2. First challenge where X demonstrates strength
3. Second challenge where Y shows wisdom
...
[20 more invented beats]

Why bad? Added massive elaboration the user never stated.

✅ Good with AI Suggestions:

# Leadership Competition Notes

- X and Y compete for leadership
- Z was previous leader
- May create tension with Z (uncertain)

Open questions:
- Competition format: <AI>tournament-style? political maneuvering? trial-based?</AI>
- Z's response: <AI>oppose both? support one? stay neutral?</AI>
- Resolution?

✅ Good with Hidden Author Notes:

# Leadership Competition Notes

- X and Y compete for leadership
- Z was previous leader
- May create tension with Z (uncertain)
- <hidden>Z is secretly manipulating both X and Y to destroy each other, planning to reclaim power after they're both discredited</hidden>

Open questions:
- Competition format?
- Outcome?

Why use <hidden>? The manipulation twist is planned for later reveal. Readers/characters don't know yet, but the author needs to track it while brainstorming.

If You're Over-Elaborating

Stop if you're writing:

  • Numbered scene lists
  • Detailed backstories
  • Specific dialogue
  • Precise timelines
  • Multiple paragraphs per point
  • Examples user didn't mention

Wrap AI suggestions in <AI> tags, keep minimal (2-3 options).

Success Check

Good: User says "Yes, that's what I said" Bad: User says "I never said all that"

Notes should feel skeletal and incomplete. That's the point - preserves creative freedom.

After Capturing: Discuss and Explore

DON'T just write notes and stop. After capturing, engage with the user to help develop ideas:

Useful follow-ups:

  • Clarifying questions: "You mentioned tension with Z - are you thinking internal conflict or external confrontation?"
  • Potential directions: "This setup could go a few ways: political intrigue, personal drama, or action-focused. What feels right?"
  • Exploring implications: "If Z opposes them both, how does that change the power dynamics?"
  • Connecting threads: "This competition ties into the earlier succession crisis you mentioned - want to explore that link?"

Keep it conversational:

  • Offer 2-3 possibilities, not exhaustive lists
  • Ask about what excites the user
  • Help clarify vague ideas without over-defining them
  • Point out interesting implications or contradictions

The goal: Help the user think through their ideas, not take over the creative process.

Skills are Composable

Feel free to combine with other skills when helpful (e.g., using cw-official-docs to document finalized worldbuilding, or cw-story-critique to analyze what you're brainstorming).

File Placement (Claude Code)

  1. Check project docs for conventions
  2. Look at where similar content lives
  3. Place near related content
  4. Name: brainstorm-[topic].md
  5. Ask if unclear

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

36.42%
按下载量换算444

Claude

32.73%
按下载量换算399

Cursor

19.27%
按下载量换算235

Gemini CLI

9.47%
按下载量换算116

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills