SkillsAdd

lylll9436/paper-polish-workflow-skill

get-paper

>- Search Google Scholar via Chrome DevTools MCP, let the user select a paper, and retrieve its BibTeX entry. 通过 Chrome DevTools MCP 在 Google Scholar 搜索论文并获取 BibTeX 引用。

First seen Apr 2, 2026

Installation

$ npx skills add lylll9436/paper-polish-workflow-skill --skill get-paper
View on skills.sh ↗ GitHub repository ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

find-skills Same topic
vercel-labs/skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "fi…

3.3M installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-prepare Same topic
microsoft/azure-skills

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Te…

568.3K installs

Also in this package

Other skills from lylll9436/paper-polish-workflow-skill · top by installs.

npx skills add lylll9436/paper-polish-workflow-skill
paper-polish-workflow 168 ppw:de-ai 87 ppw:reviewer-simulation 84 ppw:translation 78 ppw:logic 78 ppw:abstract 76 ppw:polish 75 ppw:cover-letter 74 ppw:repo-to-paper 73 ppw:visualization 73

Browse all from lylll9436/paper-polish-workflow-skill

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 385
License LICENSE
Default branch main
Open issues 6
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 4,338 B
  • docs SUMMARY.md 208 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 79 installs

SKILL.md

Purpose

This Skill searches Google Scholar using Chrome DevTools MCP tools, presents search results to the user for selection, and retrieves BibTeX entries for selected papers. It automates the manual process of searching Google Scholar, clicking "Cite", and copying BibTeX. This Skill does NOT use Semantic Scholar MCP — it operates entirely through browser automation.

Trigger

Activates when the user asks to:

  • Search Google Scholar for a paper
  • Get BibTeX from Google Scholar
  • /get-paper <search query>

Workflow

Step 1: Navigate to Google Scholar

  • Call mcpchrome-devtoolslist_pages to check browser state.
  • If no page is open on scholar.google.com, call mcpchrome-devtoolsnavigate_page to https://scholar.google.com.
  • If already on Google Scholar, reuse the current page.

Step 2: Search

  • Take a snapshot to find the search box element.
  • Fill the search box with the user's query using mcpchrome-devtoolsfill.
  • Click the Search button using mcpchrome-devtoolsclick.
  • Wait for results with mcpchrome-devtoolswait_for (text: ["Cited by"]).

Step 3: Present Results

  • Take a snapshot of search results.
  • Extract the top 5-8 results: title, authors, venue, year, citation count.
  • Present them as a numbered list to the user.
  • Ask the user which paper(s) to retrieve BibTeX for (support multiple selections).
  • If the user's query is an exact title and the first result is a clear match, skip asking and auto-select it.

Step 4: Get BibTeX (for each selected paper)

For each selected paper:

  1. Click Cite: Click the Cite button (haspopup="menu") for the selected result.
  2. Wait for dialog: Wait for ["BibTeX"] text to appear.
  3. Click BibTeX link: Click the BibTeX link inside the Cite dialog.
  4. Read BibTeX: Wait for ["@"] to appear on the new page. Take a snapshot and extract the full BibTeX entry text.
  5. Navigate back: Go back to the search results page (mcpchrome-devtoolsnavigate_page type=back).
  6. Close dialog if open: If the Cite dialog is still showing, click Cancel.

Step 5: Output

  • Display all collected BibTeX entries to the user.
  • Ask the user if they want to append these entries to a specific .bib file.

- If yes, read the target bib file, check for duplicate keys, and append new entries. - Default target: manuscript/references/references.bib (if it exists in the current project).

Output Contract

Output Format Condition
bibtex_entry BibTeX text Always produced
Paper metadata Numbered list with title, authors, venue, year, citations Always presented before selection

Edge Cases

Situation Handling
Google Scholar CAPTCHA or rate-limit Inform the user and stop
No results found Inform the user, suggest alternative keywords
BibTeX page fails to load Retry once, then inform the user
Multiple papers selected Loop through Step 4 for each selection
Cite dialog not closing Navigate back to force close

Notes

  • BibTeX keys from Google Scholar are auto-generated (e.g., wang2024assessing). Do not modify them unless the user asks.
  • This skill uses Chrome DevTools MCP tools only. It does NOT use Semantic Scholar MCP.
  • Multiple papers can be fetched in one session by repeating Step 4.

Prerequisites

This Skill requires Chrome DevTools MCP server to be configured in Claude Code. To enable it:

  1. Open Claude Code settings.
  2. Navigate to MCP Servers.
  3. Add the Chrome DevTools MCP server.
  4. Ensure a Chrome browser is running with remote debugging enabled.

Skill: get-paper