Token导航 LogoToken导航TokenDH.com
待分类只读github未标认证来源可访问许可证需确认审计通过

essay-polish论文润色

Agent Skill

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

总安装

1,115

周安装

46

GitHub Stars

1

下载量

364
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

简介

essay-polish 对已完成稿件进行精细化打磨,提升语言质感与表达精度。

  • 聚焦韵律节奏、词汇选择和风格统一性,给出诚实的专业评价。
  • 不会修复结构性缺陷,因此建议先通过 review 阶段确认基础稳固。
  • 是论文写作流程的最后一步,标志着正式成品的诞生。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

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."

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

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