Token导航 LogoToken导航

Agent Skill · 研究检索

paper-planning(纸质规划)

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

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

总安装 5,127周安装 218GitHub Stars 346下载 1,796核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/evoscientist/evoskills --skill paper-planning

这个 Skill 是做什么的

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

paper-planning 用于根据关键词查找、检索和筛选相关信息。适用于在学术写作或研究中快速定位目标文献和参考资料。通过 GitHub 仓库安装,使用 npx skills add 命令完成集成。建议在使用前核实数据源权限及网络访问控制策略。

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

来源仓库内路径:skills/paper-planning

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

paper-planning 怎么安装?

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

paper-planning 支持哪些 AI 工具?

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

paper-planning 需要什么权限?

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

paper-planning 是免费的吗?

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

paper-planning 用的人多吗?

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

paper-planning 安全吗?

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

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

值得选的地方

  • 同时适配 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调用外部服务未明确有提醒
paper-planning

纸质规划 · 本页

5,127346只读未明确通过

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

SKILL.md 原文

Paper Planning

A structured approach to planning academic papers before writing begins. Covers four key activities: Story design, Experiment planning, Figure design, and Timeline management.

When to Use This Skill

If you don't yet have an idea, use the research-ideation skill first to find a problem and design a solution.
  • User wants to plan a paper before writing
  • User asks about structuring a paper's story or contributions
  • User needs to plan experiments (comparisons, ablations)
  • User wants to design pipeline figures or teaser figures
  • User asks about writing timelines or submission schedules

Planning Overview

Paper planning follows four steps, ideally completed before writing begins:

Step 1: Story Design     → What is the narrative? What are the contributions?
Step 2: Experiment Plan   → What experiments prove our claims?
Step 3: Figure Design     → How do we visually communicate the method?
Step 4: Timeline          → When does each section get written?

Counterintuitive Planning First

Prioritize these counterintuitive rules before regular planning:

  1. Write your rejection letter first: Draft the top-5 likely rejection comments ("limited novelty", "missing baseline", "not robust", etc.), then plan experiments that directly preempt each one.
  2. Narrow claim before broad claim: Define the smallest defensible core claim first. Expand only after evidence is strong. Over-broad claims fail review more often than narrow strong claims.
  3. Design ablations before polishing method text: If a module cannot be ablated cleanly, its contribution claim is weak.
  4. Allocate compute to stress tests, not only benchmarks: A single convincing stress-test figure often contributes more than multiple small benchmark gains.
  5. Plan a fallback narrative now: If SOTA gain is marginal, predefine a secondary value proposition (efficiency, robustness, fewer assumptions, wider applicability).

See references/counterintuitive-planning.md


Step 1: Story Design

The "story" is the logical narrative that connects the problem, insight, method, and results.

Reverse Engineering the Story

Work backwards to build the story:

  1. What is the technical problem? — The specific challenge that existing methods cannot solve well
  2. What are our contributions? — The concrete technical novelties
  3. What are the benefits and new insights? — What advantages does our approach provide?
  4. How do we lead into the challenge? — How to frame the task and previous methods to naturally arrive at the challenge

Then write forward: Task → Previous methods → Challenge → Our contributions → Advantages

Core Elements to Define

Before writing any section, clearly articulate:

ElementQuestionExample
TaskWhat problem does this paper address?"Real-time 3D scene reconstruction"
ChallengeWhy can't existing methods solve it well?"Cannot handle dynamic objects efficiently"
InsightWhat key observation drives our approach?"Motion patterns are temporally sparse"
ContributionWhat do we propose?"Sparse temporal attention for dynamic regions"
AdvantageWhy is our approach better?"Reduces computation while preserving quality"

Starting Point: Pipeline Figure Sketch

Start by drawing a pipeline figure sketch. This forces you to clarify the overall method before writing.

The pipeline figure sketch serves as the paper's visual backbone:

  • Draw it before writing anything
  • It reveals whether the method is clear enough to explain
  • It identifies the novel modules vs. standard components
  • It determines subsection structure for the Method section

See references/story-design.md


Step 2: Experiment Planning

Plan experiments before writing to avoid discovering gaps late.

Two Categories of Experiments

Comparison Experiments — Prove our method is better:

  • Which baseline methods to compare against?
  • Which datasets and metrics?
  • What is the evaluation protocol?

Ablation Studies — Prove each module is effective:

  • Part 1: One big table showing impact of core contributions
  • Part 2: Several small tables for design choices and hyperparameters

Planning Checklist

  • List all comparison baselines (recent, relevant, SOTA)
  • Define evaluation metrics (standard for the task)
  • Identify datasets (standard benchmarks + challenging demos)
  • List ablation configurations (remove each core component)
  • Plan design-choice tables (hyperparameters, input quality, alternatives)
  • Plan demo scenarios (challenging data to showcase upper limit)

See references/experiment-planning.md

Experiment Plan Template

Use the template at assets/experiment-plan-template.md to organize your experiment plan.


Step 3: Figure Design

The pipeline figure is for highlighting novelty, not for making readers understand. The Method text is what makes readers understand.

Pipeline Figure Principles

  • Highlight novelty: The pipeline figure showcases what is new, not just the workflow
  • Differentiate from prior work: The figure must look different from previous methods
  • Novel modules stand out: If the overall pipeline is standard, zoom in on novel modules
  • Focus on clarity of the novel parts; standard components can be simplified

Teaser Figure

The teaser (usually Figure 1) shows the key result at a glance:

  • Place it at the top of the first page
  • Should be immediately compelling
  • Reference it from the Introduction

Visual Quality Matters

Visual polish directly influences review outcomes. See references/figure-design.md for the full visual quality guide (pipeline figures, tables, typography)


Step 4: Timeline

4-Week Countdown

Start writing at least 1 month before the deadline.

WeekTasks
4 weeks before1. Organize story (core contribution, module motivations). 2. List comparison experiments and ablation studies. 3. Write Introduction first draft.
3 weeks before1. Finalize the pipeline figure sketch. 2. Write Method first draft (use \todo{} for unsettled details). Deadline: give Introduction + Method draft to advisor.
2 weeks beforeWrite first drafts of Experiments, Abstract, Related Work.
Last weekRevise paper, polish pipeline figure and teaser, run demos.
Critical: By the end of Week 3, you must send the Introduction and Method drafts to your advisor — otherwise the advisor likely will not have enough time to finish reviewing the paper.

See references/timeline-4week.md for the detailed schedule and progress tracking template.


Handoff to Writing

When planning is complete, pass these artifacts to paper-writing:

ArtifactSource StepUsed By
Story summary (task → challenge → insight → contribution → advantage)Step 1Introduction
Module Motivation Mapping tableStep 1Method subsections
Experiment plan (comparisons + ablations + demos)Step 2Experiments section
Pipeline figure sketchStep 1 / Step 3Method overview + Figure 2
Claim-to-experiment mappingStep 2Abstract, Introduction, Experiments
Fallback narrative (if planned)Counterintuitive Rule 5Introduction / Conclusion pivot
Rejection-risk tableCounterintuitive Rule 1Self-review prioritization

Reference Navigation

TopicReference FileWhen to Use
Story designstory-design.mdStarting a new paper
Experiment planningexperiment-planning.mdBefore running experiments
Timelinetimeline-4week.mdSetting up a writing schedule
Figure designfigure-design.mdDesigning pipeline/teaser figures
Experiment plan templateexperiment-plan-template.mdCreating a structured experiment plan
Counterintuitive strategycounterintuitive-planning.mdIncreasing acceptance odds with non-obvious planning choices

Handoff to Presentation

If preparing a conference talk or slide deck, the academic-slides skill guides slide creation from your planning artifacts — including translating your story design and pipeline figure into presentation structure.

平台分布

Codex

33.52%
按下载量换算602

Claude

30.57%
按下载量换算549

Cursor

18.54%
按下载量换算333

Gemini CLI

8.77%
按下载量换算158

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills