Token导航 LogoToken导航

Agent Skill · 开发

story-check(故事检查)

story-check 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

story-check 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证为 MIT,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 15,404。

总安装 599周安装 24GitHub Stars 28下载 194核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/bybren-llc/story-systems-template --skill story-check

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

story-check 用于处理 GitHub 仓库、Issue、Pull Request 等协作信息,适合整理代码变更与项目状态。适用于围绕仓库状态或协作事项进行信息梳理的场景。通过 npx skills add 命令安装,需参考原始 README 了解具体调用方式。

安装前应确认权限范围、维护状态及是否会执行命令或读写文件。建议结合来源仓库验证其实际功能和集成限制。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

story-check 怎么安装?

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

story-check 支持哪些 AI 工具?

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

story-check 需要什么权限?

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

story-check 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

story-check 用的人多吗?

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

story-check 安全吗?

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

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

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

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
story-check

故事检查 · 本页

59928只读MIT通过

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

SKILL.md 原文

Story Check Skill

Invocation Triggers

Apply this skill when:

  • Evaluating a screenplay draft
  • Identifying story weaknesses
  • Preparing for rewrites
  • Validating story fundamentals before submission

The 12 Story Questions

Here are twelve great questions you should ask yourself about your script/story while you are developing it. You should actually chart it out.

Question 1: Story Elements

What are the elements of my story?

  • What is my story's concept?
  • What genre is my story?
CONCEPT: ___________________________________
GENRE: ___________________________________

Question 2: Message

What do I want to say with my script or story?

  • The state of the world?
  • Relationships?
  • Governments?
  • Religions?
  • Life in general?
  • People?
THEME/MESSAGE: ___________________________________

Question 3: Audience Reaction

How will audiences or readers react to my story?

  • Interesting?
  • Believable? Is it a true story?
  • Credible?
  • Compelling?
CriterionRating (1-5)Notes
Interesting
Believable
Credible
Compelling

Question 4: Beginning

Where does my story begin?

  • What is the setup?
  • Is the protagonist in a crisis?
  • Have you established your world? The rules?
  • The restrictions?
SETUP: ___________________________________
WORLD RULES: ___________________________________

Question 5: Ending

Where does my story end?

  • What is the outcome or resolution? And why?
  • Do you answer any and all questions presented?
  • Did you fulfill the premise of the story?
RESOLUTION: ___________________________________
QUESTIONS ANSWERED: [ ] Yes [ ] Partial [ ] No
PREMISE FULFILLED: [ ] Yes [ ] No

Question 6: Rising Tensions

Are there rising tensions?

  • Are there surprises?
  • How does the conflict escalate?
  • Is there a climax?
SURPRISE COUNT: ___
ESCALATION PATTERN: ___________________________________
CLIMAX: ___________________________________

Question 7: Characters

Who are my characters?

  • Are they likable?
  • Interesting? Unique or different?
  • Bigger than life?
  • Will an audience care about them?
CharacterLikableInterestingUniqueCare Factor

Question 8: Protagonist

What or who is my protagonist like?

  • Can audiences empathize with them?
  • What do they want?
  • What are their goals in life? Needs?
  • What's at stake for them?
  • Are they tied to the problem they face?
  • Are they in a position of no turning back?
EMPATHY: [ ] Strong [ ] Moderate [ ] Weak
WANT: ___________________________________
NEED: ___________________________________
STAKES: ___________________________________
POINT OF NO RETURN: Page ___

Question 9: Motivation

What are my characters' motivations?

  • Are these motivations shown?
  • Justified or unjustified?
  • Built into the story?
PROTAGONIST MOTIVATION: ___________________________________
SHOWN ON SCREEN: [ ] Yes [ ] No
JUSTIFIED: [ ] Yes [ ] No
BUILT INTO STORY: [ ] Yes [ ] No

Question 10: Antagonist

Who or what is the antagonist in my story?

  • Why are they trying to stop your protagonist?
  • Is the antagonist a worthy foe?
  • What drives them?
  • What do they want or need?
ANTAGONIST: ___________________________________
MOTIVATION: ___________________________________
WORTHY FOE: [ ] Yes [ ] No
WANT: ___________________________________

Question 11: Over-Explanation

Do I over-explain my story?

  • Is everything spelled out too clearly?
  • Is the setup "messy" and too busy?
  • Do events get explained or unfold dramatically?
  • Do too many key events take place off screen?
IssuePresent?Page(s)
Over-explanation
Messy setup
Told not shown
Key events off screen

Question 12: Believability

If my story and characters are fictitious, can I now believe that they are real?

BELIEVABILITY SCORE: ___/10
AREAS TO IMPROVE: ___________________________________

Story Check Summary Template

## Story Check Summary: [TITLE]

### PASS/FAIL Assessment
| Question | Status | Notes |
|----------|--------|-------|
| 1. Elements | | |
| 2. Message | | |
| 3. Audience Reaction | | |
| 4. Beginning | | |
| 5. Ending | | |
| 6. Rising Tensions | | |
| 7. Characters | | |
| 8. Protagonist | | |
| 9. Motivation | | |
| 10. Antagonist | | |
| 11. Over-Explanation | | |
| 12. Believability | | |

### Critical Issues
1. ___________________________________
2. ___________________________________
3. ___________________________________

### Recommended Actions
1. ___________________________________
2. ___________________________________
3. ___________________________________

### Overall Assessment
[ ] Ready for submission
[ ] Needs minor revisions
[ ] Needs significant rewrite
[ ] Fundamental story issues

Validation Checklist

  • All 12 questions answered honestly
  • Issues documented with specific page references
  • Action items prioritized
  • Overall assessment reflects reality

平台分布

Cursor

27.81%
按下载量换算54

Claude Code

21.43%
按下载量换算42

openhands

15.21%
按下载量换算30

kilo

12.54%
按下载量换算24

windsurf

7.99%
按下载量换算16

zencoder

3.5%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

继续浏览同类 Skills