Token导航 LogoToken导航

Agent Skill · 研究检索

story-architecture(故事架构)

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

story-architecture 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为权限未标注;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 37,725。

总安装 1,681周安装 68GitHub Stars 147下载 528核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/haowjy/creative-writing-skills --skill story-architecture

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

story-architecture 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。适用于需要根据关键词或任务场景从来源线索中获取信息的场景。通过 npx skills add 命令安装,需结合原始 README 确认具体用法。

安装前建议检查权限范围、维护状态及是否触发联网或文件操作。可配合来源仓库进一步核验功能细节和使用限制。

来源仓库内路径:skills/story-architecture

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/haowjy/creative-writing-skills --skill story-a…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    权限没有明确标注,第一次使用时只给一个无关紧要的任务,观察它到底读了哪些文件和网络。

常见问题

6 条

story-architecture 怎么安装?

在终端执行 npx skills add https://github.com/haowjy/creative-writing-skills --skill story-architectur…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

story-architecture 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

story-architecture 需要什么权限?

权限级别没有明确标注。第一次使用时建议只给无关紧要的任务,观察它实际读写了哪些内容。

story-architecture 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

story-architecture 用的人多吗?

公开数据是累计安装 1,681 次,近一周安装 68 次,下载 528 次,GitHub 147 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

story-architecture 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
story-architecture

故事架构 · 本页

1,681147权限未标注未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Story Architecture

Structure story at multiple levels so that each scene, chapter, and arc serves the larger narrative. This skill covers structural thinking — how parts relate to wholes, how pacing works across scales, how setup creates payoff. It's not prescriptive about methodology (three-act, hero's journey, kishotenketsu, etc.) because structure should serve the story, not the other way around.

Structural Levels

Stories operate at nested scales. Decisions at one level constrain and enable decisions at others.

Saga/Series — the full story spanning multiple arcs. What's the overarching question or transformation? How do arcs build on each other? Where are the major turning points that redefine what the story is about?

Arc — a self-contained narrative movement, typically spanning multiple chapters. Each arc has its own question, rising tension, and resolution — but also advances the saga-level story. An arc that resolves its own conflict but doesn't change anything at the saga level is filler.

Chapter — a unit of reading. Chapters need internal momentum (something changes by the end) and external momentum (the reader wants to continue to the next one). Not every chapter is a complete dramatic unit — some are part of a multi-chapter sequence.

Scene — the fundamental building block. A scene happens in a specific time and place, involves specific characters, and changes something. Scenes that don't change anything are candidates for cutting or combining.

What Makes Structure Work

Causation Over Sequence

"And then" is not structure. "Therefore" and "but" are. Events should cause or complicate each other, not merely follow each other. When you outline, check whether each beat is caused by the previous one or merely comes after it.

A simple test: can you reorder the scenes without the story breaking? If yes, the structure is a sequence, not a plot.

Stakes That Escalate

Each structural level should raise the stakes from the previous one. The first arc's conflict should matter less than the second arc's. Within an arc, early chapters establish what could be lost; later chapters threaten it.

Escalation doesn't always mean bigger explosions. Stakes can escalate emotionally (losing a friend matters more than losing a fight), morally (the right choice becomes harder), or informationally (each revelation makes the situation more complex).

Setup and Payoff

Every significant payoff needs setup, and every significant setup needs payoff. The setup doesn't need to be obvious — in fact, the best setups are invisible until the payoff arrives. But they need to exist. A twist that works relies on the reader being able to look back and see it was built.

Tracking setup/payoff across arcs is one of the hardest structural problems in long-form fiction. Maintain explicit records of open setups (foreshadowing, Chekhov's guns, unanswered questions, promises to the reader) and check them regularly.

Tension and Release

Sustained tension becomes numbness. The reader needs breathing room — not absence of conflict, but variation in intensity. A quiet conversation after a battle. A comedic beat after an emotional gut-punch. Structure these intentionally; the rhythm of tension and release is what gives a story its emotional shape.

This applies at every scale. Within a scene: not every line should be at maximum intensity. Within a chapter: alternate high and low beats. Within an arc: the climax lands harder when preceded by a quieter stretch.

Arc Design

An arc is defined by a central question — something the characters (and reader) need answered. The question creates tension, the arc's events explore it from different angles, and the resolution provides an answer (which may itself raise new questions for the next arc).

Arc Components

Hook — what pulls the reader (and characters) into this arc? The inciting event, the new complication, the revelation that changes everything. This doesn't have to be the first scene — an arc can ease in through character moments before the central tension arrives.

Rising complications — each event makes the central question harder to answer, not easier. If the protagonist keeps winning, tension drops. Complications should be logical consequences of previous choices, not random obstacles.

Midpoint shift — somewhere in the middle, something changes the nature of the conflict. The protagonist learns something that reframes the problem. An ally becomes an antagonist. The stakes change category. Without this, arcs sag in the middle.

Crisis — the moment of maximum tension where the protagonist must make a defining choice. The choice should be genuinely difficult — not between good and bad, but between competing values or between two kinds of loss.

Resolution — the aftermath of the crisis. Not just "what happened" but "what changed." The resolution of one arc's question should set up the next arc's question.

Arc Pacing

Arcs have their own rhythm independent of chapter structure. An arc might span 5 chapters or 15. The structural beats above aren't evenly distributed — rising complications take the most space, the crisis is often compressed, and the resolution can be brief.

When pacing feels off, check whether the arc's structural beats are landing where they need to. A midpoint shift in chapter 2 of a 10-chapter arc means the second half has to sustain tension without its primary tool for renewal.

Chapter Design

Chapters are reading units, not structural units. A chapter can contain multiple scenes or one long scene. It can advance the arc's plot or develop character while the plot pauses. What makes it work as a chapter is internal completeness and external pull.

Internal completeness — something should change within the chapter. The reader should feel they received something — a revelation, an emotional shift, a new complication, a moment of connection. Chapters that are purely transitional ("getting from A to B") feel like filler.

External pull — the chapter should end with forward momentum. An unanswered question, a new threat, an emotional shift that demands exploration. This doesn't mean every chapter needs a cliffhanger — subtler forms of pull work too. The reader should want to know what happens next.

Scene Design

A scene is the smallest structural unit: a continuous sequence in a specific time and place. Every scene should earn its presence.

Questions to ask about a scene:

  • What changes? (If nothing, cut it or combine it with another scene.)
  • Whose scene is it? (Which character drives the action or has the most at stake?)
  • What does the reader learn? (New information, new character depth, new tension.)
  • How does it connect to the arc? (Advance, complicate, deepen, or resolve.)

Scenes that only exist to convey information can usually be cut — find a scene that's already doing something and deliver the information there.

Outline vs. Discovery

Some writers plan extensively before drafting. Some discover the story by writing it. Most do some of both. This skill doesn't advocate for either approach — it provides structural thinking that applies regardless.

For planners: outlines are hypotheses, not contracts. If the draft reveals that the outline's structure doesn't work, change the outline. Serving the outline instead of the story produces technically correct but emotionally dead fiction.

For discovery writers: structural awareness during drafting helps you recognize when you've wandered into a dead end. You don't need a detailed outline, but knowing what your current arc's central question is helps you evaluate whether a scene is exploring that question or avoiding it.

Diagrams

When structure gets complex — parallel timelines, multiple POV threads, arc overlap — visual representations help. Mermaid diagrams can map:

  • Arc timelines showing overlap and dependencies
  • Character relationship evolution across arcs
  • Plot thread tracking (which threads are open, where they resolve)
  • Chapter-to-arc mapping

Use diagrams when the structure is too complex to hold in your head, not as decoration.

Common Structural Problems

Saggy middle. The arc's complications aren't actually complicating — they're repetitive variations of the same obstacle. Fix by adding a midpoint shift that changes the nature of the conflict.

Rushed ending. The resolution doesn't have space to land. Fix by either extending the resolution or simplifying what needs resolving.

Filler arcs. An arc that resolves internally but doesn't advance the saga. Every arc should change the story's permanent state — relationships, power dynamics, character understanding, stakes.

Disconnected scenes. Scenes that are individually interesting but don't connect causally. "This happened, then this happened" instead of "this happened, which caused this."

Stakes plateau. The story's stakes stop escalating. Later arcs should matter more than earlier ones — not necessarily bigger, but deeper. If arc 3 feels less consequential than arc 1, the structure is deflating.

平台分布

Codex

39.02%
按下载量换算206

Claude

29.82%
按下载量换算157

Cursor

19.68%
按下载量换算104

Gemini CLI

8.95%
按下载量换算47

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

权限未标注

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills