本文へ移動
cccskills
無料GitHub で公開

huggingface-papers

Look up and read Hugging Face paper pages in markdown, and use the papers API for structured metadata such as authors, linked models/datasets/spaces, Github repo and project page. Use when the user shares a Hugging Face paper page URL, an arXiv URL or ID, or asks to summarize, explain, or analyze an AI research paper.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md9.1 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Hugging Face Paper Pages

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.

When to Use

  • User shares a Hugging Face paper page URL (e.g. https://huggingface.co/papers/2602.08025)
  • User shares a Hugging Face markdown paper page URL (e.g. https://huggingface.co/papers/2602.08025.md)
  • User shares an arXiv URL (e.g. https://arxiv.org/abs/2602.08025 or https://arxiv.org/pdf/2602.08025)
  • User mentions a arXiv ID (e.g. 2602.08025)
  • User asks you to summarize, explain, or analyze an AI research paper

Parsing the paper ID

It's recommended to parse the paper ID (arXiv ID) from whatever the user provides:

InputPaper ID
https://huggingface.co/papers/2602.080252602.08025
https://huggingface.co/papers/2602.08025.md2602.08025
https://arxiv.org/abs/2602.080252602.08025
https://arxiv.org/pdf/2602.080252602.08025
2602.08025v12602.08025v1
2602.080252602.08025

This allows you to provide the paper ID into any of the hub API endpoints mentioned below.

Fetch the paper page as markdown

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}"

Paper Pages API Endpoints

All endpoints use the base URL https://huggingface.co.

Get structured metadata

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:

  • authors (names and Hugging Face usernames, in case they have claimed the paper)
  • media URLs (uploaded when submitting the paper to Daily Papers)
  • summary (abstract) and AI-generated summary
  • project page and GitHub repository
  • organization and engagement metadata (number of upvotes)

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 paper authorship

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}"
  }'
  • Endpoint: POST /api/settings/papers/claim
  • Body:
    • paperId (string, required): arXiv paper identifier being claimed
    • claimAuthorId (string): author entry on the paper being claimed, 24-char hex ID
    • targetUserId (string): HF user who should receive the claim, 24-char hex ID
  • Response: paper authorship claim result, including the claimed paper ID

Get daily papers

Fetch 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"
  • Endpoint: GET /api/daily_papers
  • Query parameters:
    • p (integer): page number
    • limit (integer): number of results, between 1 and 100
    • date (string): RFC 3339 full-date, for example 2017-07-21
    • week (string): ISO week, for example 2024-W03
    • month (string): month value, for example 2024-01
    • submitter (string): filter by submitter
    • sort (enum): publishedAt or trending
  • Response: list of daily papers

List papers

List arXiv papers sorted by published date:

curl -s -H "Authorization: Bearer $HF_TOKEN" \
  "https://huggingface.co/api/papers?cursor={CURSOR}&limit=20"
  • Endpoint: GET /api/papers
  • Query parameters:
    • cursor (string): pagination cursor
    • limit (integer): number of results, between 1 and 100
  • Response: list of papers

Search papers

Perform 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.

  • Endpoint: GET /api/papers/search
  • Query parameters:
    • q (string): search query, max length 250
    • limit (integer): number of results, between 1 and 120
  • Response: matching papers

Index a paper

Insert 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}"
  }'
  • Endpoint: POST /api/papers/index
  • Body:
    • arxivId (string, required): arXiv ID to index, for example 2301.00001
  • Pattern: ^\d{4}\.\d{4,5}$
  • Response: empty JSON object on success

Update paper links

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}"
  }'
  • Endpoint: POST /api/papers/{paperId}/links
  • Path parameters:
    • paperId (string, required): Hugging Face paper object ID
  • Body:
    • githubRepo (string, nullable): GitHub repository URL
    • organizationId (string, nullable): organization ID, 24-char hex ID
    • projectPage (string, nullable): project page URL
  • Response: empty JSON object on success

Error Handling

  • 404 on https://huggingface.co/papers/{PAPER_ID} or md endpoint: the paper is not indexed on Hugging Face paper pages yet.
  • 404 on /api/papers/{PAPER_ID}: the paper may not be indexed on Hugging Face paper pages yet.
  • Paper ID not found: verify the extracted arXiv ID, including any version suffix

Fallbacks

If the Hugging Face paper page does not contain enough detail for the user's question:

  • Check the regular paper page at https://huggingface.co/papers/{PAPER_ID}
  • Fall back to the arXiv page or PDF for the original source:
    • https://arxiv.org/abs/{PAPER_ID}
    • https://arxiv.org/pdf/{PAPER_ID}

Notes

  • No authentication is required for public paper pages.
  • Write endpoints such as claim authorship, index paper, and update paper links require Authorization: Bearer $HF_TOKEN.
  • Prefer the .md endpoint for reliable machine-readable output.
  • Prefer /api/papers/{PAPER_ID} when you need structured JSON fields instead of page markdown.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

hf-cli

無料

Hugging Face Hub CLI (`hf`) for downloading, uploading, and managing models, datasets, spaces, buckets, repos, papers, jobs, and more on the Hugging Face Hub. Use when: handling authentication; managing local cache; managing Hugging Face Buckets; running or scheduling jobs on Hugging Face infrastructure; managing Hugging Face repos; discussions and pull requests; browsing models, datasets and spaces; reading, searching, or browsing academic papers; managing collections; querying datasets; configuring spaces; setting up webhooks; or deploying and managing HF Inference Endpoints. Make sure to use this skill whenever the user mentions 'hf', 'huggingface', 'Hugging Face', 'huggingface-cli', or 'hugging face cli', or wants to do anything related to the Hugging Face ecosystem and to AI and ML in general. Also use for cloud storage needs like training checkpoints, data pipelines, or agent traces. Use even if the user doesn't explicitly ask for a CLI command. Replaces the deprecated `huggingface-cli`.

日本語の概要は準備中です。原文の説明を表示しています。

huggingface/skills1.1万2026年10月9日 更新

Discover the user's local AWS context (active profile, region, account ID, caller identity) at the start of any AWS task. Use this skill before any other AWS work — deploying to SageMaker, creating resources, calling AWS APIs, or anything that touches an AWS account. Use it especially when the user has not specified a region or profile explicitly, when they say things like "use my AWS account", "deploy to AWS", "use my profile", or when about to make any AWS CLI or SDK call. Never guess the region or account ID — always use this skill to read it from the local configuration first.

日本語の概要は準備中です。原文の説明を表示しています。

huggingface/skills1.1万2026年10月9日 更新

Set up an isolated Python environment for SageMaker / AWS work, with the right Python version and current boto3. Use this skill whenever Python code will be executed for a SageMaker deployment, training job, or any AWS automation — including when about to run `pip install`, when about to invoke `boto3`, when creating or activating a virtualenv, or when the user asks to "set up the environment". Never use system Python and never `pip install` into it. Always isolate. This skill prevents the most common failure modes: wrong Python version, dependency conflicts, and stale SDKs.

日本語の概要は準備中です。原文の説明を表示しています。

huggingface/skills1.1万2026年10月9日 更新

Plan and coordinate the deployment of a model to Amazon SageMaker AI. Use this skill whenever the user wants to deploy, host, serve, or expose a model on SageMaker or AWS — including phrases like "deploy a model", "host this LLM on AWS", "serve this embedding model", "deploy a reranker", "deploy a text-to-image / diffusion model", "host this for async inference", "create an endpoint", "serve my fine-tuned model", or any request that involves making a model available for inference on AWS. Use this even when the user is vague (e.g. "I just want to get this running on AWS, you figure it out"). Works for text-generation LLMs, embedding models, rerankers, classifiers, text-to-image / diffusion models — picks the right serving stack and chooses between real-time and async inference. This is the entry-point skill for SageMaker deployment work — it asks clarifying questions, picks a deployment pathway, and coordinates the other deployment skills.

日本語の概要は準備中です。原文の説明を表示しています。

huggingface/skills1.1万2026年10月9日 更新

Ensure a usable SageMaker execution role exists before deploying or training. Use this skill whenever about to create a SageMaker endpoint, model, training job, or any resource that requires an execution role. Use it especially when the user has not provided a role ARN explicitly, when scripts are about to call `iam:CreateRole`, or when an AccessDenied error mentions an IAM action. Never blindly call `iam:CreateRole` — always check for existing roles first. This skill prevents the most common SageMaker deployment failure: trying to create IAM resources from an SSO principal that has no IAM write permissions.

日本語の概要は準備中です。原文の説明を表示しています。

huggingface/skills1.1万2026年10月9日 更新

Create a SageMaker endpoint (real-time, real-time scale-to-zero, or async) with autoscaling, CloudWatch alarms, and tagging enabled by default. Use this skill whenever about to create a SageMaker endpoint, write deployment code that calls `create_endpoint`, or finalize a deployment after the image URI and IAM role are known. Provides deploy.py for real-time endpoints, deploy_ic.py for real-time endpoints that scale to zero instances via inference components, and deploy_async.py for async endpoints (also scale-to-zero). This is the last step in the SageMaker deployment workflow. Never generate a bare `create_endpoint` call without these defaults — endpoints without autoscaling or alarms are demos, not deployments.

日本語の概要は準備中です。原文の説明を表示しています。

huggingface/skills1.1万2026年10月9日 更新

huggingface のスキルをすべて見る

このスキルの問題を報告する