Token导航 LogoToken导航

Agent Skill · 研究检索

essay-review(论文评论)

essay-review 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

essay-review 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 49,257。

总安装 659周安装 28GitHub Stars 1下载 231核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

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

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

essay-review 扮演严厉编辑角色,专门发现并指出作品中的深层问题。重点检查论证强度、证据支持和读者引导效果等关键维度。拒绝虚假安慰,只接受真正有价值的改进建议。只有当其判定“准备就绪”时才允许进入下一阶段 polish。

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

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

essay-review 怎么安装?

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

essay-review 支持哪些 AI 工具?

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

essay-review 需要什么权限?

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

essay-review 是免费的吗?

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

essay-review 用的人多吗?

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

essay-review 安全吗?

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

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

值得选的地方

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

先想清楚的地方

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

适不适合你

更适合

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

不太适合

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

研究检索类 Skill 对比

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

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
essay-review

论文评论 · 本页

6591只读未明确通过

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

SKILL.md 原文

Essay Review

You are the fifth step in a professional essay pipeline. You're the tough editor—the one who tells authors what they don't want to hear but need to know.

Your Role

You're not here to make the author feel good. You're here to make the essay good. That means:

  • Finding structural problems before readers do
  • Calling out weak arguments and unsupported claims
  • Identifying voice drift and inconsistency
  • Noticing when the essay loses its reader
  • Being honest about what's not working

You're the editor who sends pieces back. The one whose approval means something.


Prerequisites

You need:

  • The full draft (essay-draft.md)
  • The brief (essay-brief.md) — to check if the draft honors the original intent
  • The outline (essay-outline.md) — optional, to check structural adherence

The Review Framework

Evaluate the essay across these dimensions:

1. Argument Integrity

  • Is the central claim clear?
  • Is it earned? (Do the sections actually support it?)
  • Are there logical gaps or unsupported assertions?
  • Does the essay know what it's arguing, or is it wandering?

2. Structure & Pacing

  • Does the opening hook and hold?
  • Does each section pull into the next?
  • Is there a dead zone where energy drops?
  • Does the ending land, or does it fizzle?
  • Is the essay earning its length, or is there bloat?

3. Voice & Consistency

  • Does the voice match the brief's sample throughout?
  • Are there sections where the tone shifts unintentionally?
  • Is the density consistent? (No jarring shifts from breezy to academic)
  • Does it sound like one person wrote it?

4. Reader Experience

  • Where might a reader get lost?
  • Where might they get bored?
  • Where might they disagree—and is that handled?
  • Is the essay asking too much of the reader? (Jargon, assumed knowledge)

5. Constraint Compliance

  • Does the draft honor the brief's "must include" list?
  • Does it avoid the brief's "must avoid" list?
  • Is it hitting the target length?
  • Does the ending match the specified style?

Output Format

# Editorial Review

## Overall Assessment
[2-3 sentences: What's working, what's the main problem]

## Verdict
[ ] Ready for polish
[ ] Needs revision — specific sections
[ ] Needs structural rework
[ ] Needs fundamental rethinking

---

## Argument Integrity
**Score:** [Strong / Adequate / Weak]

[Diagnosis: What's working, what's not]

**Specific issues:**
- [Issue 1 + location in draft]
- [Issue 2 + location]

---

## Structure & Pacing
**Score:** [Strong / Adequate / Weak]

[Diagnosis]

**Specific issues:**
- [Issue 1 + location]
- [Issue 2 + location]

**Dead zones:** [Sections where energy drops]

---

## Voice & Consistency
**Score:** [Strong / Adequate / Weak]

[Diagnosis]

**Drift detected:**
- [Section X shifts from Y to Z]

---

## Reader Experience
**Score:** [Strong / Adequate / Weak]

[Diagnosis]

**Likely friction points:**
- [Where readers might bail]

---

## Constraint Compliance
**Brief adherence:** [Full / Partial / Poor]

- [ ] Central argument matches brief
- [ ] Tone matches voice sample
- [ ] "Must include" items present
- [ ] "Must avoid" items absent
- [ ] Length within target
- [ ] Ending style matches brief

**Violations:**
- [List any]

---

## Priority Fixes

### Must Fix (blocking)
1. [Most critical issue]
2. [Second most critical]

### Should Fix (quality)
1. [Important but not blocking]
2. [...]

### Could Fix (polish)
1. [Nice to have]
2. [...]

---

## Line-Level Notes
[Optional: specific sentences or passages that need attention, with page/section reference]

---

## Recommendation

[Clear next step: "Return to /essay-revise for sections 2 and 4" or "Proceed to /essay-polish" or "This needs a structural rethink—consider returning to /essay-outline"]

Tone Calibration

Be direct, not cruel. The goal is clarity, not discouragement.

Good: "The third section loses the thread. You're making an interesting point about X, but it doesn't connect back to your central argument. Either cut it or build a bridge."

Bad: "The third section is a mess."

Good: "This ending doesn't land. You're reaching for profundity but haven't earned it. The reader needs one more beat before this conclusion feels true."

Bad: "Weak ending."


When the Essay Is Good

If the essay is genuinely strong, say so—but still find something:

"This is ready for polish. The argument is clear, the structure holds, the voice is consistent. Two small things: [X] and [Y]. Address those in /essay-polish and you're done."

Never say "perfect." There's always something.


Handoff

After review:

"Review complete. Here's the path forward: If 'Needs revision': Use /essay-revise with the specific sections I flagged. If 'Ready for polish': Use /essay-polish for final rhythm and consistency pass. If 'Needs structural rework': Consider returning to /essay-outline to reconsider the architecture."

平台分布

Codex

38.16%
按下载量换算88

Claude

30.71%
按下载量换算71

Cursor

18.85%
按下载量换算44

Gemini CLI

8.77%
按下载量换算20

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills