nature-academic-search

Name: nature-academic-search
Author: Yuan1z0825

3.6kinstalls1.8kforks

How to install nature-academic-search?

yuan1z0825/nature-skills/nature-academic-search

$npx -y skills add Yuan1z0825/nature-skills --skill nature-academic-search

Installs into the current project.

Summary

Multi-source literature search, citation verification, strict independent other-citation audits, article-level citation metric tables, influential citer profiling with citation-context extraction, MeSH search strategy, citation file management (.nbib/.ris/.bib conversion), and re

Files · 1

View on GitHub

SKILL.md

1	# Academic Search — Router
2
3	This skill is split into two layers:
4
5	- A static layer under `static/` that holds versioned, reusable content fragments (the MCP tool inventory and shared modules, and source routing plus operational rules).
6	- 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.
7
8	Do not try to apply the search logic from memory or from this router. Always load fragments from disk as described below.
9
10	## Routing protocol
11
12	Follow these five steps every time the skill is invoked.
13
14	### 1. Load the manifest and the core layer
15
16	Read [manifest.yaml](manifest.yaml). It declares the `workflow` axis, the allowed values, and the file paths each value maps to.
17
18	Also read every file listed under `always_load`:
19
20	- `static/core/tools.md` — the MCP tool inventory (core search, extended search, PubMed utilities) and the shared-module map.
21	- `static/core/routing-and-ops.md` — the T1→T2→T3 source routing quick guide, environment setup, error handling, and limitations.
22
23	### 2. Detect the workflow
24
25	Map the user's need to one or more `workflow` values:
26
27	- `multi-source-search` — find literature across sources.
28	- `citation-verification` — verify citations extracted from a document.
29	- `mesh-strategy` — build a MeSH/PubMed search strategy.
30	- `citation-file-mgmt` — convert/manage `.nbib`/`.ris`/`.bib` files.
31	- `reference-mgmt` — BibTeX, related-article discovery, ID conversion.
32	- `strict-other-citation-impact-audit` — determine strict independent other-citations, build article-level citation metric tables, identify high-profile citers (academy members, presidents/deans, talent-award holders, fellows, field leaders), and extract how they cited the target paper.
33
34	A combined request (for example search then export) may need more than one. State the detected workflow(s) in one short line before proceeding.
35
36	### 3. Load the matching workflow fragment(s)
37
38	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.
39
40	### 4. Run the workflow using the loaded material
41
42	Apply the loaded material in this order:
43
44	1. 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.
45	2. The workflow fragment — its specific steps.
46	3. Shared modules and scripts on demand (dedup, citation parser, search strategy, RIS/BibTeX format, format converter).
47
48	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.
49
50	### 5. Reach for references only when needed
51
52	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/academic_search.py` (no-MCP fallback discovery search) / `scripts/format-converter.py` / `scripts/preflight.py` for the tooling.
53
54	## Why this split
55
56	- The static layer is versioned and reviewable; the workflow files and shared modules were already factored this way.
57	- The dynamic layer keeps each invocation cheap: only the workflow the user needs enters context, instead of all six plus every module.
58	- The router itself is short on purpose. Update fragments and references, not this file, when adding scope.
59	- This structure mirrors the other nature-* skills (`nature-writing`, `nature-polishing`, `nature-reader`, `nature-paper2ppt`, `nature-figure`, `nature-citation`, `nature-response`, `nature-data`).

People who liked this also viewed

6 picks

Type

nature-academic-search

3.6kinstalls1.8kforks

View on GitHub

How to install nature-academic-search?

yuan1z0825/nature-skills/nature-academic-search

$npx -y skills add Yuan1z0825/nature-skills --skill nature-academic-search

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Academic Search — Router
2
3	This skill is split into two layers:
4
5	- A static layer under `static/` that holds versioned, reusable content fragments (the MCP tool inventory and shared modules, and source routing plus operational rules).
6	- 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.
7
8	Do not try to apply the search logic from memory or from this router. Always load fragments from disk as described below.
9
10	## Routing protocol
11
12	Follow these five steps every time the skill is invoked.
13
14	### 1. Load the manifest and the core layer
15
16	Read [manifest.yaml](manifest.yaml). It declares the `workflow` axis, the allowed values, and the file paths each value maps to.
17
18	Also read every file listed under `always_load`:
19
20	- `static/core/tools.md` — the MCP tool inventory (core search, extended search, PubMed utilities) and the shared-module map.
21	- `static/core/routing-and-ops.md` — the T1→T2→T3 source routing quick guide, environment setup, error handling, and limitations.
22
23	### 2. Detect the workflow
24
25	Map the user's need to one or more `workflow` values:
26
27	- `multi-source-search` — find literature across sources.
28	- `citation-verification` — verify citations extracted from a document.
29	- `mesh-strategy` — build a MeSH/PubMed search strategy.
30	- `citation-file-mgmt` — convert/manage `.nbib`/`.ris`/`.bib` files.
31	- `reference-mgmt` — BibTeX, related-article discovery, ID conversion.
32	- `strict-other-citation-impact-audit` — determine strict independent other-citations, build article-level citation metric tables, identify high-profile citers (academy members, presidents/deans, talent-award holders, fellows, field leaders), and extract how they cited the target paper.
33
34	A combined request (for example search then export) may need more than one. State the detected workflow(s) in one short line before proceeding.
35
36	### 3. Load the matching workflow fragment(s)
37
38	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.
39
40	### 4. Run the workflow using the loaded material
41
42	Apply the loaded material in this order:
43
44	1. 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.
45	2. The workflow fragment — its specific steps.
46	3. Shared modules and scripts on demand (dedup, citation parser, search strategy, RIS/BibTeX format, format converter).
47
48	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.
49
50	### 5. Reach for references only when needed
51
52	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/academic_search.py` (no-MCP fallback discovery search) / `scripts/format-converter.py` / `scripts/preflight.py` for the tooling.
53
54	## Why this split
55
56	- The static layer is versioned and reviewable; the workflow files and shared modules were already factored this way.
57	- The dynamic layer keeps each invocation cheap: only the workflow the user needs enters context, instead of all six plus every module.
58	- The router itself is short on purpose. Update fragments and references, not this file, when adding scope.
59	- This structure mirrors the other nature-* skills (`nature-writing`, `nature-polishing`, `nature-reader`, `nature-paper2ppt`, `nature-figure`, `nature-citation`, `nature-response`, `nature-data`).

People who liked this also viewed

6 picks

Type