plugin-status

Inspect Claude plugin and environment configuration and output a status table.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/taptap/agents-plugins --skill plugin-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-status
Source: https://github.com/taptap/agents-plugins/tree/main/plugins/sync/skills/plugin-status
Command: npx skills add https://github.com/taptap/agents-plugins --skill plugin-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates checking whether Claude plugins and related developer tooling are correctly installed and configured, reducing manual verification and troubleshooting time.

Core Features & Use Cases

  • Comprehensive Environment Checks: Validates enabledPlugins in ~/.claude/settings.json, known marketplaces, and plugin marketplace versions.
  • Hook and Symlink Diagnostics: Checks hooks scripts for symlink integrity, detects ordinary files versus broken links, and reports counts of valid/invalid symlinks.
  • MCP and Repo Validation: Verifies MCP servers in ~/.claude.json, Codex config presence, and repository-level files like .claude/settings.json, CLAUDE.md, and AGENTS.md.
  • Use Case: Quickly diagnose why a plugin is not available in Claude Code by running a full local and repo-level configuration audit and receiving a summarized table with remediation tips.

Quick Start

Invoke the plugin-status skill to run a full environment and repository plugin configuration check and return a summarized status table with suggested fixes.

Frequently Asked Questions about plugin-status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check Claude plugin configuration and environment setup status?

To check Claude plugin configuration, invoke the plugin-status skill to perform local shell inspections and JSON parsing, validating enabledPlugins, known marketplaces, hook scripts, and repository settings. It returns a summarized status table with remediation suggestions.

What is the best way to diagnose why a plugin is not available in Claude Code?

The best way to diagnose an unavailable Claude Code plugin is running a full local and repo-level configuration audit. This skill inspects ~/.claude/settings.json, hook symlinks, and MCP servers, outputting a status table with specific fixes.

Why does my Claude hooks symlink show as invalid or broken?

Invalid Claude hooks symlinks occur when ordinary files replace expected links or targets are deleted. This skill checks hooks scripts for symlink integrity, detecting ordinary files versus broken links, and reports counts of valid and invalid symlinks.

Does this tool verify MCP servers and repository-level .claude settings?

Yes, this tool verifies MCP servers and repository-level settings. It checks MCP configuration in ~/.claude.json, validates Codex config presence, and inspects repository files like .claude/settings.json, CLAUDE.md, and AGENTS.md.

When do I need to audit known marketplaces and enabled plugins for Claude?

You need to audit known marketplaces and enabled plugins for Claude when experiencing setup failures or missing tooling. This skill validates marketplace versions and enabledPlugins entries in ~/.claude/settings.json to ensure correct local development environment configuration.