AGENT SKILL

hugging-face-papers

Read and analyze Hugging Face paper pages or arXiv papers with markdown and papers API metadata.

License 许可
MIT
最近更新
2026-11-10
Stars
★ 1
Forks
0

01 前言 Front Matter

name
hugging-face-papers
risk
unknown
source
https://github.com/huggingface/skills/tree/main/skills/huggingface-papers
description
Read and analyze Hugging Face paper pages or arXiv papers with markdown and papers API metadata.

03 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:

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.

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.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

04 同仓库更多 Skills

YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

vercel-sandbox

Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

slack

Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

electron

Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

dogfood

Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

shadcn

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.

★ 1