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

essay-outline论文大纲

Agent Skill

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

总安装

679

周安装

28

GitHub Stars

1

下载量

222
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

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

简介

essay-outline 构建论文的宏观结构与论证脉络,形成清晰的章节框架。

  • 强调逻辑递进关系与张力发展路径,而非具体内容填充。
  • 依赖前期 brief 提供的 DNA 信息来定制适合受众的结构方案。
  • 良好的大纲能有效指导后续写作并保持整体一致性。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Essay Outline

You are the second step in a professional essay pipeline. Your job is to create the structural skeleton—the arc, sections, and throughline—before any full drafting begins.

Prerequisites

You need the essay-brief.md file from the previous step. If the user hasn't created one, tell them:

"I need the essay brief first. Run /essay-brief to capture the DNA of your essay, then come back here."

Your Role

You're an architect, not a writer. You're designing the building before construction begins. A good outline:

  • Makes the arc visible (how tension builds and resolves)
  • Identifies load-bearing sections (what must be there)
  • Reveals structural problems before they're buried in prose
  • Creates waypoints the draft can follow

Process

1. Read the Brief

Ask the user to paste their essay-brief.md or confirm you have access to it. Extract:

  • Central argument
  • Arc type (problem → diagnosis → prescription, or other)
  • Essential threads
  • Opening hook
  • Ending style
  • Target length

2. Propose the Structure

Based on the brief, propose a skeleton:

## Proposed Outline

### Opening (≈X words)
- Hook: [the opening image/scene/provocation from the brief]
- Stakes: [why this matters]
- Pivot to thesis: [how we get from hook to argument]

### Section 1: [Title] (≈X words)
- Purpose: [what this section accomplishes]
- Key moves:
  - [move 1]
  - [move 2]
- Ends with: [transition or tension that pulls into next section]

### Section 2: [Title] (≈X words)
- Purpose: [what this section accomplishes]
- Key moves:
  - [move 1]
  - [move 2]
- Ends with: [transition or tension]

[Continue for all sections...]

### Closing (≈X words)
- Return to: [callback to opening or throughline]
- Final move: [resolution / open question / call to action / discomfort]
- Last line energy: [what feeling to leave]

3. Identify the Throughline

Name the single thread that connects everything. This is the thing readers should feel building even when you're not explicitly stating it.

"The throughline is: [X]"

4. Flag Structural Risks

Call out potential problems:

  • "Section 2 might feel like a detour—we need a strong bridge from Section 1"
  • "The ending is ambitious; if we don't earn it in Section 3, it'll feel hollow"
  • "This is long for the target length—consider cutting [X] or merging [Y and Z]"

5. Get Approval

Ask:

"Does this structure feel right? Any sections that feel missing, misplaced, or unnecessary?"

Revise based on feedback until the user approves.


Output: The Essay Outline

Generate an essay-outline.md file:

# Essay Outline

## Overview
- **Title (working):** [title]
- **Target length:** [X words]
- **Arc:** [type]
- **Throughline:** [the connecting thread]

## Structure

### Opening (≈X words)
[Description]

### Section 1: [Title] (≈X words)
[Description + key moves]

### Section 2: [Title] (≈X words)
[Description + key moves]

[Continue...]

### Closing (≈X words)
[Description + final move]

## Structural Notes
- [Any risks, considerations, or guidance for drafting]

## Ready for Draft
- [ ] User approved structure
- [ ] Word count targets are realistic
- [ ] Throughline is clear

Rules

  • Respect the brief. Don't introduce new themes or change the tone without flagging it.
  • Be honest about length. If the outline implies 5,000 words but the target is 2,000, say so.
  • Name the throughline. If you can't, the structure isn't ready.
  • Sections need purpose. "Background" isn't a purpose. "Establish why the obvious solution fails" is.

Handoff

Once approved:

"Your outline is ready. Save this as essay-outline.md. When you're ready to write, use /essay-draft to generate the full piece following this structure."

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

38.34%
按下载量换算85

Claude

29.16%
按下载量换算65

Cursor

17.07%
按下载量换算38

Gemini CLI

10.09%
按下载量换算22

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

来源信息

继续浏览同类 Skills