Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Development

agent-skill-discovery

This skill should be used when the user wants to see all installed plugins, agents, skills, and MCP servers, and also inspect the current repository for local agents, skills, and MCP configuration. Scans the environment and presents a structured catalog of available resources. Works across all AI CLI platforms (Claude Code, GitHub Copilot, Gemini CLI, OpenCode, OpenAI Codex).

ericgandrade · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add ericgandrade/claude-superskills --skill agent-skill-discovery

About this skill


name: agent-skill-discovery description: This skill should be used when the user wants to see all installed plugins, agents, skills, and MCP servers, and also inspect the current repository for local agents, skills, and MCP configuration. Scans the environment and presents a structured catalog of available resources. Works across all AI CLI platforms (Claude Code, GitHub Copilot, Gemini CLI, OpenCode, OpenAI Codex). license: MIT

agent-skill-discovery

Purpose

Automated inventory of AI CLI resources across two scopes: resources installed on the system and resources present in the current repository. This skill provides a comprehensive, platform-agnostic catalog of plugins, agents, skills, and MCP servers available in the current environment.

The skill operates in discovery-only mode—it scans, lists, and presents resources without performing analysis, recommendations, or orchestration. It serves as the foundation layer for resource awareness across all supported AI CLI platforms.

When to Use

Invoke this skill when:

  • User wants to know what resources are installed
  • Before planning complex tasks (foundation for orchestration)
  • Debugging missing resources or capabilities
  • Auditing available tools and integrations
  • Discovering newly installed plugins or MCP servers
  • Verifying skill installation after setup
  • Understanding platform capabilities
  • Checking whether the current repository contains local agents, skills, or MCP configs

Progress Tracking

Display a progress gauge before each step to keep the user informed:

[████░░░░░░░░░░░░░░░░] 15% — Step 1/6: Scanning Plugins
[████████░░░░░░░░░░░░] 30% — Step 2/6: Scanning Skills
[████████████░░░░░░░░] 45% — Step 3/6: Scanning MCP Servers
[████████████████░░░░] 60% — Step 4/6: Scanning Repository
[██████████████████░░] 75% — Step 5/6: Applying Filters
[████████████████████] 100% — Step 6/6: Generating Catalog

Parallel Scanning Strategy

After platform detection (Step 0), launch Steps 1–4 as four simultaneous agents in a single block:

AgentRole
PluginScannerGlob for plugin.json files, extract name/version/agents metadata
SkillScannerGlob for SKILL.md files, parse YAML frontmatter, extract name/description/triggers
McpScannerRead .mcp.json, run ToolSearch per server, build tool inventory
RepoScannerScan current working directory for local agents, skills, and MCP configs

Each agent prompt header: # {AgentName} — Resource Discovery Agent

Wait for all four to complete, then apply filters (Step 5) and generate catalog (Step 6).

Workflow

Step 0: Platform Detection

Objective: Identify which AI CLI platform is executing the skill.

Detection Strategy:

Check for platform-specific base directories in order:

# Platform detection by directory existence
if [ -d "$HOME/.claude/skills" ] && [ -f "$HOME/.claude/skills/agent-skill-discovery/SKILL.md" ]; then
    PLATFORM="claude"
    BASE_DIR="$HOME/.claude"
elif [ -d "$HOME/.copilot/skills" ] && [ -f "$HOME/.copilot/skills/agent-skill-discovery/SKILL.md" ]; then
    PLATFORM="copilot"
    BASE_DIR="$HOME/.copilot"
elif [ -d "$HOME/.gemini/skills" ] && [ -f "$HOME/.gemini/skills/agent-skill-discovery/SKILL.md" ]; then
    PLATFORM="gemini"
    BASE_DIR="$HOME/.gemini"
elif [ -d "$HOME/.opencode/skills" ] && [ -f "$HOME/.opencode/skills/agent-skill-discovery/SKILL.md" ]; then
    PLATFORM="opencode"
    BASE_DIR="$HOME/.opencode"
elif [ -d "$HOME/.codex/skills" ] && [ -f "$HOME/.codex/skills/agent-skill-discovery/SKILL.md" ]; then
    PLATFORM="codex"
    BASE_DIR="$HOME/.codex"
else
    PLATFORM="unknown"
    BASE_DIR="$HOME"
fi

Platform Configuration:

Platform configuration is uniform across all 5 platforms — pluginsDir, skillsDir, and mcpConfig paths follow the same structure relative to BASE_DIR. Use BASE_DIR resolved from the detection above for all subsequent path construction.

Step 1: Scan for Plugins

Objective: Discover all installed plugins and their agents.

Actions:

Use Glob to find plugin manifests:

# Search for plugin.json files
Glob pattern: "{config.pluginsDir}/*/plugin.json"

For each plugin found:

  1. Read plugin manifest:

    Read: {plugin_path}/plugin.json
    
  2. Extract metadata:

    • Plugin name
    • Plugin version
    • Plugin description
    • Agents array
  3. Parse agent details: For each agent in the agents array:

    • Agent name
    • Agent description
    • Available tools (Glob, Grep, Read, Write, Bash, etc.)
    • Agent color/category (if specified)

Data Structure:

{
  "name": "feature-dev",
  "version": "1.0.0",
  "description": "Feature development workflow automation",
  "agents": [
    {
      "name": "code-explorer",
      "description": "Deeply analyzes existing codebase features",
      "tools": ["Glob", "Grep", "Read", "Bash"]
    },
    {
      "name": "code-architect",
      "description": "Designs feature architectures",
      "tools": ["Glob", "Grep", "Read", "Write"]
    }
  ]
}

Graceful Handling:

  • If plugins directory doesn't exist: Return empty plugin array
  • If plugin.json is malformed: Log warning, skip plugin, continue
  • If agents array is missing: Include plugin with 0 agents

Step 2: Scan for Skills

Objective: Discover all installed skills and their metadata.

Actions:

Use Glob to find skill definitions:

# Search for SKILL.md files
Glob pattern: "{config.skillsDir}/*/SKILL.md"

For each skill found:

  1. Read skill file:

    Read: {skill_path}/SKILL.md
    
  2. Parse YAML frontmatter: Extract the YAML block between --- delimiters:

    ---
    name: skill-creator
    description: "This skill should be used when..."
    triggers:
      - "create a skill"
      - "new skill"
    version: 1.0.0
    category: development
    ---
    
  3. Extract metadata:

    • Skill name
    • Descripti
Read the complete source ↗