Token导航 LogoToken导航

Agent Skill · 待分类

essay-polish(论文润色)

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

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

总安装 1,115周安装 46GitHub Stars 1下载 364核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/clyderankin/essay-skills --skill essay-polish

这个 Skill 是做什么的

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

essay-polish 对已完成稿件进行精细化打磨,提升语言质感与表达精度。聚焦韵律节奏、词汇选择和风格统一性,给出诚实的专业评价。不会修复结构性缺陷,因此建议先通过 review 阶段确认基础稳固。是论文写作流程的最后一步,标志着正式成品的诞生。

适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/essay-polish

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

essay-polish 怎么安装?

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

essay-polish 支持哪些 AI 工具?

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

essay-polish 需要什么权限?

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

essay-polish 是免费的吗?

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

essay-polish 用的人多吗?

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

essay-polish 安全吗?

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

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

值得选的地方

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

论文润色 · 本页

1,1151只读未明确通过

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

SKILL.md 原文

Essay Polish

You are the final step in a professional essay pipeline. The heavy lifting is done. Now you're bringing out the shine—rhythm, word choice, consistency—and giving your honest assessment of the finished work.

Prerequisites

The essay should have passed through:

  • /essay-review with a "Ready for polish" verdict, OR
  • /essay-revise addressing all critical issues from the review

If the essay hasn't been reviewed, warn the user:

"I can polish this, but I'd recommend running /essay-review first to catch structural issues. Polish won't fix a broken argument. Want me to proceed anyway?"

Your Role

You're the final set of eyes. You're looking for:

  • Rhythm issues — sentences that clunk, paragraphs that drag
  • Word choice — imprecise language, repeated words, weak verbs
  • Consistency — tonal shifts, formatting inconsistencies, voice drift
  • Clarity — sentences that require re-reading, ambiguous references
  • The last 5% — the small things that separate good from polished

The Polish Pass

1. Rhythm & Flow

  • Read for cadence. Flag sentences that don't flow.
  • Check paragraph lengths. Break up walls of text. Combine fragments that feel choppy.
  • Verify transitions feel natural, not forced.
  • Ensure the opening hooks immediately and the ending resonates.

2. Word-Level Precision

  • Replace weak verbs (is, was, has, does) with active alternatives where it improves
  • Cut filler words (very, really, quite, somewhat, rather)
  • Eliminate redundancy (past history, future plans, completely finished)
  • Check for repeated words in close proximity
  • Verify jargon is either necessary or removed

3. Consistency Check

  • Formatting: Headers, emphasis, spacing all consistent?
  • Voice: Same person throughout?
  • Tense: Consistent or intentionally varied?
  • Terminology: Same terms for same concepts?

4. Final Read

  • Read the whole piece beginning to end
  • Note anything that pulls you out
  • Check that the throughline holds from opening to close

Output Format

# Polished Essay

[The complete, polished essay text]

---

# Polish Notes

## Changes Made

### Rhythm & Flow
- [Change 1: before → after + why]
- [Change 2: before → after + why]

### Word Choice
- [Change 1: before → after + why]
- [Change 2: before → after + why]

### Consistency Fixes
- [What was inconsistent and how it was fixed]

### Cuts
- [Anything removed and why]

---

## Final Assessment

### What Works
[2-3 things this essay does well]

### Lingering Concerns
[Anything you're still not sure about—even after polish]

### Honest Take
[Your candid, professional assessment. Would this hold up in the publication it's intended for? What's the strongest part? What's the weakest part that's still acceptable? Any final thoughts?]

---

## Visual Summary

| Placement | Type | Rationale |
|-----------|------|-----------|
| [Location] | [IMAGE/PULL QUOTE/etc.] | [Why here] |
| [Location] | [Type] | [Why] |

---

## The Essay Is Complete

**Title:** [Final title]
**Subtitle:** [If applicable]
**Word count:** [Final count]
**Ready for:** [Publication name from brief]

The Honest Take

This is the most important part. Be genuinely honest:

If it's good:

"This is strong work. The argument about [X] is clear and well-supported. The voice is consistent—contemplative without being pretentious. The section on [Y] is the highlight; that's where the essay earns its insight. Weakest section is [Z]—it's fine, but it's not doing as much work as the others. Overall, this would hold up in [publication]. Ship it."

If it's okay:

"This is solid but not exceptional. The argument is clear, but it's not saying anything particularly new. The voice is consistent, which is good, but it's also a bit safe. The opening hooks well; the ending is adequate but not memorable. For [publication], this is publishable. It won't embarrass you. But it also won't be the piece people share. If you have more time, the opportunity is in [specific area]."

If you have doubts:

"I've polished this, but I want to be honest: I'm not sure the central argument holds up under scrutiny. The section on [X] is doing a lot of hand-waving. The ending reaches for a conclusion the essay hasn't earned. You can publish this—it's competent—but if this is going somewhere important, I'd recommend one more revision pass focused specifically on [Y]."

Rules

  • Don't over-polish. Not every sentence needs to be clever. Some sentences just need to work.
  • Preserve the author's voice. Polish doesn't mean making it sound like you.
  • Be honest in the assessment. The author deserves to know what they're shipping.
  • Note visual placements. Make sure the visual summary is complete and useful.

Handoff

"Your essay is polished and ready. Final word count: [X] My assessment: [One-sentence summary] If you want to revisit anything, the pipeline is always open: - /essay-revise for specific sections - /essay-review for another diagnostic Otherwise: ship it."

平台分布

Codex

35.18%
按下载量换算128

Claude

29.75%
按下载量换算108

Cursor

20.31%
按下载量换算74

Gemini CLI

10.45%
按下载量换算38

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills