Registry Browser Skill for Claude

> Search watched registries for community legal skills, showing matches with descriptions and offering to show the full SKILL.md before install. Use when the user says "browse", "search skills", "find a skill for", "what's out there for", or wants to add a new registry to the watchlist.

622 tokens

context cost

SKILL.md, read when the skill is used

files

plus reference files

copies elsewhere

how many repositories repackaged it

8 996

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/anthropics/claude-for-legal --skill registry-browser

What comes with it

474 bytes besides the instruction

references/registries.yaml

The instruction itself

11 sections, as written by the author

/registry-browser

Load ~/.claude/plugins/config/claude-for-legal/legal-builder-hub/CLAUDE.md → watched registries.
Use the workflow below.
Search each registry. Show matches with descriptions.
Offer to show full SKILL.md for any match.

Purpose

Find skills across the watched registries. Search, preview, decide.

Load context

~/.claude/plugins/config/claude-for-legal/legal-builder-hub/CLAUDE.md → watched registries list.

Workflow

Step 1: Fetch registry indexes

For each watched registry:

GitHub repos: fetch skills/ directory listing and each SKILL.md frontmatter (name + description).
Marketplace-style registries: fetch the index.

Cache the index locally (references/registry-cache.json) so browsing is fast. Refresh cache if >7 days old or on request.

Step 2: Search

Match query against skill names and descriptions. Simple keyword match is fine — these are small enough that fuzzy search is overkill.

Also: browse by category if the registry organizes skills that way.

Step 3: Present matches

## Search: "[query]"

**Found [N] skills across [M] registries:**

### [skill-name]
**From:** [registry name]
**Description:** [from frontmatter]
[View full SKILL.md] [Install]

### [skill-name]
[...]

Step 4: Preview

On "view full SKILL.md": fetch and show the whole file. User reads it before deciding to install. No surprises.

Step 5: Add a registry

If the user has a URL to a registry not in the watchlist:

Fetch it, validate it's a skills repo (has skills/ or .claude-plugin/)
Show what's in it
Add to ~/.claude/plugins/config/claude-for-legal/legal-builder-hub/CLAUDE.md → watched registries on confirmation

Default registries

lpm-skills — 14 legal project management skills. Practice-agnostic. Good starting point.
Space for others to be added as the ecosystem grows.

What this skill does not do

Install anything. It browses. skill-installer installs.
Rate or review skills. It shows you the SKILL.md; you judge.
Search the whole internet. Only watched registries.

Other skills for the same job

different authors, same section of the catalogue

Notebooklm

by ZhanlinCui

×8

Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth. Drastically reduced hallucinations through document-only responses.

Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.

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.

Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.

Use when the user explicitly asks for a desktop or system screenshot (full screen, specific app or window, or a pixel region), or when tool-specific capture capabilities are unavailable and an OS-level capture is needed.

A fast Rust-based headless browser automation CLI with Node.js fallback that enables AI agents to navigate, click, type, and snapshot pages via structured commands.

| 所有联网操作必须通过此 skill 处理，包括：搜索、网页抓取、登录后操作、动态页面交互等。触发场景：用户要求搜索信息、查看网页内容、访问需要登录的网站、操作网页界面、抓取社交媒体内容（小红书、微博、推特等）、读取动态渲染页面、以及任何需要真实浏览器环境的网络任务。

2.7k tokens scripts zh

Anchor Browser Automation

by christophacham

×2

Automate Anchor Browser tasks via Rube MCP (Composio). Always search tools first for current schemas.

756 tokens needs MCP

How to use it

Copy the folder

Take anthropics/registry-browser from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.