webui skill
Starts a Nuxt.js production server to provide a web interface for browsing and studying papers.
- GitHub stars
- 358
- Files
- 1
- Last commit
- Aug 14, 2026
- License
- MIT
- Allowed tools
- 1
What does the webui skill do?
webui starts a Nuxt.js production server to provide a web interface for browsing and studying papers.
Summary generated from the skill's SKILL.md.
About the webui skill
Browsing and studying academic papers through a visual interface is what this skill enables. It automates the deployment of a Nuxt.js production server, allowing researchers and developers to move from a text-based environment to a dedicated web viewer. An agent should load this skill when a user needs to interact with papers via a browser rather than through chat commands.
The process involves using Bash to manage dependencies via npm, building the production server, and verifying that port 5815 is available. It includes logic to detect version mismatches, performing clean installs if node_modules are corrupted, and ensuring the server is healthy by checking the /api/papers endpoint. Once the server is running in the background, it provides a local web interface for paper exploration.
What an agent can do with it
- 1Launch the paper viewerStart the Claude Paper web viewer to browse and study papers through a browser.
- 2Manage server dependenciesAutomatically install or repair node_modules if the web environment is missing or corrupted.
- 3Update the production buildRebuild the Nuxt.js server whenever the plugin version changes to ensure the interface is current.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the webui skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the webui skill in Plugin
/plugin marketplace add alaliqing/claude-paper /plugin install claude-paper@claude-paper
Install the webui skill in Claude Code
~/.claude/skills/webui/SKILL.md
$ npx degit alaliqing/claude-paper/plugin/skills/webui ~/.claude/skills/webuiInstall the webui skill in Claude Code (project)
.claude/skills/webui/SKILL.md
$ npx degit alaliqing/claude-paper/plugin/skills/webui .claude/skills/webuiInstall the webui skill in Codex
~/.agents/skills/webui/SKILL.md
$ npx degit alaliqing/claude-paper/plugin/skills/webui ~/.agents/skills/webuiInstall the webui skill in Gemini CLI
~/.gemini/skills/webui/SKILL.md
$ npx degit alaliqing/claude-paper/plugin/skills/webui ~/.gemini/skills/webuiInstall the webui skill in Claude.ai
npx degit alaliqing/claude-paper/plugin/skills/webui webui && zip -r webui.zip webui # claude.ai → Customize → Skills → + → Create skill → Upload a skill → webui.zip
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A skill needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablealaliqing/claude-paper/plugin/skills/webui is public and reachablegithub.com/alaliqing/claude-paper/tree/HEAD/plugin/skills/we ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-08-14github.com/alaliqing/claude-paper/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/alaliqing/claude-paper/blob/HEAD/plugin/skills/we ↗Pass
- Pre-approved tools are scopedBash lets the agent run any shell command without askinggithub.com/alaliqing/claude-paper/blob/HEAD/plugin/skills/we ↗Finding
- SKILL.md follows the Agent Skills formatthe description does not say when to use the skillgithub.com/alaliqing/claude-paper/blob/HEAD/plugin/skills/we ↗Finding
SKILL.md
View on GitHubStart Web UI
This skill starts the Claude Paper web viewer using the production Nuxt.js server.
Step 1: Check and Install Dependencies (First Run Only)
Check if web dependencies are installed (with corruption check):
cd "${CLAUDE_PLUGIN_ROOT}/src/web"
if [ ! -d "node_modules" ]; then
echo "First run - installing web dependencies..."
npm ci
echo "Web dependencies installed!"
elif [ ! -f "node_modules/.package-lock.json" ] || [ ! -d "node_modules/nuxt" ]; then
echo "ERROR: node_modules is corrupted, performing clean install..."
rm -rf node_modules
npm ci
echo "Web dependencies installed!"
else
echo "Dependencies already installed"
fi
Step 2: Build Production Server (auto-rebuilds on plugin update)
Build if needed or if plugin version changed:
cd ${CLAUDE_PLUGIN_ROOT}/src/web
PLUGIN_VERSION=$(node -e "console.log(require('${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json').version)")
BUILD_VERSION=""
if [ -f ".output/.build-version" ]; then
BUILD_VERSION=$(cat ".output/.build-version")
fi
if [ ! -f ".output/server/index.mjs" ] || [ "$PLUGIN_VERSION" != "$BUILD_VERSION" ]; then
echo "Building production server (v${PLUGIN_VERSION})..."
npm run build
echo "$PLUGIN_VERSION" > .output/.build-version
echo "Build complete!"
else
echo "Production build is up to date (v${BUILD_VERSION})"
fi
Step 3: Check Port Availability
Ensure port 5815 is available (with version check restart):
# Get version info for comparison
PLUGIN_VERSION=$(node -e "console.log(require('${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json').version)")
BUILD_VERSION=""
if [ -f ".output/.build-version" ]; then
BUILD_VERSION=$(cat ".output/.build-version")
fi
if lsof -i :5815 > /dev/null 2>&1; then
echo "INFO: Port 5815 is already in use"
PID_FILE="/tmp/claude-paper-webui.pid"
if [ -f "$PID_FILE" ] && kill -0 $(cat "$PID_FILE") 2>/dev/null; then
# Check version match - restart if plugin was updated
if [ "$PLUGIN_VERSION" = "$BUILD_VERSION" ]; then
echo "Claude Paper web UI is already running (version ${PLUGIN_VERSION})"
echo "Access it at: http://localhost:5815"
exit 0
else
echo "Version mismatch: running ${BUILD_VERSION}, need ${PLUGIN_VERSION}"
echo "Stopping old server..."
kill $(cat "$PID_FILE") 2>/dev/null
sleep 2
rm -f "$PID_FILE"
echo "Old server stopped, will restart with new version"
fi
else
echo "ERROR: Port 5815 is occupied by another process"
exit 1
fi
fi
Step 4: Start Production Server
Start the server in background:
HOST=127.0.0.1 PORT=5815 node .output/server/index.mjs &
SERVER_PID=$!
# Save PID for later cleanup
echo $SERVER_PID > /tmp/claude-paper-webui.pid
echo "Server PID: $SERVER_PID"
Step 5: Verify Server Health
Wait for server to be ready:
timeout=10
while [ $timeout -gt 0 ]; do
if curl -s http://localhost:5815/api/papers > /dev/null 2>&1; then
echo "Server is ready!"
break
fi
sleep 1
timeout=$((timeout - 1))
done
if [ $timeout -eq 0 ]; then
echo "ERROR: Server failed to start properly"
kill $SERVER_PID 2>/dev/null
rm -f /tmp/claude-paper-webui.pid
exit 1
fi
Step 6: Inform User
Tell the user the web viewer is available and provide cleanup instructions:
Claude Paper web UI is now running!
Access it at: http://localhost:5815
To stop the server, run:
kill $(cat /tmp/claude-paper-webui.pid)
Files in this skill
1webui skill questions
How do I install the webui skill in Claude Code?
Run npx degit alaliqing/claude-paper/plugin/skills/webui ~/.claude/skills/webui. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the webui skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
How can I stop the web UI server?
To stop the server, you should run the command to kill the process using the stored PID file.
What happens if the web dependencies are corrupted?
The skill performs a clean install by removing the node_modules directory and running npm ci.