Token导航 LogoToken导航

Agent Skill · 开发

prose-writing(散文写作)

用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写。它适合让 Agent 提炼结构、补齐章节、统一术语、检查链接或把零散材料整理成可读文档。使用时应保留项目已有事实、命令和路径,不要把未确认的信息写成确定结论;涉及对外文案时,还需要控制语气,避免过度营销或夸大能力。

prose-writing 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为权限未标注;许可证信息还不明确,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 10,477。

总安装 2,230周安装 92GitHub Stars 147下载 729核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/haowjy/creative-writing-skills --skill prose-writing

这个 Skill 是做什么的

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

prose-writing 用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写,适合让 Agent 提炼结构、补齐章节、统一术语或把零散材料整理成可读文档。适用于技术文档编写、内容稿件优化和文案结构重组等场景。支持对现有文本进行格式调整、逻辑梳理和语言润色,保留原始事实。

使用时应避免过度营销或夸大能力,涉及对外文案时需控制语气。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/prose-writing

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    权限没有明确标注,第一次使用时只给一个无关紧要的任务,观察它到底读了哪些文件和网络。

常见问题

6 条

prose-writing 怎么安装?

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

prose-writing 支持哪些 AI 工具?

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

prose-writing 需要什么权限?

权限级别没有明确标注。第一次使用时建议只给无关紧要的任务,观察它实际读写了哪些内容。

prose-writing 是免费的吗?

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

prose-writing 用的人多吗?

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

prose-writing 安全吗?

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

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

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

适不适合你

更适合

  • 已经在用 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有提醒
prose-writing

散文写作 · 本页

2,230147权限未标注未明确通过

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

SKILL.md 原文

Prose Writing

Draft narrative fiction that serves the story's needs. This skill covers craft technique — the how of prose. Project-specific voice, character speech patterns, and formatting conventions come from style files. Read those before writing.

Two Modes

Interactive

Back-and-forth with the author. They describe what they want, you draft, they react, you revise. The conversation IS the feedback loop — don't produce a "final" draft on the first pass. Offer options when the direction is ambiguous. Ask about intent when a scene could go multiple ways.

Autonomous

You receive a brief (scene outline, beat list, emotional arc, relevant context) and produce a draft. No author in the loop — the draft goes to critics next, not to a human. This means:

  • Follow the brief's direction without second-guessing it. The orchestrator already confirmed intent.
  • Make concrete choices rather than hedging. A critic can flag a bad choice; they can't critique a hedge.
  • Write the full scene, not a summary or outline. The output is prose, not planning.
  • Mark places where you made significant interpretive choices (e.g., <!-- CHOICE: interpreted "tense conversation" as passive-aggressive rather than openly hostile -->) so critics and the orchestrator can evaluate your calls.

Scene Entry

Open scenes in the middle of something happening. The reader should orient through action and context, not through setup narration. A character already mid-task, mid-conversation, or mid-thought gives the reader something to track immediately.

Avoid:

  • Weather/setting paragraphs before anything happens
  • Character waking up or traveling to the scene location
  • "The room was..." description blocks
  • Recap of how we got here

The exception is when the setting itself IS the story beat — a character seeing a destroyed city for the first time, or arriving somewhere that changes everything. Then the setting description carries narrative weight.

Scene Purpose

Every scene needs to change something — character knowledge, relationships, power dynamics, stakes, emotional state. If nothing is different at the end than at the beginning, the scene is a candidate for cutting.

Before writing, identify what changes. In interactive mode, ask the author. In autonomous mode, extract it from the brief. If the brief doesn't specify what changes, flag it: <!-- UNCLEAR: brief doesn't specify what changes in this scene -->.

Point of View

Stay in the established POV. First person means the narrator can only report what they perceive, think, and feel — not what other characters are thinking. Third limited means access to one character's interiority per scene.

POV violations are the most common craft error in AI-generated fiction. Watch for:

  • Reporting emotions of non-POV characters as fact ("She felt angry") instead of through observable behavior ("Her jaw tightened")
  • The narrator knowing things they shouldn't (what happened in a room they weren't in)
  • Head-hopping between characters within a scene

Show Through Action

Demonstrate character states through behavior, dialogue, and physical response rather than narrating them directly.

Telling: "He was nervous about the meeting." Showing: "He checked his watch for the third time, then straightened a tie that was already straight."

This doesn't mean never tell. Summary narration is appropriate for:

  • Transitions between important moments
  • Routine actions that don't carry emotional weight
  • Time compression ("The next three weeks passed in a blur of training")

The heuristic: tell for logistics, show for moments that matter.

Dialogue

Dialogue should do at least two things simultaneously: advance the plot AND reveal character, or reveal character AND build tension, or build tension AND seed information. Single-purpose dialogue ("As you know, the reactor is on the third floor") feels flat because real conversation is never purely transactional.

Subtext. Characters rarely say exactly what they mean. They deflect, understate, change the subject, answer a different question than the one asked. The gap between what's said and what's meant is where characterization lives.

Voice differentiation. Each character should sound distinct enough that you could identify the speaker without dialogue tags. This comes from vocabulary, sentence structure, speech patterns, and what they choose to talk about — not from accent spelling or verbal tics bolted on.

Action beats over dialogue tags. "Said" is invisible; use it freely. Avoid creative tags ("he exclaimed," "she retorted") — they draw attention to the tag instead of the dialogue. Use action beats to show how something is said: "She set the cup down carefully. 'That's not what I meant.'"

Pacing

Vary sentence length and structure to control reading speed. Short sentences speed things up — good for action, tension, shock. Longer sentences slow the reader down — good for reflection, description, complex emotion.

Scene-level pacing: alternate between high-tension and lower-tension beats. Sustained intensity becomes numbing. The quiet moment after the crisis is what gives the crisis weight.

Chapter-level pacing: end on forward momentum. Not necessarily a cliffhanger — an unanswered question, a new complication, an emotional shift. Give the reader a reason to continue.

Sensory Detail

Ground scenes in specific sensory details rather than generic description. "The forest" is nowhere. "Pine needles crunching underfoot, the smell of wet bark" is a place.

Use the POV character's sensory priorities. A chef notices smells. A musician notices sounds. A soldier notices exits. What a character pays attention to reveals who they are.

Avoid cataloging all five senses mechanically. One or two vivid, specific details do more work than a comprehensive sensory inventory.

Interiority

The POV character's inner life — thoughts, reactions, memories, associations — is what distinguishes prose fiction from screenplay. Don't neglect it.

But interiority should be specific and revealing, not generic emotional labeling. "She felt sad" is a label. "She kept reaching for her phone to text him before remembering" is interiority that shows the reader something about grief.

In high-action scenes, interiority contracts to fragments — quick reactions, snap judgments. In reflective scenes, it expands. Match the depth of inner experience to the pace of the scene.

Revision Signals

When reviewing your own draft (or receiving critique), watch for these patterns:

  • Redundant beats. Saying the same thing through action, dialogue, AND narration. Pick the strongest delivery and cut the others.
  • Throat-clearing. Opening paragraphs that circle the point before landing on it. Cut to where the real scene starts.
  • Emotional choreography. Characters cycling through emotions in predictable patterns (shock → denial → anger → acceptance) without the specific, messy reality of how people actually process things.
  • Placeholder prose. Competent but generic sentences that could appear in any story. If a sentence could be swapped into a different scene without anyone noticing, it's not doing enough work.

Resources

Style files passed alongside this skill contain project-specific voice guidance — character speech patterns, tonal registers, formatting conventions, scene-type techniques. Read them before drafting. They override general craft advice when they're more specific.

平台分布

Codex

35%
按下载量换算255

Claude

27.13%
按下载量换算198

Cursor

20.55%
按下载量换算150

Gemini CLI

10.27%
按下载量换算75

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

权限未标注

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

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

继续浏览同类 Skills