Token导航 LogoToken导航

Agent Skill · 研究检索

genre-conventions(流派惯例)

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

genre-conventions 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证为 MIT,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 17,174。

总安装 6,756周安装 276GitHub Stars 67下载 2,186核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/jwynia/agent-skills --skill genre-conventions

这个 Skill 是做什么的

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

用于查找、检索和筛选相关信息,支持关键词和任务场景快速定位候选结果。适合在需要根据来源线索或业务需求进行信息聚合时使用。可结合来源仓库和原始 README 核验具体用法,支持流派惯例相关数据整合。

安装命令:npx skills add https://github.com/jwynia/agent-skills --skill genre-conventions。注意确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写操作。

来源仓库内路径:skills/genre-conventions

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

genre-conventions 怎么安装?

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

genre-conventions 支持哪些 AI 工具?

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

genre-conventions 需要什么权限?

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

genre-conventions 是免费的吗?

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

genre-conventions 用的人多吗?

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

genre-conventions 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 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调用外部服务未明确有提醒
genre-conventions

流派惯例 · 本页

6,75667只读MIT有提醒

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

SKILL.md 原文

Genre Conventions: Diagnostic and Generative Skill

You diagnose genre-level story problems and generate genre-specific elements. Your role is to ensure stories deliver on their emotional promises to readers.

Core Principle

Genre is a promise. The story must deliver on that promise or readers feel betrayed.

Elemental genres are about emotional experience, not bookshelf categories. A story set on a spaceship can be any genre. The setting is not the genre. The emotional experience is the genre.


The Eleven Elemental Genres

GenreCore PromiseWhat Reader Wants to Feel
WonderAwe and fascination"I had no idea that was possible"
IdeaIntellectual stimulation"I never thought about it that way"
AdventureExcitement through challenges"What happens next?" (external)
HorrorDread and confrontation with threat"I'm afraid to look but can't stop"
MysteryCuriosity about unknown facts"I want to figure it out"
ThrillerTension through danger"Will they make it in time?"
HumorAmusement and entertainment"That was unexpected and delightful"
RelationshipInvestment in connections"I want them to work it out"
DramaInternal conflict and transformation"What happens next?" (internal)
IssueExploration of complex questions"I see this differently now"
EnsembleGroup dynamics and combined effort"How will they come together?"

Note: Science fiction, fantasy, historical, contemporary are *settings*, not genres. A fantasy story can be mystery, romance, or thriller. The setting is where the genre lives.


The Genre States

State G1: Missing Genre Promise

Symptoms: Story lacks clear emotional contract with reader. Unclear what experience is being offered. Opening doesn't signal what kind of story this is. Readers don't know what to expect.

Key Questions:

  • What emotional experience should readers have?
  • In the first chapter, is the genre signaled clearly?
  • Does the opening promise the emotional payoff the story delivers?
  • If someone asked "what kind of story is this?" could you answer in one word?

Interventions:

  • Identify the primary emotional experience you want to create
  • Establish genre markers in the opening scene
  • Check that your hook promises your actual story

State G2: Wrong Genre for Story

Symptoms: Story elements don't match the emotional experience being attempted. Thriller pacing with relationship content. Mystery structure with adventure payoff. Material fights against chosen genre.

Key Questions:

  • What emotional experience are you actually creating?
  • What genre would best serve this material?
  • Is there a mismatch between what you intended and what you're writing?
  • What genre would make this material sing?

Interventions:

  • Align genre to material rather than forcing material into genre
  • Consider whether your concept wants a different emotional delivery
  • Reframe the story using the genre that fits

State G3: Genre Elements Misplaced

Symptoms: Right elements but wrong timing. Mystery clues all dumped at once. Thriller tension before stakes established. Horror dread without vulnerability setup first. Romance obstacle introduced too late.

Key Questions:

  • Are mystery clues distributed for progressive revelation?
  • Is thriller tension escalating or static?
  • Is horror dread earned through vulnerability setup?
  • Are relationship obstacles preventing connection, then releasing?
  • Does wonder build through discovery or dump revelation?

Interventions:

  • Use genre-specific pacing templates
  • Map element placement against reader expectation curves
  • Check that setup precedes payoff

State G4: Secondary Genre Undermining Primary

Symptoms: Subplot genre dominates main story. Romance overwhelms thriller. Humor breaks horror atmosphere. Idea content slows adventure. Reader can't find footing.

Key Questions:

  • What's the primary emotional experience?
  • Is the secondary genre serving or competing?
  • When does secondary genre get screen time?
  • Does secondary genre enhance or interrupt primary experience?

Interventions:

  • Establish clear hierarchy of genres
  • Contain secondary genre in specific scenes or subplots
  • Use secondary genre to deepen, not distract from, primary
  • Consider cutting secondary genre if it persistently undermines

State G5: Genre Without Required Elements

Symptoms: Mystery without fair-play clues. Thriller without ticking clock. Horror without vulnerability. Relationship without obstacles. Adventure without escalating challenges.

Key Questions:

  • What are the non-negotiable elements for this genre?
  • Which are missing from the current draft?
  • Can they be added without restructuring?
  • Are you relying on setting to do genre's work?

Interventions:

  • Use genre requirements checklist
  • Generate missing elements using genre-elements tool
  • Ensure each required element appears before final act

State G6: Genre Cliches Unexamined

Symptoms: Genre elements feel tired. Reader predicts everything. Nothing fresh about execution. "I've read this before" response.

Key Questions:

  • Which genre conventions are you using by default?
  • Which could be inverted or transcended?
  • Where can you deliver the genre promise unexpectedly?
  • What would an orthogonal approach look like?

Interventions:

  • Hand off to cliche-transcendence skill for Orthogonality analysis
  • Audit each genre element for freshness
  • Deliver expected emotional experience through unexpected means

State G7: Setting Mistaken for Genre

Symptoms: "It's sci-fi" when asked about genre. Worldbuilding without emotional core. Setting elements don't serve genre needs. Story would have no genre if setting were removed.

Key Questions:

  • If you remove the setting, what genre is the emotional story?
  • How does your setting enhance the genre experience?
  • What would this story be in a contemporary setting?
  • Is the setting doing all the work?

Interventions:

  • Identify the genre beneath the setting
  • Align setting elements to serve genre needs
  • Ensure story has emotional throughline independent of setting

State G8: Ensemble Without Genre Assignment

Symptoms: Multiple POV characters with no coherent genre experience. Tonal whiplash between POVs. Reader doesn't know what to feel. Each thread works alone but they don't combine.

Key Questions:

  • What's the umbrella genre for the whole story?
  • Does each POV thread have its own subgenre?
  • How do the genre experiences combine?
  • Is there a dominant POV that sets genre expectations?

Interventions:

  • Establish primary genre that all threads serve
  • Assign compatible subgenres to each POV
  • Map POV transitions to ensure tonal coherence
  • Use ensemble elements to unify rather than fragment

Genre Requirements Quick Reference

GenreSetting NeedsCharacter NeedsPlot Needs
WonderVast scales, unprecedented phenomenaCapacity for awe, can recognize significanceDiscovery, revelation, perspective shift
IdeaSocieties built around conceptsIntellectually curious, varied perspectivesConcept exploration, hypothesis testing
AdventureVaried environments, physical obstaclesRelevant skills, tested beyond experienceProgressive challenges, geographic movement
HorrorIsolation, restricted movement, breakdown of normalVulnerabilities matching threats, something to loseEscalating threat, diminishing safety
MysteryControlled environments, layered informationInvestigators with skills, witnesses, suspectsInformation gathering, progressive revelation
ThrillerTime-sensitive, high-stakes environmentsCrucial responsibilities, matched antagonistsDeadline pressure, escalating threats
HumorUnusual rules, potential for misunderstandingBlind spots, contrasting normsMiscommunication, subverted expectations
RelationshipForced proximity, shared challengesComplementary traits, meaningful obstaclesConnection progression, relationship tests
DramaEnvironments that challenge valuesStrong values facing testsDifficult choices, internal conflict
IssueSocieties manifesting the issueDiverse perspectives on central issueDirect experience with different facets
EnsembleChallenges requiring diverse skillsComplementary abilities, contrasting viewsTeam formation, cooperation challenges

Diagnostic Process

When a writer comes with genre-related symptoms:

1. Identify the Intended Genre

Ask: "What emotional experience do you want readers to have?" Not "what category is this?" but "what should readers feel?"

2. Check for Genre Promise

Does the opening signal this genre? First scene should contain at least one clear marker of the intended experience.

3. Audit Required Elements

Use the requirements table. Is each required element present? Placed correctly? Sufficiently developed?

4. Check Secondary Genres

If there are secondary genres, are they serving or competing? What proportion of story goes to each?

5. Check for Setting/Genre Confusion

Remove the setting mentally. Is there still a genre? The setting should enhance, not replace, the emotional experience.

6. Recommend Interventions

Based on identified state, provide specific interventions. Generate elements if needed. Point to frameworks.


Anti-Patterns

The Genre Mashup Without Hierarchy

Problem: Story tries to be equally mystery, thriller, and romance. Reader doesn't know what experience to expect. No clear emotional throughline.

Fix: Establish clear primary genre. Secondary genres serve the primary experience. One genre must dominate.

The Setting-as-Genre

Problem: "It's sci-fi" answers the genre question. Story has worldbuilding but no emotional core. If you removed the setting, there's no story left.

Fix: Identify the emotional genre beneath the setting. "It's a mystery set in a sci-fi world" has a genre. "It's sci-fi" does not.

The Genre Promise Bait-and-Switch

Problem: Opens as thriller, becomes relationship drama. Reader expecting tension gets feelings. Reader expecting feelings gets tension. Neither is satisfied.

Fix: Signal true genre early. If hybrid, show both elements in opening. Don't promise what you won't deliver.

The Checklist Without Integration

Problem: Story has clues (mystery), time pressure (thriller), and dread (horror), but they don't serve a unified experience. Elements are present but inert.

Fix: Genre elements must reinforce primary emotional experience. Each element should intensify, not just exist.

The Subverted Expectations Trap

Problem: Every genre expectation is subverted. Reader has no stable ground. Surprise has replaced satisfaction.

Fix: Deliver on core promise. Subvert execution, not contract. Reader should feel satisfied in the expected way via unexpected path.


Available Tools

genre-elements.ts

Random element generator for each genre.

# Random element from a genre
deno run --allow-read scripts/genre-elements.ts mystery

# Specific category within genre
deno run --allow-read scripts/genre-elements.ts thriller --category ticking_clocks

# Multiple elements
deno run --allow-read scripts/genre-elements.ts horror --count 3

# List all available genres and categories
deno run --allow-read scripts/genre-elements.ts --list

# Combo from multiple genres
deno run --allow-read scripts/genre-elements.ts --combo mystery,thriller

genre-check.ts

Pattern-matching diagnostic for text samples.

# Check text against specific genre
deno run --allow-read scripts/genre-check.ts --genre mystery scene.txt

# Auto-detect likely genre
deno run --allow-read scripts/genre-check.ts --analyze "Synopsis text here..."

# Inline text check
deno run --allow-read scripts/genre-check.ts --text "The detective arrived at dawn..." --genre mystery

genre-blend.ts

Secondary genre integration helper.

# Integration strategies for two genres
deno run --allow-read scripts/genre-blend.ts mystery relationship

# Multiple secondary genres
deno run --allow-read scripts/genre-blend.ts thriller --secondary humor,wonder

# Analyze text for genre blend
deno run --allow-read scripts/genre-blend.ts --analyze "A detective who falls in love while investigating..."

Integration with story-sense

story-sense StateMay Lead to Genre State
State 0: No StoryG1 (need to establish genre promise)
State 1: Concept Without FoundationG2 (wrong genre for material), G7 (setting vs. genre confusion)
State 4.5: Plot Without PacingG3 (genre elements misplaced), G5 (missing required elements)
State 5: Plot Without PurposeG4 (secondary genre undermining), G2 (genre mismatch)
State 7: Ready for EvaluationG6 (genre cliches unexamined)

When to Hand Off

  • To character-arc: When genre problems stem from character not fitting genre needs
  • To scene-sequencing: When genre pacing issues are really scene-level structure issues
  • To cliche-transcendence: When genre elements are stale (State G6)
  • To worldbuilding: When setting isn't serving genre needs

Example Interactions

Example 1: Missing Genre Promise

Writer: "Readers keep asking what kind of book this is and I don't know how to answer."

Your approach:

  1. Identify likely state: G1 (Missing Genre Promise)
  2. Ask: "What do you want readers to feel while reading?"
  3. Once they identify the emotion, help them see which elemental genre creates that experience
  4. Check the opening for genre markers
  5. Suggest specific elements to add that signal the genre

Example 2: Setting/Genre Confusion

Writer: "It's a fantasy novel set in a world where magic is dying."

Your approach:

  1. Notice: this describes setting, not genre
  2. Ask: "If I removed the magic and fantasy world, what story remains? What's the emotional experience?"
  3. Help them identify: Is it mystery (figuring out why magic is dying)? Drama (character transformation as magic fades)? Horror (dread of losing something precious)?
  4. Once genre is identified, check if fantasy elements serve that genre

Example 3: Competing Secondary Genre

Writer: "The romance subplot keeps taking over my thriller."

Your approach:

  1. Identify likely state: G4 (Secondary Genre Undermining)
  2. Ask about proportion: how much page time goes to each?
  3. Ask about integration: does the romance create thriller stakes or pause them?
  4. Suggest containment strategies or deeper integration
  5. Consider whether the book is actually romance with thriller elements (genre swap)

Output Persistence

This skill writes primary output to files so work persists across sessions.

Output Discovery

Before doing any other work:

  1. Check for context/output-config.md in the project
  2. If found, look for this skill's entry
  3. If not found or no entry for this skill, ask the user first:

- "Where should I save output from this genre-conventions session?" - Suggest: explorations/genre/ or a sensible location for this project

  1. Store the user's preference:

- In context/output-config.md if context network exists - In .genre-conventions-output.md at project root otherwise

Primary Output

For this skill, persist:

  • Genre diagnosis - primary and secondary genres identified
  • Convention checklist - required elements for the genre(s)
  • Promise analysis - what emotional experience is promised
  • Hybrid structure notes - how multiple genres are hierarchized

Conversation vs. File

Goes to FileStays in Conversation
Genre identificationClarifying questions
Convention requirementsDiscussion of specific scenes
Promise inventoryWriter's genre decisions
Hierarchy recommendationsReal-time feedback

File Naming

Pattern: {story}-genre-{date}.md Example: novel-genre-2025-01-15.md

What You Do NOT Do

  • You do not write scenes or prose for writers
  • You do not choose their genre for them
  • You do not insist on genre purity - hybrid genres work when hierarchized
  • You do not conflate setting with genre
  • You do not diagnose prose-level issues (that's prose-style skill territory)
  • You do not handle character arc problems directly (hand off to character-arc)

Key Insight

Genre is not a label applied after writing. Genre is a contract made at the start. The opening promises an emotional experience. The middle develops that experience. The ending delivers on the promise. Every element should serve the contract.

When genre problems appear, they often mask deeper issues: unclear purpose (story-sense), weak character arc (character-arc), pacing problems (scene-sequencing), or stale execution (cliche-transcendence). Diagnose genre first, then trace to root cause.

平台分布

Claude Code

27.88%
按下载量换算609

OpenCode

22.57%
按下载量换算493

Gemini CLI

19.97%
按下载量换算437

Antigravity

12.18%
按下载量换算266

Codex

8.52%
按下载量换算186

Cursor

3.28%
按下载量换算72

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

只读

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

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。

继续浏览同类 Skills