Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计通过

plugin-registry插件注册表

Agent Skill

plugin-registry 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

939

周安装

38

GitHub Stars

28

下载量

295
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:plugin-registry(插件注册表)
来源仓库:https://github.com/laurigates/claude-plugins
仓库路径:skills/plugin-registry
安装命令:
npx skills add https://github.com/laurigates/claude-plugins --skill plugin-registry
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/laurigates/claude-plugins --skill plugin-registry

简介

用于查找、检索和筛选相关信息,支持关键词匹配与任务场景适配。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。
  • 可通过 npx skills add 命令从指定仓库安装并使用。
  • 安装前建议确认权限范围和维护状态,避免触发联网或文件读写操作。
  • 注意:实际功能需结合原始 README 进一步核验,当前描述基于通用模板。

SKILL.md

Claude Code Plugin Registry

Expert knowledge for understanding and troubleshooting the Claude Code plugin registry.

When to Use This Skill

Use this skill when...Use something else when...
Plugin shows "installed" but isn't workingSetting up new plugins (use /configure:claude-plugins)
Need to understand plugin scopesConfiguring plugin permissions (use settings-configuration skill)
Fixing orphaned registry entriesCreating workflows with plugins (use github-actions-plugin)
Debugging installation failures

Registry Location

The plugin registry is stored at:

~/.claude/plugins/installed_plugins.json

This file tracks all installed plugins across all projects.

Registry Structure (v2)

{
  "version": 2,
  "plugins": {
    "plugin-name@marketplace-name": [
      {
        "scope": "project",
        "projectPath": "/path/to/project",
        "installPath": "~/.claude/plugins/cache/marketplace/plugin-name/1.0.0",
        "version": "1.0.0",
        "installedAt": "2024-01-15T10:30:00Z",
        "lastUpdated": "2024-01-15T10:30:00Z",
        "gitCommitSha": "abc123"
      }
    ]
  }
}

Each plugin key maps to an array of installations (supporting multiple scopes).

Field Reference

FieldRequiredDescription
scopeYes"project" or "user" (global)
projectPathproject onlyDirectory where plugin is active
installPathYesCache path for installed plugin files
versionYesInstalled version
installedAtYesISO timestamp of installation
lastUpdatedYesISO timestamp of last update
gitCommitShaYesGit commit of installed version

Installation Scopes

User Scope (global, default)

/plugin install my-plugin@marketplace
  • "scope": "user" in registry entry
  • No projectPath field
  • Available in all projects

Project Scope

/plugin install my-plugin@marketplace --scope project
  • "scope": "project" in registry entry
  • Has projectPath set to installation directory
  • Should only be active in that project
  • Bug #14202: Still shows as "installed" in other projects

Known Issue: #14202

Problem: Project-scoped plugins incorrectly appear as globally installed.

Root Cause: Inconsistent projectPath checking:

OperationChecks projectPath?Result
Marketplaces "(installed)"NoShows installed everywhere
/plugin installNoRefuses to install
Installed tab listingYesCorrectly filtered

Symptoms:

  1. Plugin shows "(installed)" checkmark in Marketplaces view
  2. /plugin install says "already installed"
  3. Plugin doesn't appear in Installed tab for current project
  4. Plugin doesn't actually work in current project

Workaround: Manually edit the registry to add an entry for the current project.

Manual Registry Operations

View Registry

jq . ~/.claude/plugins/installed_plugins.json

List All Plugins

jq -r '.plugins | keys[]' ~/.claude/plugins/installed_plugins.json

Find Project-Scoped Plugins

jq '.plugins | to_entries[] | .value[] | select(.scope == "project") | {projectPath, version}' ~/.claude/plugins/installed_plugins.json

Find Orphaned Entries

Use the Read tool to read ~/.claude/plugins/installed_plugins.json, then check each projectPath with test -d.

Backup Registry

cp ~/.claude/plugins/installed_plugins.json ~/.claude/plugins/installed_plugins.json.backup

Fixing Registry Issues

Remove Orphaned Entry

  1. Read ~/.claude/plugins/installed_plugins.json with the Read tool
  2. Back up with cp ~/.claude/plugins/installed_plugins.json ~/.claude/plugins/installed_plugins.json.backup
  3. Remove the orphaned entry from the plugins object
  4. Write the updated JSON with the Write tool

Add Entry for Current Project

  1. Read the registry with Read tool
  2. Add a new entry to the plugin's array with scope: "project" and current projectPath
  3. Write the updated JSON with Write tool

Convert Project-Scoped to User (Global)

  1. Read the registry with Read tool
  2. Change "scope": "project" to "scope": "user" and remove projectPath
  3. Write the updated JSON with Write tool

Project Settings Integration

Project-scoped plugins also need entries in .claude/settings.json:

{
  "enabledPlugins": [
    "plugin-name@marketplace"
  ]
}

Without this, even a correctly registered project-scoped plugin won't load.

Troubleshooting Checklist

  1. Plugin shows installed but doesn't work

- Check if projectPath matches current directory - Check .claude/settings.json for enabledPlugins - Run /health:plugins for diagnosis

  1. Can't install plugin (already installed)

- Check registry for existing entry - Check if entry has different projectPath - Use /health:plugins --fix or manual edit

  1. Plugin works in one project but not another

- Likely a project-scoped plugin - Need separate registry entry per project - Or convert to global scope

  1. Registry file is corrupted

- Restore from backup if available - Or delete and reinstall plugins - Location: ~/.claude/plugins/installed_plugins.json

Agentic Optimizations

ContextCommand
View registryjq -c. ~/.claude/plugins/installed_plugins.json
List plugins`jq -r '.plugins \keys[]' ~/.claude/plugins/installed_plugins.json`
Check specificjq '.plugins."name@market"' ~/.claude/plugins/installed_plugins.json
Project plugins`jq '.plugins \to_entries[] \.value[] \select(.scope=="project")' ~/.claude/plugins/installed_plugins.json`

Quick Reference

Registry Path

~/.claude/plugins/installed_plugins.json

Key Format

{plugin-name}@{marketplace-name}

Scope Indicator

  • "scope": "project" + projectPath → Project-scoped
  • "scope": "user" → Global (user-wide)

After Editing

Always restart Claude Code for registry changes to take effect.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

35.74%
按下载量换算105

Claude

29.97%
按下载量换算88

Cursor

16.78%
按下载量换算50

Gemini CLI

9.43%
按下载量换算28

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills