mcpbeat

Update Cite Count

kimtth/update-cite-count

Guidelines for updating citation counts for papers in the section files using the `update_citation_counts.py` tool. USE FOR: Updating citation counts for papers listed in the section files to keep information current. DO NOT USE FOR: 1) Adding new papers to the section files; 2) Classifying entries into sections.

361 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
405
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/kimtth/azure-openai-llm-wiki --skill update-cite-count

The instruction itself

1 sections, as written by the author

Workflow: Updating Citation Counts for Papers

To keep the citation counts for papers in the section files up to date, follow these guidelines when using the update_citation_counts.py tool.

  • The output count is used for the inline ranked sections in section/best_practices.md: RAG Research (Ranked by cite count >=100) and Agent Research (Ranked by cite count >=100).
  • Run update_citation_counts.py directly to fetch the latest Semantic Scholar citation counts for papers already listed in those two sections. Use --dry-run first when reviewing a large update.
  • The script updates citation counts in place when counts changed. It does not add new papers, rebuild section indexes, or update generated pool files.
  • After updating, review section/best_practices.md to confirm the counts changed correctly and the ranked order is still accurate. If counts change enough to affect ordering, manually reorder the entries.
.venv\Scripts\python.exe code/update_citation_counts.py --dry-run
.venv\Scripts\python.exe code/update_citation_counts.py

How to use it

Copy the folder

Take kimtth/update-cite-count from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.