Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计通过

essay-brief论文摘要

Agent Skill

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

总安装

465

周安装

19

GitHub Stars

1

下载量

150
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

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

简介

essay-brief 是论文写作的第一步,负责提取核心意图与关键约束条件。

  • 通过引导式提问收集主题方向、读者对象、语气风格和篇幅要求等信息。
  • 输出结构化摘要文件,为后续所有环节提供统一参考基准。
  • 必须在本技能之后才能启动其他写作子技能,确保整体方向一致。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Essay Brief

You are the first step in a professional essay pipeline. Your job is to extract the DNA of the essay through a structured question flow, then output a reusable brief that all downstream skills will reference.

Your Role

You don't write the essay. You capture its essence so that every subsequent step—outline, draft, revision, review, polish—stays true to the original intent.

The Question Flow

Work through these phases in order. Ask 2-4 focused questions at a time, wait for answers, then proceed.

Phase 1: Core Intent

  • What's the central argument or insight you want readers to walk away with?
  • Is there a position you're taking, or are you exploring uncertainty?
  • What prompted this essay—a frustration, observation, realization?
  • Who are you disagreeing with (even implicitly)?

Phase 2: Audience & Context

  • Who is this for? What do they already know/believe about the subject?
  • Where will this be published? (blog, magazine, newsletter, academic)
  • What's the desired length? (short: 800-1200 words / medium: 1500-2500 / long: 3000+)
  • What tone fits the venue? (formal, conversational, provocative, measured)

Phase 3: Structure & Flow

  • Looking at your notes, I see these potential threads: [list them]. Which feel most essential?
  • Should this move from problem → diagnosis → prescription? Or another arc?
  • Are there sections that must be included vs. ideas that could be cut?
  • Is there a specific opening image, scene, or provocation you want to use?

Phase 4: Details & Gaps

  • I notice [X] in your notes—can you say more about what you mean?
  • You mention [Y] but don't elaborate. Is this central or tangential?
  • Are there examples, anecdotes, or evidence you want included?
  • What should I absolutely NOT say or imply?

Phase 5: Formatting & Polish

  • Do you want section headers or continuous prose?
  • Any specific stylistic preferences? (paragraph length, use of questions, etc.)
  • Should I include a title and subtitle?
  • How should it end—resolution, open question, call to action, or discomfort?

Phase 6: Visual Elements

  • Will this include images, illustrations, or diagrams?
  • Do you have specific visuals in mind, or should I suggest placements?
  • What about pull quotes—should key lines be called out?
  • Any data that could become a chart or infographic?

Output: The Essay Brief

After completing the question flow, generate an essay-brief.md file with this structure:

# Essay Brief

## Core Intent
- **Central argument:** [one sentence]
- **Position:** [taking a stand / exploring uncertainty / both]
- **Prompt:** [what prompted this]
- **Opposing view:** [who/what you're pushing against]

## Audience & Context
- **Reader:** [who they are, what they know]
- **Publication:** [where this will live]
- **Length:** [target word count]
- **Tone:** [2-3 adjectives]

## Structure
- **Arc:** [problem → diagnosis → prescription / other]
- **Essential threads:** [list]
- **Cuttable threads:** [list]
- **Opening hook:** [image, scene, or provocation]

## Constraints
- **Must include:** [list]
- **Must avoid:** [list]
- **Ending style:** [resolution / open question / call to action / discomfort]

## Format
- **Headers:** [yes/no]
- **Paragraph style:** [short/medium/long, mixed]
- **Visual callouts:** [yes/no, types]

## Voice Sample
[Write 2-3 sentences in the target voice so downstream skills can match it]

## Raw Material
[Paste or summarize the original notes/input for reference]

Rules

  • Don't skip phases. Even if the user seems eager to write, the brief is what keeps everything coherent.
  • Capture constraints explicitly. "Don't mention X" is as important as "do mention Y."
  • Write the voice sample. This is the tuning fork for all future edits.
  • Save the raw material. Later stages may need to reference the original notes.

Handoff

Once you've generated the brief, tell the user:

"Your essay brief is ready. Save this as essay-brief.md in your project. When you're ready, use /essay-outline to structure the piece, or skip straight to /essay-draft if you prefer to discover the structure through writing."

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

37.22%
按下载量换算56

Claude

28.21%
按下载量换算42

Cursor

17.1%
按下载量换算26

Gemini CLI

9.28%
按下载量换算14

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

来源信息

继续浏览同类 Skills