Token导航 LogoToken导航

Agent Skill · 研究检索

hum-narrative(嗡嗡声叙述)

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

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

总安装 441周安装 18GitHub Stars 124下载 141核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/asgard-ai-platform/skills --skill hum-narrative

这个 Skill 是做什么的

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

hum-narrative 用于查找、检索和筛选相关信息,支持基于关键词快速定位结果。适用于叙事结构分析和信息筛选场景。通过 npx skills add 命令从 GitHub 仓库安装,需确认权限范围。使用前建议核实是否会触发联网或文件读写操作。可结合原始 README 继续核验具体功能和使用限制。

来源仓库内路径:skills/hum-narrative

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

hum-narrative 怎么安装?

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

hum-narrative 支持哪些 AI 工具?

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

hum-narrative 需要什么权限?

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

hum-narrative 是免费的吗?

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

hum-narrative 用的人多吗?

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

hum-narrative 安全吗?

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

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

值得选的地方

  • 同时适配 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调用外部服务未明确有提醒
hum-narrative

嗡嗡声叙述 · 本页

441124只读未明确通过

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

SKILL.md 原文

Narrative & Storytelling

Overview

Stories are the most natural human communication format. Narrative structure gives information emotional weight, memorability, and meaning. This skill applies storytelling principles to business contexts: brand stories, presentations, pitches, and change communication.

Framework

IRON LAW: Every Story Needs Tension

A narrative without conflict or tension is a report, not a story. The tension
can be a problem to solve, a gap between current and desired state, or an
obstacle to overcome. Without tension, there's no reason for the audience
to keep listening.

Story Arc (Universal Structure)

  1. Setup (Status Quo): Establish the world, the character, and the normal state
  2. Trigger (Inciting Incident): Something disrupts the status quo — a problem, opportunity, or discovery
  3. Rising Action (Struggle): Attempts to address the disruption, obstacles encountered
  4. Climax (Turning Point): The decisive moment — breakthrough, decision, or revelation
  5. Resolution: The new state of affairs — what changed, what was learned

Brand Story Framework

ElementQuestionExample
Founding mythWhy does this company exist?"We started because we couldn't find X..."
EnemyWhat wrong are you fighting?"The industry treats customers like numbers"
QuestWhat are you trying to achieve?"We're on a mission to make X accessible to everyone"
ValuesWhat principles guide you?"We believe in transparency, simplicity, and..."
TransformationWhat change do you create?"Our customers go from struggling with X to thriving at Y"

Storytelling in Business Contexts

Presentations: Open with a story (Pathos), then transition to data (Logos). "Let me tell you about one customer..." → "And she's not alone — here's the data."

Pitch decks: Problem (tension) → Solution (your product) → Traction (proof the story is working) → Vision (how the story ends)

Change communication: Current state (familiar) → Why change is needed (tension) → Vision of future state (resolution) → How we get there (plan)

Data storytelling: Don't just show charts. Frame them: "We expected X to happen. Instead, Y happened. Here's why, and here's what it means."

Output Format

# Narrative Design: {Context}

## Story Arc
1. **Setup**: {status quo}
2. **Trigger**: {what disrupted it}
3. **Struggle**: {challenges faced}
4. **Climax**: {turning point}
5. **Resolution**: {new state}

## Key Elements
- Tension: {the core conflict}
- Character: {who the audience identifies with}
- Stakes: {what happens if the tension isn't resolved}
- Transformation: {what changes}

## Application
{How to integrate this narrative into the specific communication context}

Examples

Correct Application

Scenario: Brand story for a Taiwanese sustainable packaging startup

  • Setup: "Taiwan produces 8.4 million tonnes of waste per year. Most packaging is used once and discarded."
  • Trigger: "Our founder worked at a packaging factory and watched truckloads of plastic wrap go straight to landfill every week."
  • Struggle: "We spent 2 years and 47 failed prototypes trying to make sugarcane-based packaging that was as durable as plastic."
  • Climax: "Prototype #48 worked. Same durability, fully compostable in 90 days."
  • Resolution: "Now 200+ food brands in Taiwan use our packaging. We've diverted 500 tonnes from landfills."
  • Tension is clear, character is relatable, stakes are tangible ✓

Incorrect Application

  • "Our company was founded in 2019. We sell sustainable packaging. Our revenue is NT$50M." → Facts without narrative structure. No tension, no character, no arc. This is a report, not a story. Violates Iron Law.

Gotchas

  • The customer is the hero, not you: In brand storytelling, the customer should be the protagonist who overcomes challenges with your help. Your brand is the guide (mentor), not the hero.
  • Authenticity > drama: Exaggerated stories backfire when discovered. Use real stories, real data, real people.
  • Cultural narrative norms differ: Western narratives favor individual heroes and linear arcs. East Asian narratives may emphasize collective effort and cyclical patterns. Match the cultural context.
  • Don't force everything into a story: Some information is better delivered as facts, tables, or lists. Use narrative for the emotional frame, not for every data point.
  • Story length must match context: Elevator pitch = 30-second story. Keynote = 15-minute story. Annual report = multi-chapter story. Adjust detail to the format.

References

  • For the Hero's Journey (Campbell/Vogler) structure, see references/heros-journey.md

平台分布

Codex

35.16%
按下载量换算50

Claude

30.49%
按下载量换算43

Cursor

17.65%
按下载量换算25

Gemini CLI

8.27%
按下载量换算12

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills