nsfc-bib-manager_skill

This skill helps you manage verified BibTeX entries by adding citations only after data verification and writing to bib files.
  • Python

787

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill huangwb8/chineseresearchlatex --skill nsfc-bib-manager

  • config.yaml200 B
  • SKILL.md1.5 KB

Overview

This skill manages verified bibliographic entries for LaTeX projects and writes BibTeX into the project repository. I add or verify paper metadata (title, authors, year, journal, DOI) and insert entries into references/ccs.bib or references/mypaper.bib while avoiding fabricated data. It is triggered only when the user explicitly asks to add citations, update .bib files, or verify references.

How this skill works

I first confirm the claim or statement that needs supporting citations to avoid adding irrelevant references. I search online sources and publisher metadata (prefer MCP or publisher records) to verify title, authors, year, journal, and DOI. If metadata are fully verifiable, I generate a minimal BibTeX entry and append it to the correct .bib file; if some fields cannot be verified, I mark them as "to-verify" instead of inventing values. Finally, I recommend the corresponding \cite{key} insertion point in the target .tex file without editing bibliography style files.

When to use it

  • User explicitly requests adding citations, e.g., "add references", "write BibTeX", or "update .bib".
  • User asks to verify or correct paper metadata (title/author/year/journal/DOI).
  • Preparing a manuscript and you want verified, machine-readable bibliography entries.
  • Migrating or consolidating references into references/ccs.bib or references/mypaper.bib.
  • Ensuring no hallucinated citations are introduced into the LaTeX source.

Best practices

  • Always state the specific claim or sentence that needs a citation before adding references.
  • Prefer authoritative sources: publisher pages, CrossRef, DOI registries, and MCP where available.
  • Only populate fields I can verify; mark unresolved fields as "to-verify" rather than guessing.
  • Write minimal, standard BibTeX entries and append to the appropriate file (ccs.bib for general refs, mypaper.bib for applicant papers).
  • Do not change bibliography style or reference.tex; respect existing formatting and citation workflow.

Example use cases

  • User: "Add a citation for the algorithm runtime bound in section 2" — I verify relevant papers and add BibTeX to references/ccs.bib and suggest \cite{key}.
  • User: "Update .bib with my recent publication" — I verify the applicant's paper metadata and add it to references/mypaper.bib.
  • User: "Check DOI and publication info for Smith 2020" — I confirm metadata from CrossRef and correct the .bib entry if needed.
  • User: "Write BibTeX for a conference paper I found" — I fetch publisher metadata, create a verified BibTeX entry, and mark any missing fields as to-verify.

FAQ

I will not invent values. Missing fields are marked "to-verify" and I will still produce a minimal BibTeX entry that you can complete once verified.

Which .bib file will you modify?

General verified literature goes to references/ccs.bib. Papers authored by the applicant go to references/mypaper.bib. I follow this priority automatically.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational