Token导航 LogoToken导航

Agent Skill · 待分类

flash-fiction(快闪小说)

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

flash-fiction 是待分类类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在待分类类的 11,209 个 Skill 里排第 977。

总安装 6,053周安装 260GitHub Stars 67下载 2,122核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/jwynia/agent-skills --skill flash-fiction

这个 Skill 是做什么的

这个 Skill 的分类还没最终确定,用法以来源仓库的说明为准。

flash-fiction 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态、代码变更或协作事项进行整理。

通过 npx skills add 命令从指定仓库安装,需结合原始 README 核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/flash-fiction

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

flash-fiction 怎么安装?

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

flash-fiction 支持哪些 AI 工具?

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

flash-fiction 需要什么权限?

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

flash-fiction 是免费的吗?

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

flash-fiction 用的人多吗?

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

flash-fiction 安全吗?

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

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

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

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理待分类类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

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

待分类类 Skill 对比

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

infsh CLI · Codex、Claude

4,374,576382权限未标注未明确未收录
ai-video-generation

AI 视频生成 · Codex、Claude

4,313,376382调用外部服务未明确有提醒
lark-openapi-explorer

云雀 OpenAPI 浏览器 · Codex、Claude

2,064,1209,011需要联网未明确有提醒
lark-workflow-standup-report

Lark 工作流程站立报告 · Codex、Claude

2,041,6328,978需要联网未明确通过
use-my-browser

使用我的浏览器 · Codex、Claude

1,848,49140操作浏览器未明确未通过
flash-fiction

快闪小说 · 本页

6,05367只读未明确通过

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

SKILL.md 原文

Flash Fiction Diagnostic

Purpose

Diagnose and fix problems in flash fiction and micro fiction (typically under 1500 words). Flash fiction demands exceptional craft efficiency—every word must serve multiple purposes. This skill identifies which dimension needs attention when a piece isn't working.

Quick Reference

StateSignalCore Issue
FF1Opening doesn't hookStructure/Pacing problem
FF2Characters feel thinCharacter compression failure
FF3Beginning/ending disconnectFrame weakness
FF4Everything on surfaceSubtext missing
FF5Prose feels flatImagery/figurative language weak
FF6Setting genericSensory detail lacking
FF7Theme absent or preachyThematic development off
FF8Words don't singLanguage precision/rhythm issues
FF9Something feels "off"Logical consistency breach

Diagnostic States

FF1: Structure & Pacing Failure

Symptoms:

  • Opening doesn't grab
  • Middle sags or rushes
  • Ending feels abrupt or dragged
  • Word count not distributed well
  • Arc feels incomplete

Diagnostic Questions:

  1. Does the first sentence create immediate engagement?
  2. Is there a clear turning point?
  3. Does each paragraph advance multiple purposes (plot + character + theme)?
  4. Is the scope appropriate for the word count?
  5. Is information released at optimal moments?

Interventions:

  • Map the arc: beginning → rising action → climax → resolution
  • Calculate word distribution across sections
  • Strengthen opening hook (in medias res, mystery, declaration)
  • Ensure ending provides closure while leaving resonance
  • Cut any paragraph that only does one thing

Transformation Pattern:

WEAK: "Sarah had been working at the firm for three years when she found the file."
STRONG: "The file had no label—just a smudge of what looked like dried blood along its edge."

FF2: Character Compression Failure

Symptoms:

  • Characters feel generic or interchangeable
  • Too much backstory exposition
  • Character change feels unearned
  • Relationships explained rather than shown
  • No sense of life beyond the page

Diagnostic Questions:

  1. Is each character introduced through revealing action?
  2. Can history be inferred without explicit backstory?
  3. Do defining objects/mannerisms reveal essence?
  4. Is the character arc shown through parallel actions?
  5. Do relationships emerge through interaction, not explanation?

Interventions:

  • Replace generic description with character-specific detail
  • Convert backstory exposition to implications
  • Ensure first action reveals personality
  • Show change through decision pattern shifts
  • Establish relationships through what's unspoken

Transformation Pattern:

WEAK: "James had PTSD from the war. He moved to escape memories."
STRONG: "James flinched at the turkey platter's clatter, hand reaching for the phantom sidearm.
He'd chosen this town for its population sign: 827 souls—small enough to hear rumors
of strangers before meeting them."

FF3: Beginning/Ending Frame Weakness

Symptoms:

  • Opening and closing feel disconnected
  • No sense of journey despite brevity
  • Ending doesn't fulfill opening's promise
  • First/last images don't resonate
  • Structure feels arbitrary

Diagnostic Questions:

  1. What does the opening promise the reader?
  2. Does the ending fulfill or meaningfully subvert that promise?
  3. Is there a first/last image relationship (echo, transformation, contrast)?
  4. Does the ending feel both surprising and inevitable?
  5. What emotion persists after reading?

Interventions:

  • Identify the implicit contract the opening creates
  • Ensure closing image relates to opening image
  • Consider circular structure (return with transformation)
  • Strengthen final sentence for resonance
  • Check that emotional journey is complete

Transformation Pattern:

WEAK ENDING: "So they decided not to sell. They were happy. The end."
STRONG ENDING: "Daniel returned the FOR SALE sign to the garage, laid it beside the smaller
one from his childhood treehouse. Some prices, they'd decided, were too steep to calculate."

FF4: Subtext Missing

Symptoms:

  • Everything stated explicitly
  • No layers beneath surface
  • Readers don't participate in meaning-making
  • Backstory dumped, not implied
  • No iceberg effect

Diagnostic Questions:

  1. What is stated that could be implied?
  2. What is strategically left unsaid?
  3. Are there meaningful gaps for readers to fill?
  4. Does the visible portion suggest invisible depth?
  5. Is ambiguity purposeful or accidental?

Interventions:

  • Convert explicit statements to implications
  • Create strategic gaps (narrative ellipsis)
  • Withhold information for revelation impact
  • Apply iceberg theory: show tip, imply mass below
  • Ensure backstory emerges through objects/actions, not explanation

Transformation Pattern:

EXPLICIT: "John never recovered from his divorce. He felt bitter about Maria leaving him."
IMPLIED: "John twisted his wedding ring finger, a reflex unchanged by three years and
the absence of metal. The man at the next table laughed, and John recognized
the laugh before the face."

FF5: Imagery & Figurative Language Weak

Symptoms:

  • Prose feels flat or utilitarian
  • Metaphors cliched or absent
  • No pattern to imagery
  • Symbols heavy-handed or missing
  • Descriptions don't resonate

Diagnostic Questions:

  1. Are comparisons fresh and precise?
  2. Do metaphors/similes serve multiple purposes (character + theme + emotion)?
  3. Is there an imagery pattern that develops?
  4. Are symbolic objects naturally integrated?
  5. Is there balance between concrete and abstract?

Interventions:

  • Replace clichéd comparisons with original ones
  • Ensure figurative language reveals character perspective
  • Build related image patterns that develop
  • Select symbolic objects that can transform meaning
  • Ground abstract concepts in concrete imagery

Transformation Pattern:

FLAT: "The factory was abandoned and looked sad."
RICH: "Machinery hulked under dust shrouds, metal teeth gleaming in fractured light
between boarded windows. No one suggested splitting up."

FF6: Setting & Sensory Detail Lacking

Symptoms:

  • Location generic or absent
  • Only visual sense engaged
  • Setting doesn't serve character/theme
  • Atmosphere missing
  • Environment feels like backdrop, not participant

Diagnostic Questions:

  1. How quickly is the reader oriented in specific time/place?
  2. Are multiple senses engaged?
  3. Does setting reveal character without stating it?
  4. Does environment reinforce theme?
  5. Is atmospheric mood established through concrete detail?

Interventions:

  • Replace generic settings with specific, revealing locations
  • Incorporate non-visual senses (sound, smell, touch, taste)
  • Make setting details reveal character relationship to place
  • Align physical environment with thematic concerns
  • Embed mood in concrete details, not stated atmosphere

Transformation Pattern:

GENERIC: "The coffee shop was busy. People sat drinking coffee."
SPECIFIC: "The Fallout Shelter Café's concrete walls trapped steam from twenty
underemployed grad students' laptops, their whispered theories competing
with grinding beans and Ella Fitzgerald's crackled vinyl."

FF7: Thematic Development Off

Symptoms:

  • Theme absent or unclear
  • Theme stated, not embodied
  • Didactic/preachy tone
  • Single perspective dominates
  • Ending oversimplifies

Diagnostic Questions:

  1. Is the theme identifiable without being heavy-handed?
  2. Does theme emerge from character and situation (not imposed)?
  3. Are multiple perspectives on the theme represented?
  4. Is thematic content conveyed through concrete details?
  5. Does the conclusion deepen rather than simplify?

Interventions:

  • Embody theme in action and object, not statement
  • Show theme through specific circumstances, then let readers generalize
  • Include multiple viewpoints on the thematic question
  • Replace "character realized that..." with demonstrating action
  • Preserve complexity in the conclusion

Transformation Pattern:

STATED: "Carl realized that trust was essential for relationships."
EMBODIED: "Carl handed her the combination to the safe where he kept
his mother's letters, then turned away so he wouldn't see her expression."

FF8: Language Precision & Rhythm Issues

Symptoms:

  • Weak verbs (walked, went, was)
  • Vague nouns (thing, stuff, area)
  • Unnecessary modifiers
  • Sentence monotony
  • No musicality

Diagnostic Questions:

  1. Does each verb precisely capture the specific action?
  2. Are nouns concrete and specific?
  3. Does each modifier meaningfully sharpen understanding?
  4. Are sentence lengths and structures varied?
  5. Do sound patterns enhance (alliteration, rhythm, cadence)?

Interventions:

  • Replace weak verbs with precise, energetic alternatives
  • Substitute general nouns with specific, sensory-rich ones
  • Eliminate redundant or decorative modifiers
  • Vary sentence structure for rhythm and emphasis
  • Develop sound patterns that match meaning

Transformation Pattern:

WEAK: "She went across the field quickly."
PRECISE: "She slashed through the wheat, scattering husks."

MONOTONOUS: "He opened the door. He looked inside. He saw nothing. He closed the door."
VARIED: "He opened the door and looked inside. Nothing. The door clicked shut as he turned."

FF9: Logical Consistency Breach

Symptoms:

  • Something feels "off" even if hard to identify
  • Physical impossibilities
  • Timeline contradictions
  • Characters know things they shouldn't
  • Rules established then broken

Diagnostic Questions:

  1. Do objects function consistently?
  2. Does the timeline allow events as described?
  3. Do characters know only what they could realistically know?
  4. Are physical limitations respected?
  5. If rules are bent, is it consistent?

Interventions:

  • Map physical movement and verify possibility
  • Chart events chronologically with durations
  • Check character knowledge boundaries
  • Verify cause-effect proportionality
  • Document world rules and check consistent application

Transformation Pattern:

IMPOSSIBLE: "She finished her shift at midnight, drove 30 miles home,
cooked dinner, and was in bed by 12:15."
POSSIBLE: "She finished at midnight. The apartment she'd rented
closer to the hospital meant she could be cooking within minutes."

Evaluation Checklist

For any flash fiction piece:

Structure (FF1)

  • First sentence hooks
  • Each paragraph serves multiple purposes
  • Clear arc despite compression
  • Scope matches word count

Character (FF2)

  • Characters introduced through revealing action
  • History inferred, not explained
  • Change shown through action

Frame (FF3)

  • Opening/closing images relate
  • Ending fulfills or transforms promise
  • Emotional journey complete

Subtext (FF4)

  • More implied than stated
  • Strategic gaps for reader participation
  • Iceberg effect achieved

Imagery (FF5)

  • Fresh figurative language
  • Imagery patterns develop
  • Symbols naturally integrated

Setting (FF6)

  • Specific time/place established quickly
  • Multiple senses engaged
  • Setting serves theme

Theme (FF7)

  • Theme emerges, not stated
  • Multiple perspectives present
  • Complexity preserved

Language (FF8)

  • Precise verbs
  • Concrete nouns
  • Sentence variety
  • Musicality present

Consistency (FF9)

  • Physics work
  • Timeline possible
  • Knowledge boundaries respected

Anti-Patterns

The Miniature Novel

Trying to compress a novel-length story into flash length. Flash fiction is not a summary—it's a complete experience in miniature. Choose a scope that fits.

The Twist Dependency

Relying entirely on a surprise ending. If the story only works with the twist, the preceding content isn't pulling weight. The journey should matter.

The Vignette Trap

Beautiful prose without narrative movement. Flash fiction still needs change—something must be different by the end, even if subtle.


Integration Points

Inbound:

  • From story-sense: After identifying story state
  • From drafting: During first draft creation
  • From revision: For line-level polish

Outbound:

  • To prose-style: For deeper language work
  • To dialogue: For conversation problems
  • To endings: For closure issues

Complementary:

  • scene-sequencing: Single-scene pacing
  • character-arc: Compressed transformation
  • cliche-transcendence: Fresh imagery generation

Word Count Guidance

LengthNameFocus Priority
<100DrabbleSingle image, single moment, maximum compression
100-500Micro fictionOne scene, one shift, implication over statement
500-1000Flash fictionSmall arc, 1-2 scenes, full iceberg effect
1000-1500Sudden fictionMultiple scenes possible, more character room
1500-2500Short shortApproaching short story territory

Sources

Frameworks synthesized from flash fiction craft analysis, incorporating principles from:

  • Hemingway's iceberg theory
  • John Gardner on the "vivid and continuous dream"
  • Compression techniques from poetry applied to prose

平台分布

Codex

35.41%
按下载量换算751

Claude

28.57%
按下载量换算606

Cursor

18.28%
按下载量换算388

Gemini CLI

9.39%
按下载量换算199

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills