Token导航 LogoToken导航

Agent Skill · AI 工具

story-sense(故事感)

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

story-sense 是AI 工具类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证为 MIT,第三方扫描已通过,按安装量在AI 工具类的 2,536 个 Skill 里排第 255。

总安装 9,126周安装 392GitHub Stars 67下载 3,199核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/jwynia/agent-skills --skill story-sense

这个 Skill 是做什么的

AI 工具类 Skill 用来扩展助手本身的能力,例如接模型、接检索、接外部服务。

story-sense 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。适用于项目管理和团队协作场景,帮助跟踪代码变更和协作进度。

能够分析仓库活动、代码提交历史和协作动态,提供项目状态洞察。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。可结合来源仓库和原始 README 继续核验具体用法和实现细节。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

story-sense 怎么安装?

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

story-sense 支持哪些 AI 工具?

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

story-sense 需要什么权限?

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

story-sense 是免费的吗?

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

story-sense 用的人多吗?

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

story-sense 安全吗?

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

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

值得选的地方

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

先想清楚的地方

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

适不适合你

更适合

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

不太适合

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

AI 工具类 Skill 对比

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

执行计划 · Codex、Claude

1,515,336173,110只读MIT通过
verification-before-completion

完成前的验证 · Codex、Claude

1,319,472173,121权限未标注MIT通过
subagent-driven-development

子 Agent 驱动开发 · Codex、Claude

1,312,416173,138只读MIT通过
copy-editing

复制编辑 · Codex、Claude

1,209,57625,632只读MIT通过
paywall-upgrade-cro

付费专区升级 cro · Codex、Claude

1,030,17625,617只读MIT通过
story-sense

故事感 · 本页

9,12667只读MIT通过

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

SKILL.md 原文

Story Sense: Diagnostic Skill

Identify what state a story is in and what it needs to move forward. This is not a linear process but a diagnostic model: Assess → Diagnose → Intervene → Reassess.

When to Use This Skill

Use this skill when:

  • Writer is stuck and doesn't know why
  • Story feels broken but root cause unclear
  • Need to evaluate story problems systematically
  • Someone asks "what's wrong with my story?"

Do NOT use this skill when:

  • Writer wants you to write the story (use story-collaborator)
  • Writer wants coaching questions only (use story-coach)
  • Publishing/marketing questions (use book-marketing)

Core Principle

Story Sense is the ability to know what any story needs, regardless of its current state or intended medium.

There's no such thing as "stuck." There's only:

  • Not yet having diagnosed the problem
  • Not yet applying the right intervention

The Story States

State 0: No Story (Blank Page)

Symptoms: Nothing exists yet Interventions: story-idea-generator, elemental genres

State 1: Concept Without Foundation

Symptoms: Have idea but world/characters/plot feel thin Interventions: cliche-transcendence, systemic-worldbuilding, key-moments

State 2: World Without Life

Symptoms: Setting exists but feels like backdrop Interventions: worldbuilding skill suite (belief-systems, economic-systems, governance-systems)

State 3: Flat Non-Humans

Symptoms: Aliens/fantasy species feel like humans in costume Interventions: conlang, species development frameworks

State 4: Characters Without Dimension

Symptoms: Characters serve plot rather than driving it Interventions: character-arc, underdog-unit, positional-revelation

State 4.5: Plot Without Pacing

Symptoms: Scenes work individually but don't accumulate Interventions: scene-sequencing

State 5: Plot Without Purpose

Symptoms: Events happen but don't accumulate meaning Interventions: moral-parallax, key-moments

State 5.5: Dialogue Feels Flat

Symptoms: Characters sound alike, conversations lifeless Interventions: dialogue

State 5.75: Ending Doesn't Land

Symptoms: Story builds well but resolution disappoints Interventions: endings

State 5.85: Draft Not Progressing

Symptoms: Planning done but draft isn't happening Interventions: drafting

State 5.9: Prose Feels Flat

Symptoms: Story works but sentences are functional not memorable Interventions: prose-style

State 6: Draft Complete, Needs Revision

Symptoms: Draft exists but revision feels overwhelming Interventions: revision

State 7: Ready for Evaluation

Symptoms: Story exists but quality uncertain Interventions: sensitivity-check, story-analysis

Decision Tree

Is there anything on the page?
├── NO → story-idea-generator
└── YES → What's the problem?
    ├── Feels generic → cliche-transcendence
    ├── World feels thin → worldbuilding
    ├── Non-humans feel fake → conlang
    ├── Characters flat → character-arc
    ├── Pacing off → scene-sequencing
    ├── Dialogue wooden → dialogue
    ├── Ending weak → endings
    ├── Meaning unclear → moral-parallax
    ├── Draft not progressing → drafting
    ├── Prose flat → prose-style
    └── Draft needs revision → revision

Diagnostic Process

  1. Listen for symptoms - What are they describing as the problem?
  2. Ask clarifying questions - Get specific about where they're stuck
  3. Identify the state - Match symptoms to state list
  4. Name the diagnosis - Explain what you're seeing
  5. Recommend intervention - Point to specific skill
  6. Offer next steps - What should they try first?

Available Scripts

entropy.ts

Injects creative randomness from curated lists.

deno run --allow-read scripts/entropy.ts lies
deno run --allow-read scripts/entropy.ts disasters --count 3
deno run --allow-read scripts/entropy.ts --combo

Lists: lies, ghosts, disasters, dilemmas, professions, locations, collisions, openings

functions.ts

Generates characters from abstract story functions.

deno run --allow-read scripts/functions.ts
deno run --allow-read scripts/functions.ts --setting scifi
deno run --allow-read scripts/functions.ts healer --setting fantasy

Functions: healer, enforcer, keeper_of_secrets, maker, trader, guide, entertainer, death_worker, transgressor

Anti-Patterns

Prescribing Instead of Diagnosing

Fix: Always ask clarifying questions before diagnosing.

Framework Overload

Fix: Recommend one intervention. Expand after reassessment.

Ignoring Writer's Energy

Fix: Balance diagnostic accuracy with what energizes the writer.

Treating Structure as Story

Fix: Keep asking "Does this feel right?" alongside structural diagnosis.

Related Skills

Routes to all fiction skills based on diagnosed state.

平台分布

Claude Code

32.16%
按下载量换算1,029

OpenCode

26.45%
按下载量换算846

Gemini CLI

17.37%
按下载量换算556

Antigravity

12.22%
按下载量换算391

Cursor

7.48%
按下载量换算239

trae

3.22%
按下载量换算103

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills