Internal Comms
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use …
Hugging Face Paper pages (hf.co/papers) is a platform built on top of arXiv (arxiv.org), specifically for research papers in the field of artificial intelligence (AI) and computer science. Hugging Face users can submit their paper at hf.co/papers/submit, which features it on the Daily Papers feed (hf.co/papers). Each day, users can upvote papers and comment on papers. Each paper page allows authors to:
- claim their paper (by clicking their name on the authors field). This makes the paper page appear on their Hugging Face profile.
- link the associated model checkpoints, datasets and Spaces by including the HF paper or arXiv URL in the model card, dataset card or README of the Space
- link the Github repository and/or project page URLs
- link the HF organization. This also makes the paper page appear on the Hugging Face organization page.
Whenever someone mentions a HF paper or arXiv abstract/PDF URL in a model card, dataset card or README of a Space repository, the paper will be automatically indexed. Note that not all papers indexed on Hugging Face are also submitted to daily papers. The latter is more a manner of promoting a research paper. Papers can only be submitted to daily papers up until 14 days after their publication date on arXiv.
The Hugging Face team has built an easy-to-use API to interact with paper pages. Content of the papers can be fetched as markdown, or structured metadata can be returned such as author names, linked models/datasets/spaces, linked Github repo and project page.
https://huggingface.co/papers/2602.08025)https://huggingface.co/papers/2602.08025.md)https://arxiv.org/abs/2602.08025 or https://arxiv.org/pdf/2602.08025)2602.08025)It's recommended to parse the paper ID (arXiv ID) from whatever the user provides:
| Input | Paper ID |
|---|---|
https://huggingface.co/papers/2602.08025 |
2602.08025 |
https://huggingface.co/papers/2602.08025.md |
2602.08025 |
https://arxiv.org/abs/2602.08025 |
2602.08025 |
https://arxiv.org/pdf/2602.08025 |
2602.08025 |
2602.08025v1 |
2602.08025v1 |
2602.08025 |
2602.08025 |
This allows you to provide the paper ID into any of the hub API endpoints mentioned below.
The content of a paper can be fetched as markdown like so:
curl -s "https://huggingface.co/papers/{PAPER_ID}.md"
This should return the Hugging Face paper page as markdown. This relies on the HTML version of the paper at https://arxiv.org/html/{PAPER_ID}.
There are 2 exceptions: - Not all arXiv papers have an HTML version. If the HTML version of the paper does not exist, then the content falls back to the HTML of the Hugging Face paper page. - If it results in a 404, it means the paper is not yet indexed on hf.co/papers. See Error handling for info.
Alternatively, you can request markdown from the normal paper page URL, like so:
curl -s -H "Accept: text/markdown" "https://huggingface.co/papers/{PAPER_ID}"
All endpoints use the base URL https://huggingface.co.
Fetch the paper metadata as JSON using the Hugging Face REST API:
curl -s "https://huggingface.co/api/papers/{PAPER_ID}"
This returns structured metadata that can include:
To find models linked to the paper, use:
curl https://huggingface.co/api/models?filter=arxiv:{PAPER_ID}
To find datasets linked to the paper, use:
curl https://huggingface.co/api/datasets?filter=arxiv:{PAPER_ID}
To find spaces linked to the paper, use:
curl https://huggingface.co/api/spaces?filter=arxiv:{PAPER_ID}
Claim authorship of a paper for a Hugging Face user:
curl "https://huggingface.co/api/settings/papers/claim" \
--request POST \
--header "Content-Type: application/json" \
--header "Authorization: Bearer $HF_TOKEN" \
--data '{
"paperId": "{PAPER_ID}",
"claimAuthorId": "{AUTHOR_ENTRY_ID}",
"targetUserId": "{USER_ID}"
}'
POST /api/settings/papers/claimpaperId (string, required): arXiv paper identifier being claimedclaimAuthorId (string): author entry on the paper being claimed, 24-char hex IDtargetUserId (string): HF user who should receive the claim, 24-char hex IDFetch the Daily Papers feed:
curl -s -H "Authorization: Bearer $HF_TOKEN" \
"https://huggingface.co/api/daily_papers?p=0&limit=20&date=2017-07-21&sort=publishedAt"
GET /api/daily_papersp (integer): page numberlimit (integer): number of results, between 1 and 100date (string): RFC 3339 full-date, for example 2017-07-21week (string): ISO week, for example 2024-W03month (string): month value, for example 2024-01submitter (string): filter by submittersort (enum): publishedAt or trendingList arXiv papers sorted by published date:
curl -s -H "Authorization: Bearer $HF_TOKEN" \
"https://huggingface.co/api/papers?cursor={CURSOR}&limit=20"
GET /api/paperscursor (string): pagination cursorlimit (integer): number of results, between 1 and 100Perform hybrid semantic and full-text search on papers:
curl -s -H "Authorization: Bearer $HF_TOKEN" \
"https://huggingface.co/api/papers/search?q=vision+language&limit=20"
This searches over the paper title, authors, and content.
GET /api/papers/searchq (string): search query, max length 250limit (integer): number of results, between 1 and 120Insert a paper from arXiv by ID. If the paper is already indexed, only its authors can re-index it:
curl "https://huggingface.co/api/papers/index" \
--request POST \
--header "Content-Type: application/json" \
--header "Authorization: Bearer $HF_TOKEN" \
--data '{
"arxivId": "{ARXIV_ID}"
}'
POST /api/papers/indexarxivId (string, required): arXiv ID to index, for example 2301.00001^\d{4}\.\d{4,5}$Update the project page, GitHub repository, or submitting organization for a paper. The requester must be the paper author, the Daily Papers submitter, or a papers admin:
curl "https://huggingface.co/api/papers/{PAPER_OBJECT_ID}/links" \
--request POST \
--header "Content-Type: application/json" \
--header "Authorization: Bearer $HF_TOKEN" \
--data '{
"projectPage": "https://example.com",
"githubRepo": "https://github.com/org/repo",
"organizationId": "{ORGANIZATION_ID}"
}'
POST /api/papers/{paperId}/linkspaperId (string, required): Hugging Face paper object IDgithubRepo (string, nullable): GitHub repository URLorganizationId (string, nullable): organization ID, 24-char hex IDprojectPage (string, nullable): project page URLhttps://huggingface.co/papers/{PAPER_ID} or md endpoint: the paper is not indexed on Hugging Face paper pages yet./api/papers/{PAPER_ID}: the paper may not be indexed on Hugging Face paper pages yet.If the Hugging Face paper page does not contain enough detail for the user's question:
https://huggingface.co/papers/{PAPER_ID}https://arxiv.org/abs/{PAPER_ID}https://arxiv.org/pdf/{PAPER_ID}Authorization: Bearer $HF_TOKEN..md endpoint for reliable machine-readable output./api/papers/{PAPER_ID} when you need structured JSON fields instead of page markdown.Source: Hugging Face · Apache-2.0 · SHA-256 shown alongside the download.
License file included. A license and checksum are not a security certification. Review package instructions and scripts before running them.
huggingface-papers/BB-SKILLS-REVIEW.json1057 byteshuggingface-papers/LICENSE.upstream.txt11357 byteshuggingface-papers/SKILL.md9348 byteshuggingface-papers/SOURCE.txt194 byteshuggingface-papers/upstream-notices/LICENSE11357 bytesSource and packaging checks recorded on 2026-10-03. These notes are not safety certification or measured task performance.
An HTTP-capable client; access to Hugging Face paper pages and APIs.
Check cited papers directly. Skill redistribution does not grant redistribution rights to the papers themselves.
Upstream commit: ca0325bb20b2d0a1b2efa893670c4c72f79e707b
Runtime status: not tested by this catalog. Configure your client and test the skill in your own environment.
Records are supplied by the site administrator and bound to a specific package. They are not third-party safety certification. This page does not execute skills.
No published scenario records yet. Resource availability and download counts do not imply measured task performance.
Be the first to share your experience.
Sign in to leave a review →A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use …
Help address review/issue comments on the open GitHub PR for the current branch using gh CLI; verify gh auth first and prompt the user to au…
Find GGUF models, compare quantization choices, and plan llama.cpp inference for your own hardware.
Compare reliable sources, track uncertainty, and turn findings into a concise decision brief.