Token导航 LogoToken导航

Agent Skill · 待分类

prose-distill(散文精华)

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

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

总安装 1,032周安装 43GitHub Stars 28下载 344核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/laurigates/claude-plugins --skill prose-distill

这个 Skill 是做什么的

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

prose-distill 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。适用于代码审查、项目进度跟踪和协作事项梳理等开发协作场景。

支持从指定仓库提取 Issue、PR 等协作数据,并生成结构化摘要。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

prose-distill 怎么安装?

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

prose-distill 支持哪些 AI 工具?

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

prose-distill 需要什么权限?

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

prose-distill 是免费的吗?

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

prose-distill 用的人多吗?

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

prose-distill 安全吗?

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

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

值得选的地方

  • 同时适配 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操作浏览器未明确未通过
prose-distill

散文精华 · 本页

1,03228只读未明确通过

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

SKILL.md 原文

/prose:distill

Distill verbose text to its concentrated essence — the art of compression without loss.

When to Use This Skill

Use this skill when...Use something else when...
Text is wordy and needs tighteningYou need to change tone or register (use prose-tone)
Redundant phrases need removingYou need to restructure document flow (use prose-structure)
User says "condense", "tighten", "shorten"You need to adapt for a specific audience (use prose-audience)
Preserving all meaning while reducing lengthSummarizing (lossy) rather than distilling (lossless)

Core Principles

Distillation is lossless compression of natural language. Every sentence in the output must preserve the information content of the input. The goal is approaching the Shannon limit of the message — boiling off redundancy to leave concentrated meaning.

The Hierarchy of Cuts

Apply in this order. Each level removes less essential material:

  1. Redundant phrases — saying the same thing twice in different words
  2. Filler words — "actually", "basically", "essentially", "really", "very", "quite", "rather"
  3. Hedge words — "somewhat", "arguably", "it could be said that", "in a sense"
  4. Throat-clearing — opening phrases that delay the point ("It is worth noting that", "It should be mentioned that")
  5. Nominalizations — noun forms where verbs are stronger ("make a decision" → "decide", "perform an analysis" → "analyze")
  6. Passive constructions — where active is clearer and shorter
  7. Prepositional chains — "the result of the analysis of the data" → "the data analysis result"
  8. Weak verbs + adverbs — replace with a single precise verb ("moved quickly" → "darted")

What to Preserve

  • Technical precision and domain terminology
  • Necessary qualifications and nuance
  • Logical structure and argument flow
  • Voice and character (distill the style, don't flatten it)
  • Specific details, numbers, names, references

Parameters

Parse $ARGUMENTS:

  • If text is provided inline, distill it directly
  • If a file path is provided, read and distill the file contents
  • If no arguments, ask the user for text to distill

Execution

Execute this distillation workflow:

Step 1: Assess the input

Read the provided text. Identify:

  • Approximate word count
  • Density of redundancy (light, moderate, heavy)
  • Whether the text has a distinctive voice worth preserving

Step 2: Apply the hierarchy of cuts

Work through the text applying cuts in order from the hierarchy above. For each sentence:

  1. Can two sentences merge into one without losing meaning?
  2. Are there redundant phrases?
  3. Can filler/hedge words be removed?
  4. Can nominalizations become verbs?
  5. Can passive become active without changing emphasis?
  6. Can prepositional chains compress?

Step 3: Verify lossless compression

Compare the distilled version against the original. Confirm:

  • No information was lost
  • No meaning was altered
  • Qualifications and nuance survived
  • The logical flow is intact

Step 4: Present the result

Output the distilled text. Follow with a brief summary:

---
Original: ~N words
Distilled: ~N words
Reduction: ~N%

If any meaning was ambiguous and required interpretation, note it.

Examples

Filler and hedge removal

Before: "It is essentially worth noting that the system actually performs quite well in basically all of the scenarios that were tested."

After: "The system performs well in all tested scenarios."

Nominalization to verb

Before: "We performed an investigation into the cause of the failure and made a determination that the configuration was incorrect."

After: "We investigated the failure and determined the configuration was incorrect."

Redundancy elimination

Before: "The end result of this process is that each and every individual component is tested and verified to ensure and confirm that it meets the required specifications and standards."

After: "This process verifies each component meets the required specifications."

Preserving necessary nuance

Before: "While the approach generally works well in most common scenarios, there are some edge cases, particularly those involving concurrent access patterns, where the current implementation may exhibit degraded performance characteristics."

After: "The approach works well in common scenarios but may degrade under concurrent access patterns."

Note: "may" is preserved — it's a genuine qualification, not a hedge.

Agentic Optimizations

ContextApproach
Short text (< 100 words)Distill inline, show before/after
Medium text (100-500 words)Distill in sections, show word count reduction
Long text or file (> 500 words)Read file, distill, write result, show stats
Preserving technical accuracyFlag any cuts that might alter technical meaning

平台分布

Codex

36.29%
按下载量换算125

Claude

27.64%
按下载量换算95

Cursor

18.91%
按下载量换算65

Gemini CLI

8.37%
按下载量换算29

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills