REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
向顶会优秀论文学科研|Oral Paper Skill — 从 883 篇 Oral 论文摘要中“蒸馏”共通做法,用于论文对照改进与学习复盘 · Skill + prompt pack (CN/EN). Learn from 883 Oral paper abstracts to improve your research and writing.
作者提供的原文
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/skills/adkid-zephyr-oral-paper-skill)在同一工作中把 AI 连到服务的 MCP
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
MCP server for terminal commands, file operations, and process management
同类工作,排序与 Skill 列表相同
| 本项 oral-paper-skill | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| 作者 | Adkid-Zephyr | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skill 数 | 1 | 1 | 1 | 1 | 1 |
| GitHub 星标 | 602 | 470,165 | 234,528 | 150,695 | 144,727 |
| 最近代码更新 | 2026年9月18日 | 2026年11月20日 | 2026年4月20日 | 2026年11月20日 | 2026年11月19日 |
| 许可证 | – | MIT | – | Apache-2.0 | MIT |
Adkid-Zephyr 提供的 1 个 Skill(指令集),AI 读取后照做 · 不是 MCP server
MCP = 手
把 AI 连到外部服务或数据,例如读取 Notion 或开发票。需要有程序或服务器在运行。
Skill = 手册
教 AI 怎么做某项工作的文本文件,不连接任何服务。
有些会重叠:少数 Skill 带有调用工具的脚本,少数 MCP 只提供知识。请从你想完成的工作出发。
Codex
依据开发者 README 和 repo 中的文件夹
GitHub 账号 Adkid-Zephyr(个人),已创建 2 年
★ 602 星 · 代码最近更新 2026年9月18日
没有,都是纯文本文件,由 AI 阅读后照做
没有脚本,所以不会自己联网
没有发现 hook 或写入电脑设置的操作
根据仓库 commit a2c4bc4 中的文件自动检查(只读取文件,没有运行任何内容)。这不是安全保证,请自己阅读后再决定
第一步:你用哪个 AI?
选择你用的应用,本页只显示该应用的安装方法
这个 Skill 没有说明许可证,所以我们不在网站上提供 ZIP。请从 GitHub 下载并自己整理文件夹,或者用上面的"让 AI 帮你安装",更简单
解压后,只把 skills/oral-paper-skill 文件夹重新压缩。ZIP 的最上层必须是包含 SKILL.md 的 oral-paper-skill 文件夹,不能直接放散乱的文件
+Create skillUpload a skill选择文件 oral-paper-skill.zip
SettingsCapabilitiesCode execution and file creation
Turn on Code execution and file creation first (newer menus: Create and edit files) · personal plans: Settings → Capabilities · Team/Enterprise: an admin turns it on under Organization settings → Plugins & skills · every plan, including Free
Upload once; it works in claude.ai and Claude Desktop, and in recent Claude Code signed in with a Claude account (not with an API key)
Cowork and cloud sessions use the skills turned on in your claude.ai account, not ~/.claude/skills on your computer (Claude Desktop scheduled tasks run locally and still load it)
Checked against official docs 2026年11月12日 · Source: support.claude.com, support.claude.com, code.claude.com
复制这句话,粘贴到 Claude Code 的对话中
如果只用于一个项目,请粘贴到在该项目文件夹中打开的对话里 · AI 在安装前一定会先告诉你路径
AI 会先说明要做什么,每一步都会征求你的同意
重新打开 Claude Code,输入 /oral-paper-skill,或直接提出相关任务,Claude 会自动选用
Checked against official docs 2026年11月12日 · Source: code.claude.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
正在检查命令 · 通过后才会显示复制按钮
ChatGPT 桌面应用内置 Codex,Codex 从 ~/.agents/skills 文件夹读取 Skill
在 ChatGPT 桌面应用中打开 Codex,把这句话粘贴到对话中
AI 在安装前一定会先告诉你路径
AI 会先说明要做什么,每一步都会征求你的同意
把 oral-paper-skill 文件夹放到 ~/.agents/skills/oral-paper-skill
~ 是你的主文件夹($HOME)
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
正在检查命令 · 通过后才会显示复制按钮
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
不能使用你自己安装的 Skill,只能使用目录中插件自带的 Skill
想在 ChatGPT 中使用这个 Skill,请按上面的方法使用 ChatGPT 桌面应用
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
复制这句话,粘贴到 Codex 的对话中 · 适用于 ChatGPT 桌面应用中的 Codex、Codex CLI 和 IDE 扩展
如果只用于一个项目,请粘贴到在该项目文件夹中打开的对话里 · AI 在安装前一定会先告诉你路径
AI 会先说明要做什么,每一步都会征求你的同意
Codex 会自动发现新安装的 Skill;如果没有出现,请重启 Codex · 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
正在检查命令 · 通过后才会显示复制按钮
复制这句话,粘贴到 Cursor 的对话中
如果只用于一个项目,请粘贴到在该项目文件夹中打开的对话里 · AI 在安装前一定会先告诉你路径
AI 会先说明要做什么,每一步都会征求你的同意
在 Cursor 的 Agent 聊天中输入 / 并选择 oral-paper-skill
Checked against official docs 2026年11月12日 · Source: cursor.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
正在检查命令 · 通过后才会显示复制按钮
适用于其他能读取 Skill 的应用。这句话列出了 Claude Code、Codex 和 Cursor 的路径,AI 会按你的应用选择 · 复制这句话,粘贴到应用的对话中
如果只用于一个项目,请粘贴到在该项目文件夹中打开的对话里 · AI 在安装前一定会先告诉你路径
AI 会先说明要做什么,每一步都会征求你的同意
Checked against official docs 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
其他支持 Agent Skills 的应用(如 Gemini CLI、GitHub Copilot)使用不同文件夹,请查看该应用的指南,再把含 SKILL.md 的文件夹复制过去。
已于 2026年11月11日 对照 Claude Code、Codex 和 Cursor 官方指南核实 skill 文件夹
以下文字来自开发者的 repo,不是 PopNx MCP 的指令
7,689 个字符 · 在 GitHub 打开完整文件
---
name: oral-paper-skill
description: Help authors learn from exemplary ICLR, ICML, and NeurIPS papers through source-linked manuscript comparisons, concrete writing and experiment suggestions, and guided reflection. Use for research storytelling, contribution framing, paper comparison, figure planning, or research retrospectives. Not an acceptance predictor or a routine grammar/citation formatter.
---
# Oral Paper Skill
Turn useful practices from exemplary papers into concrete revisions and focused learning. Offer two services: **compare and improve** a manuscript, or **learn and reflect** on a practice. Preserve the author's research purpose and judgment.
The current knowledge base includes semantic extraction of 883 abstracts from 884 official event records, source checks, and cross-paper synthesis. It is abstract-level evidence, not 883 full-paper readings or an explanation of Oral selection. For provenance, read [sources and reading levels](references/oral-patterns.md).
## Start from the author's purpose
Identify the requested artifact, contribution type, stage, and relevant constraints. Use the supplied draft, results, and examples before asking for more. Ask only when missing information would materially change the advice or authorization.
Several coherent contributions are allowed. Missing evidence in an early idea differs from evidence contradicting a result claim. Do not turn a writing or learning request into an automatic decision to abandon research.
## Choose a relevant practice and example
Read [abstract-derived practices and examples](references/abstract-derived-practices.md) when applying the distilled knowledge. Select only the practices useful for this request; do not run every paper through all seven.
1. **Specify the research tension.** Identify an unmet requirement or an observation that makes the question worth investigating. Do not manufacture a prior-work failure.
2. **State the contribution delta.** Name the changed output, operation, representation, assumption, or enabled activity. A method name and “novel” do not explain the difference.
3. **Match evidence to the claim.** Identify the measured or proved property. Keep attempts distinct from success, a proxy from the whole capability, and proposed evaluation from reported outcomes.
4. **Choose a meaningful comparison.** Explain what decision it resolves, what stays fixed, and what changes. For efficiency, identify the actual resource unit and accounting boundary; active parameters, tokens, latency, memory and total cost are different quantities.
5. **Keep conditions beside conclusions.** Preserve the model class, quantifier, guarantee regime, comparator and numerical convention that give the result its meaning.
6. **Explain what the resource enables.** Connect contents or interfaces to a research activity. Distinguish intended uses, demonstrated uses and release commitments.
7. **Extract a bounded lesson.** Explain what readers can reconsider or investigate, separating observation, interpretation and a proposed action. State what would limit transfer.
These are editorial moves supported by examples, not measured universal traits or admission criteria. Their usefulness for a new manuscript is a reasoned recommendation, not a demonstrated causal effect.
Choose exemplars by problem, contribution, evidence needs and resource constraints—not fame alone. Use [archetype guidance](references/archetypes.md) for theory, empirical, systems, resource, method and position-paper differences. A resource need not also deliver a new mechanism or a superior model; a descriptive finding need not claim causality.
## Keep source attribution precise
For an attributed practice, identify the paper, source link, and inspected abstract unit, section or figure. The curated examples have been checked against their original abstracts; their numbered units belong to the stored snapshot, not official section numbers.
- Separate **what the source says**, **why the practice might help**, and **what you propose for this draft**. An application suggestion is not an experiment the authors necessarily ran.
- Abstracts support framing, stated contributions and author-reported evidence. Inspect the relevant full text or actual figure before attributing experimental rigor, proof details or figure design to a paper.
- Preserve consequential qualifiers: structural-assumption-free is not assumption-free; a reported maximum error is not automatically a proved bound; an unspecified percentage is not automatically percentage points; a future release is not present availability.
- Keep genuinely unspecified source facts unknown. Do not repair them from intuition or treat absence from an abstract as absence from the full paper.
- If a suitable source is unavailable, label advice as general research guidance. Do not invent citations or make the user supply references merely to satisfy a template.
Do not reload the entire corpus for a single edit. Use a small, relevant comparison set and retrieve additional material only when the recommendation depends on it.
## Compare and improve
Locate the draft's important claim and its current support. For each high-priority change, connect:
**draft location → relevant source practice → concrete revision or feasible next check → why it fits → important limit.**
Default to at most three improvements. Prioritize changes that alter understanding or interpretation over cosmetic resemblance. If no useful gap is apparent, say so rather than inventing criticism.
When asked to edit, deliver the revised text, figure plan or experiment protocol directly. Keep the title, abstract, introduction and main evidence coherent, without forcing every section to repeat one claim. Preserve the author's story unless actual evidence requires changing its scope.
For a proposed experiment, specify only what changes the decision: the claim, comparison, unit of analysis, relevant controlled conditions, outcome, and how results would change the interpretation. “Match everything” may answer the wrong question; distinguish component attribution from comparing systems as delivered. If a claim is already contradicted, do not use prose to conceal it.
## Learn and reflect
Teach one useful practice with a small sourced example. Explain its purpose and an important exception, then give one focused exercise on the user's paragraph, comparison or plan. Label any invented teaching example or illustrative rewrite explicitly.
If the user requests both modes, prioritize the artifact and explain only the lessons that affected it. Use [the comparison guide](references/review-scorecard.md) only when a structured retrospective would help.
## Evidence and delivery
Keep observed findings, supported claims, inferences, plans and invalidated claims distinct, without burdening every response with status labels. Do not turn pilots, mechanical checks or AI judgments into prevalence, transfer, novelty or readiness claims. Planned figures must not contain fabricated results or success-shaped mock curves.
ORAL can remain an optional mnemonic: central question, reader-visible evidence, meaningful alternatives, and a lasting lesson. It is not the empirical conclusion of the corpus analysis, a score, or a required sequence.
Before delivery, check the few things that matter: source fidelity, applicability, a concrete change, and consistency with the actual evidence. Self-review and format validation are not evidence of measured user benefit.
Keep the response concise. Do not default to GO/WAIT/KILL, Oral-level ratings, acceptance predictions, or another literature survey when the user asked for a revision.
提问、分享技巧或报告无法使用。按“有帮助”数量排序。