` | Wikipedia | `Wikipedia_<Title>.md` | OEIS A-numbers entered bare (e.g. `A000045`) without a URL should be treated as if the user typed `https://oeis.org/A000045`. **Naming convention for files:** - Papers: `Author_Year_ShortTitle.pdf` (first author last name, year, 2-4 word title) - Notebooks: `Author_Year_ShortTitle.nb` - Repos: directory name matching the repo name - Other: descriptive name with extension ### 2. Create wiki article Article prose (Summary, Use in this project) follows the `Semantic line breaks` toggle in `AGENTS.md` § *Source formatting*; the `## Recover` lines stay as `Key: Value`. Write `Wiki/Resources/Name.md`: ```markdown # Author Year — Short Title *[[ LLM Generated ]]* Full citation. *Journal/venue*, volume, pages, year. ## Summary What it is and why it matters to this project. Key results or contents. 2-3 paragraphs. ## Use in this project How this resource connects to or supports the current work. ## Recover Download: https://doi.org/... Target: Resources/Author_Year_ShortTitle.pdf ``` #### Recover section variants **Paper with DOI:** ```markdown ## Recover Download: https://doi.org/10.1088/0951-7715/4/2/002 Target: Resources/Moore_1991_GeneralizedShifts.pdf ``` **arXiv paper:** ```markdown ## Recover Download: https://arxiv.org/pdf/0810.5625 Target: Resources/Ollivier_2009_RicciCurvature.pdf ``` **Git repo:** ```markdown ## Recover Clone: https://github.com/org/repo Target: Resources/RepoName ``` **Wolfram Community notebook:** ```markdown ## Recover Download: https://community.wolfram.com/... Target: Resources/Author_Year_Title.nb ``` **Web page (no download):** ```markdown ## Recover URL: https://example.com/page ``` **Tool/package:** ```markdown ## Recover Install: pip install package-name ``` **MathWorld / nLab / DLMF / Wikipedia entry (URL-only):** ```markdown ## Recover URL: https://mathworld.wolfram.com/RiemannZetaFunction.html ``` **OEIS sequence:** ```markdown ## Recover URL: https://oeis.org/A000045 OEIS: A000045 ``` The `OEIS:` key is optional but useful for offline cross-reference (recovery scripts can use it to ping the OEIS JSON API and confirm the sequence is unchanged). The `## Recover` section is machine-readable. Each line is `Key: Value`. The recovery script parses these to rebuild `Resources/`. ### 3. Update wiki 1. Add one-line entry to `Wiki/Index.md` under Resources: ```markdown - [Author Year — Short Title](Resources/Name.md) — one-line summary ``` 2. Add cross-links to related articles' See also sections ### 4. Read and summarize (if paper) For papers specifically: 1. **Prefer LaTeX source** — use `mcp__arxiv-latex-mcp` to read sections, extract equations, and definitions directly from LaTeX. This is critical for accurate Wolfram implementations of formulas. 2. Fall back to `mcp__arxiv__read_paper` or PDF reading if LaTeX source is unavailable. 3. Write a substantive summary — not just the abstract, but key results, theorems, definitions that matter for the project. Include important equations in LaTeX form. 4. Note specific connections to the current work in "Use in this project" ## Batch resource addition When adding multiple resources at once (e.g., during initial exploration): 1. Download all files first 2. Create all wiki articles 3. Add all index entries in one update 4. Log once with count: "Added N resources: [list]" ## Resource recovery `Resources/` is gitignored. Before giving the local recovery command, ensure `Scripts/recover_resources.sh` exists. If absent, create `Scripts/` and copy `${PLUGIN_ROOT}/scripts/recover_resources.sh` there, preserving its executable mode; never replace an existing or customized helper. This installs the helper only; adding a resource does not run bulk recovery. To rebuild from scratch: ```bash Scripts/recover_resources.sh ``` The script: 1. Scans all `Wiki/Resources/*.md` files 2. Reads each `## Recover` section 3. Parses `Download:` lines → `curl` to `Target:` path 4. Parses `Clone:` lines → `git clone` to `Target:` path 5. Parses `Install:` lines → runs install command 6. Submodules recovered via `git submodule update --init --recursive` **Git submodules:** When adding a repo that the project depends on at build time (e.g., a Lean dependency, a Wolfram paclet), prefer `git submodule add` over a plain clone. The submodule is tracked in `.gitmodules` and survives across clones. Add a `!Resources/SubmoduleName/` exception to `.gitignore` so the submodule directory isn't ignored. The Recover section uses `Submodule:` instead of `Clone:`: ```markdown ## Recover Submodule: https://github.com/org/repo Resources/RepoName ``` For non-dependency repos (reference code, examples), a plain clone is fine. ## What counts as a resource Anything external that informs or supports the project: - Papers (PDFs) - Git repos / submodules - Notebooks (.nb, .ipynb) - Datasets, spreadsheets - Tools, packages, libraries - Web pages, blog posts, documentation ## Integration with other skills - `project-create` runs this pipeline for every reference paper it downloads. - `wiki-search-math` and `wiki-search-wolfram` hand their kept results here. - `paper-cite` produces the BibTeX entry when the resource is also cited in a paper or journal. - `project-provenance` mirrors the `## Recover` convention for prompts. ## When NOT to use - Internal artifacts (code, notebooks, wiki articles the project itself produces) — they are not resources. - A link mentioned in passing that nothing depends on — adding it is noise.

--- name: wiki-add-resource description: > Add a resource (paper, repo, notebook, dataset, tool, web page) to the wiki. Downloads the file locally (gitignored), creates a wiki article with a Recover section for reproducibility, and updates the index. Use when the user says "add this paper", "save this resource", "note this repo", or when encountering a new reference during work. Also use during project-create to register discovered papers and Wolfram Community resources. --- Before acting, read [the runtime guidance](../../RUNTIME.md). # Resource Management Resources have two layers: 1. **Wiki article** (`Wiki/Resources/Name.md`) — tracked in git, permanent. Contains citation, summary, and a machine-readable `## Recover` section. 2. **Local file** (`Resources/`) — gitignored, ephemeral. The actual PDF, repo clone, notebook, or dataset. The wiki article is the source of truth. Local files can be rebuilt from `## Recover` sections via `Scripts/recover_resources.sh`. ## When to use - The user says "add this paper", "save this resource", "note this repo", or hands over a URL, PDF, repo, notebook, or dataset worth keeping. - During `project-create` literature setup, and when `wiki-search-math` / `wiki-search-wolfram` results are worth registering. - When an external dependency enters the project and needs a `## Recover` line. ## Steps ### 1. Download (if applicable) Create `Resources/` if it doesn't exist. | Type | Action | |------|--------| | Paper (PDF) | Download to `Resources/Author_Year_ShortTitle.pdf` | | arXiv paper | Use `mcp__arxiv__download_paper` → `Resources/` | | Git repo | Clone to `Resources/RepoName/` or add as git submodule | | Wolfram notebook | Download to `Resources/Author_Year_Title.nb` | | Dataset | Download to `Resources/DatasetName.ext` | | Web page | No download — just the URL | | Tool/package | Download or note install command | | **MathWorld entry** | No download — wiki article with URL + summary | | **nLab page** | No download — wiki article with URL + summary | | **OEIS sequence** | No download — wiki article with A-number + first terms | | **DLMF formula/section** | No download — wiki article with locator + URL | | **Wikipedia article** | No download — wiki article with URL + summary | ### URL-based source detection When a URL is the input, infer the source from the host + path: | URL pattern | Source | Article name | |-------------|--------|--------------| | `mathworld.wolfram.com/.html` | MathWorld | `MathWorld_.md` | | `ncatlab.org/nlab/show/` | nLab | `nLab_.md` | | `oeis.org/A######` | OEIS | `OEIS_A######.md` | | `dlmf.nist.gov/` | DLMF | `DLMF_.md` | | `en.wikipedia.org/wiki/` | Wikipedia | `Wikipedia_<Title>.md` | OEIS A-numbers entered bare (e.g. `A000045`) without a URL should be treated as if the user typed `https://oeis.org/A000045`. **Naming convention for files:** - Papers: `Author_Year_ShortTitle.pdf` (first author last name, year, 2-4 word title) - Notebooks: `Author_Year_ShortTitle.nb` - Repos: directory name matching the repo name - Other: descriptive name with extension ### 2. Create wiki article Article prose (Summary, Use in this project) follows the `Semantic line breaks` toggle in `AGENTS.md` § *Source formatting*; the `## Recover` lines stay as `Key: Value`. Write `Wiki/Resources/Name.md`: ```markdown # Author Year — Short Title *[[ LLM Generated ]]* Full citation. *Journal/venue*, volume, pages, year. ## Summary What it is and why it matters to this project. Key results or contents. 2-3 paragraphs. ## Use in this project How this resource connects to or supports the current work. ## Recover Download: https://doi.org/... Target: Resources/Author_Year_ShortTitle.pdf ``` #### Recover section variants **Paper with DOI:** ```markdown ## Recover Download: https://doi.org/10.1088/0951-7715/4/2/002 Target: Resources/Moore_1991_GeneralizedShifts.pdf ``` **arXiv paper:** ```markdown ## Recover Download: https://arxiv.org/pdf/0810.5625 Target: Resources/Ollivier_2009_RicciCurvature.pdf ``` **Git repo:** ```markdown ## Recover Clone: https://github.com/org/repo Target: Resources/RepoName ``` **Wolfram Community notebook:** ```markdown ## Recover Download: https://community.wolfram.com/... Target: Resources/Author_Year_Title.nb ``` **Web page (no download):** ```markdown ## Recover URL: https://example.com/page ``` **Tool/package:** ```markdown ## Recover Install: pip install package-name ``` **MathWorld / nLab / DLMF / Wikipedia entry (URL-only):** ```markdown ## Recover URL: https://mathworld.wolfram.com/RiemannZetaFunction.html ``` **OEIS sequence:** ```markdown ## Recover URL: https://oeis.org/A000045 OEIS: A000045 ``` The `OEIS:` key is optional but useful for offline cross-reference (recovery scripts can use it to ping the OEIS JSON API and confirm the sequence is unchanged). The `## Recover` section is machine-readable. Each line is `Key: Value`. The recovery script parses these to rebuild `Resources/`. ### 3. Update wiki 1. Add one-line entry to `Wiki/Index.md` under Resources: ```markdown - [Author Year — Short Title](Resources/Name.md) — one-line summary ``` 2. Add cross-links to related articles' See also sections ### 4. Read and summarize (if paper) For papers specifically: 1. **Prefer LaTeX source** — use `mcp__arxiv-latex-mcp` to read sections, extract equations, and definitions directly from LaTeX. This is critical for accurate Wolfram implementations of formulas. 2. Fall back to `mcp__arxiv__read_paper` or PDF reading if LaTeX source is unavailable. 3. Write a substantive summary — not just the abstract, but key results, theorems, definitions that matter for the project. Include important equations in LaTeX form. 4. Note specific connections to the current work in "Use in this project" ## Batch resource addition When adding multiple resources at once (e.g., during initial exploration): 1. Download all files first 2. Create all wiki articles 3. Add all index entries in one update 4. Log once with count: "Added N resources: [list]" ## Resource recovery `Resources/` is gitignored. Before giving the local recovery command, ensure `Scripts/recover_resources.sh` exists. If absent, create `Scripts/` and copy `${PLUGIN_ROOT}/scripts/recover_resources.sh` there, preserving its executable mode; never replace an existing or customized helper. This installs the helper only; adding a resource does not run bulk recovery. To rebuild from scratch: ```bash Scripts/recover_resources.sh ``` The script: 1. Scans all `Wiki/Resources/*.md` files 2. Reads each `## Recover` section 3. Parses `Download:` lines → `curl` to `Target:` path 4. Parses `Clone:` lines → `git clone` to `Target:` path 5. Parses `Install:` lines → runs install command 6. Submodules recovered via `git submodule update --init --recursive` **Git submodules:** When adding a repo that the project depends on at build time (e.g., a Lean dependency, a Wolfram paclet), prefer `git submodule add` over a plain clone. The submodule is tracked in `.gitmodules` and survives across clones. Add a `!Resources/SubmoduleName/` exception to `.gitignore` so the submodule directory isn't ignored. The Recover section uses `Submodule:` instead of `Clone:`: ```markdown ## Recover Submodule: https://github.com/org/repo Resources/RepoName ``` For non-dependency repos (reference code, examples), a plain clone is fine. ## What counts as a resource Anything external that informs or supports the project: - Papers (PDFs) - Git repos / submodules - Notebooks (.nb, .ipynb) - Datasets, spreadsheets - Tools, packages, libraries - Web pages, blog posts, documentation ## Integration with other skills - `project-create` runs this pipeline for every reference paper it downloads. - `wiki-search-math` and `wiki-search-wolfram` hand their kept results here. - `paper-cite` produces the BibTeX entry when the resource is also cited in a paper or journal. - `project-provenance` mirrors the `## Recover` convention for prompts. ## When NOT to use - Internal artifacts (code, notebooks, wiki articles the project itself produces) — they are not resources. - A link mentioned in passing that nothing depends on — adding it is noise. - Emails, chat logs, slide decks