论文搜索
- 作者仓库星标 16,057
- 作者更新于 实时读取
- 作者仓库 nature-skills
- 领域
- 通用
- 兼容 Agent
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- 信任分
- 88 / 100 · 社区维护
- 作者 / 版本 / 许可
- @Yuan1z0825 · 未声明 license
- Token 消耗评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部 API Key
- 不需要
- 兼容的系统
- 未声明（默认跨平台）
- 底层运行要求
- 无特殊要求
- 文件与系统权限
-
- 只读
- 允许写入 / 修改
- Shell 执行
- 网络行为
- 仅限本地
- 安装命令数
- 26 条
档案由构建时根据 SKILL.md 与安装命令自动衍生，可能与作者实际意图存在差异。
需要注意： 未限定 allowed-tools，默认拥有全部工具权限。
---
name: nature-academic-search
description: >- This skill is split into two layers: Do not try to apply the search logic from memory or from…
category: 通用
runtime: 无特殊运行时
---
# nature-academic-search 输出预览
## PART A: 任务判断
- 适用问题：通用任务拆解、检查和交付。
- 输入要求：目标材料、限制条件、期望输出和验收方式。
- 证据边界：围绕“Routing protocol / 1. Load the manifest and the core layer / 2. Detect the workflow”读取原文规则，不把推断写成作者承诺。
## PART B: 执行结果
- **01** 任务判断：确认你的需求是否属于通用任务拆解、检查和交付，并标出输入、限制和预期结果。
- **02** 执行计划：优先按“Routing protocol / 1. Load the manifest and the core layer / 2. Detect the workflow”拆成步骤，说明每一步会读取什么、修改什么、产出什么。
- **03** 交付结果：给出可复制的命令、文件改动、检查清单或内容草稿，并说明如何继续迭代。
- **04** 风险边界：结合 读取文件、写入/修改文件、执行终端命令、主要在本地完成、通常不需要额外 API Key 给出执行前确认项。
## Running Rules
- 读取文件、写入/修改文件、执行终端命令；主要在本地完成；通常不需要额外 API Key。
- 先小样例验证，再放大到真实任务。
- 交付时同时给结果、检查口径和下一步迭代建议。原文没有稳定的斜杠命令要求。安装验证后通常全局生效，直接在对话里点名这个 Skill 并描述任务即可。
告诉 Agent 目标文件或材料、期望结果、不可改范围、是否允许联网或执行命令。本 Skill 的权限画像是：读取文件、写入/修改文件、执行终端命令。
先用一个小任务确认它会围绕“Routing protocol / 1. Load the manifest and the core layer / 2. Detect the workflow”工作；涉及文件或命令时，先看 diff、日志、预览或测试结果。
检查最终产物是否包含明确结果、必要证据和下一步动作；如果输出泛泛而谈，就补充输入、边界和验收标准后重跑。
---
name: nature-academic-search
description: >- This skill is split into two layers: Do not try to apply the search logic from memory or from…
category: 通用
source: Yuan1z0825/nature-skills
---
# nature-academic-search
## 什么时候使用
- 把通用方向的常用动作沉淀成 Agent 可调用的技能 适合处理通用任务拆解、检查、交付和复盘，核心价值是把输入、判断、执行、验证和交付边界固定下来，避免 Agent 泛泛回答。 把任务拆成可执行、可检查、可继续迭代的步骤；通常不需要额外…
- 面向通用任务拆解、检查和交付，优先处理能明确输入、步骤和验收标准的工作。
## 需要提供什么
- 目标材料、目录范围、期望结果和不可改动内容。
- 是否允许联网、执行命令、读写文件或调用外部服务。
## 执行规则
- 围绕「Routing protocol / 1. Load the manifest and the core layer / 2. Detect the workflow」组织步骤，不把推断写成作者事实。
- 读取文件、写入/修改文件、执行终端命令；主要在本地完成；通常不需要额外 API Key。
- 先跑小样例，确认结果可检查后再扩大任务范围。
## 输出要求
- 给出最终产物、关键证据、验证方式和下一步动作。
- 信息不足时标记 unknown，不编造命令、平台或依赖。作者原文负责流程事实；仓库文件负责来源和命令；流狐只补充适用场景、限制和质量判断。
skill "nature-academic-search" {
输入层 -> 用户目标 + 目标文件 + 禁止范围 + 验收标准
上下文层 -> Routing protocol / 1. Load the manifest and the core layer / 2. Detect the workflow
规则层 -> SKILL.md 触发条件 / 执行顺序 / 输出格式
运行层 -> 无特殊运行时 | 读取文件、写入/修改文件、执行终端命令 | 主要在本地完成
安全层 -> 通常不需要额外 API Key + 小任务验证 + diff / 日志复核
输出层 -> 可复制结果 + 检查清单 + 下一步迭代
}Academic Search — Router
This skill is split into two layers:
- A static layer under
static/that holds versioned, reusable content fragments (the MCP tool inventory and shared modules, and source routing plus operational rules). - A dynamic layer (this file plus
manifest.yaml) that detects which workflow the user needs and loads that workflow, reaching for shared modules and scripts only when a step needs them.
Do not try to apply the search logic from memory or from this router. Always load fragments from disk as described below.
Routing protocol
Follow these five steps every time the skill is invoked.
1. Load the manifest and the core layer
Read manifest.yaml. It declares the workflow axis, the allowed values, and the file paths each value maps to.
Also read every file listed under always_load:
static/core/tools.md— the MCP tool inventory (core search, extended search, PubMed utilities) and the shared-module map.static/core/routing-and-ops.md— the T1→T2→T3 source routing quick guide, environment setup, error handling, and limitations.
2. Detect the workflow
Map the user's need to one or more workflow values:
multi-source-search— find literature across sources.citation-verification— verify citations extracted from a document.mesh-strategy— build a MeSH/PubMed search strategy.citation-file-mgmt— convert/manage.nbib/.ris/.bibfiles.reference-mgmt— BibTeX, related-article discovery, ID conversion.
A combined request (for example search then export) may need more than one. State the detected workflow(s) in one short line before proceeding.
3. Load the matching workflow fragment(s)
Read the file mapped for each detected workflow (under references/workflows/). Do not read every workflow. Each workflow file links to the shared modules it needs.
4. Run the workflow using the loaded material
Apply the loaded material in this order:
- Core tools and routing (
core/tools.md,core/routing-and-ops.md) — which MCP tool for which need, and the T1→T2→T3 fallback chain that is the standard execution order across all workflows. - The workflow fragment — its specific steps.
- Shared modules and scripts on demand (dedup, citation parser, search strategy, RIS/BibTeX format, format converter).
Report specific tool failures and continue with remaining tools; broaden terms when there are no results; fall back to manual generation from MCP-fetched metadata if a script fails twice.
5. Reach for references only when needed
The files under references/ (and scripts/) are deep references, not defaults. Open them on demand per the references.on_demand table in the manifest — for example references/source-tiers.md for the full reliability classification, references/dedup-engine.md / references/citation-parser.md / references/search-strategy.md / references/ris-bibtex-format.md for the shared modules, and scripts/format-converter.py / scripts/preflight.py for the tooling.
Why this split
- The static layer is versioned and reviewable; the workflow files and shared modules were already factored this way.
- The dynamic layer keeps each invocation cheap: only the workflow the user needs enters context, instead of all five plus every module.
- The router itself is short on purpose. Update fragments and references, not this file, when adding scope.
- This structure mirrors the other nature-* skills (
nature-writing,nature-polishing,nature-reader,nature-paper2ppt,nature-figure,nature-citation,nature-response,nature-data).
先判断是否适合
作者设计意图
作者的方法与取舍
边界和复核