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

scientific-paper科学论文

Agent Skill

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

总安装

783

周安装

32

GitHub Stars

公开资料未说明

下载量

251
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/jcardif/agent-skills --skill scientific-paper

简介

scientific-paper 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。

  • 适用于科研选题、文献调研、信息聚合等需要从多源数据中提炼线索的场景。
  • 通过安装命令 npx skills add https://github.com/jcardif/agent-skills --skill scientific-paper 添加,需确认权限范围和维护状态。
  • 使用前应核实是否会触发联网、命令执行或文件读写操作,避免越权访问。
  • 建议结合原始 README 进一步核验具体用法和功能边界。

SKILL.md

Scientific Paper Writing

Core philosophy

Approach every paper as a PhD-level researcher would:

  1. Understand before writing. Read existing content, the problem domain, and related work before producing a single sentence.
  2. Rigor over volume. Every claim must be substantiated — by derivation, citation, or empirical evidence. Never pad.
  3. Precision in language. Use exact terminology. Define terms on first use. Avoid weasel words ("very", "clearly", "obviously").
  4. Reproducibility. A competent reader should be able to reproduce every result from what is written.
  5. Intellectual honesty. State assumptions explicitly. Acknowledge limitations. Report negative results. Distinguish what is proven from what is conjectured.
  6. Write to communicate, not to impress. The goal is transferring understanding to the reader. Prefer simple, direct prose over elaborate vocabulary. Complex ideas demand simple writing.

Research methodology workflow

When asked to write or substantially expand a paper, follow this process:

Phase 1: Problem Formulation
  - What is the precise research question?
  - Why does it matter? (motivation)
  - What would a solution look like? (success criteria)
  - What are the boundaries? (scope)

Phase 2: Literature & Prior Art
  - What existing work addresses this or related problems?
  - What are the gaps in existing approaches?
  - How does this work position itself relative to the field?

Phase 3: Methodology & Framework
  - What analytical/computational approach will be used?
  - Why is this approach appropriate? (justify the choice)
  - Define notation, assumptions, and formal setup

Phase 4: Development
  - Build the mathematical or analytical framework
  - Derive results step by step
  - Verify internal consistency

Phase 5: Analysis & Discussion
  - What do the results mean?
  - What are the limitations?
  - What are the practical implications?

Phase 6: Writing & Polish
  - Structure for the reader, not the author
  - Ensure logical flow between sections
  - Verify all cross-references, citations, notation consistency

For detailed guidance on each phase, see references/scientific-method.md.

LaTeX standards

Document setup

Always use these baseline packages unless there is a specific reason not to:

\usepackage[a4paper,margin=1in]{geometry}
\usepackage{amsmath,amssymb,amsthm}    % Mathematics
\usepackage{hyperref}                   % Clickable references
\usepackage{cleveref}                   % Smart cross-refs (\cref)
\usepackage{booktabs}                   % Professional tables
\usepackage{graphicx}                   % Figures
\usepackage[backend=biber,style=numeric-comp]{biblatex}  % Citations

Mathematical typesetting rules

  • Operators: Use \operatorname{} or define with \DeclareMathOperator for multi-letter operators (e.g., \operatorname{argmax}, not argmax in math mode)
  • Variables: Single italic letters for scalars ($x$), bold for vectors ($\mathbf{v}$), blackboard bold for sets ($\mathbb{R}$)
  • Subscripts/superscripts: Use descriptive subscripts: $r_{\text{net}}$, not $r_n$ when $n$ is ambiguous
  • Equations: Number all important equations. Use align for multi-line, equation for single-line. Never use eqnarray.
  • Definitions: Use \coloneqq (:=) when defining a quantity, = for equality
  • Notation table: Include a notation summary table when the paper uses more than 10 symbols

Theorem environments

Define and use proper theorem environments:

\newtheorem{theorem}{Theorem}[section]
\newtheorem{lemma}[theorem]{Lemma}
\newtheorem{proposition}[theorem]{Proposition}
\newtheorem{corollary}[theorem]{Corollary}
\theoremstyle{definition}
\newtheorem{definition}[theorem]{Definition}
\newtheorem{example}[theorem]{Example}
\theoremstyle{remark}
\newtheorem{remark}[theorem]{Remark}

Tables

Use booktabs rules (\toprule, \midrule, \bottomrule). Never use vertical lines. Example:

\begin{table}[htbp]
  \centering
  \caption{Description before the table.}
  \label{tab:example}
  \begin{tabular}{lrr}
    \toprule
    Item & Value & Unit \\
    \midrule
    Precision & 94.3 & \% \\
    Samples   & 1{,}000 & -- \\
    \bottomrule
  \end{tabular}
\end{table}

For complete LaTeX reference, see references/latex-reference.md.

Writing quality standards

  • Active voice preferred over passive ("We derive..." not "It is derived...")
  • Present tense for established facts and mathematical truths; past tense for describing what was done
  • One idea per paragraph. Topic sentence first, then support.
  • Transitions between sections and paragraphs — the reader should never wonder "why am I reading this now?"
  • Avoid: "it is well known that", "trivially", "clearly", "the reader can easily verify". If it is clear, the reader does not need to be told; if it is not, saying so is condescending.
  • Define before use. Every symbol, abbreviation, and technical term must be defined before or at first use.

For detailed style guidelines, see references/writing-style.md.

Workflow for editing existing papers

When asked to work on an existing .tex file:

  1. Read the entire file first. Understand structure, notation, and what exists.
  2. Identify what is needed. Expand content? Fix errors? Add sections? Improve prose?
  3. Maintain consistency. Match existing notation, style, and conventions. Do not introduce new packages or notation that conflicts with what exists.
  4. Build on what is there. Extend, do not replace, unless explicitly asked to rewrite.
  5. Verify compilation. Ensure no LaTeX errors are introduced.

Workflow for new papers

  1. Clarify the research question with the user before writing.
  2. Outline first. Propose a section structure and get agreement before writing prose.
  3. Design figures and tables early. Determine the key visuals before writing prose — let the figure sequence drive the narrative structure.
  4. Write non-linearly. Start with Results/Methods (the most concrete sections), then Discussion, then Introduction, then Abstract. Few successful papers are written start-to-finish.
  5. Revise in order: content → structure → style. First ensure correctness and completeness, then logical organization, then prose quality.
  6. Writing is iterative. Drafting reveals gaps in reasoning. Expect to revisit earlier sections as later ones develop.

Quality checklist

Before considering a paper section complete:

- [ ] Every claim is substantiated (derivation, citation, or evidence)
- [ ] All notation is defined and used consistently
- [ ] All equations are numbered and referenced in the text
- [ ] Cross-references (\ref, \cref) are correct
- [ ] No undefined terms or unexplained abbreviations
- [ ] Assumptions are explicitly stated
- [ ] Limitations are acknowledged
- [ ] Alternative interpretations or counterarguments are addressed
- [ ] Results are reported separately from interpretation
- [ ] Figures and tables are self-explanatory through their captions
- [ ] Logical flow: each paragraph follows from the previous
- [ ] No filler text or unsupported generalizations

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

36.47%
按下载量换算92

Claude

29.8%
按下载量换算75

Cursor

19.15%
按下载量换算48

Gemini CLI

9.89%
按下载量换算25

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

来源信息

继续浏览同类 Skills