plugin-recommender

Search internal and external plugin ecosystems to recommend validated plugins for task descriptions.

7|Updated May 26, 2026
One-click install
npx skills add https://github.com/chrono-meta/forge-harness --skill plugin-recommender-chrono-meta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-recommender
Source: https://github.com/chrono-meta/forge-harness/tree/main/plugins/fh-meta/skills/plugin-recommender
Command: npx skills add https://github.com/chrono-meta/forge-harness --skill plugin-recommender-chrono-meta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the guesswork and wasted time of searching for the right plugin across multiple ecosystems, avoids duplicate or conflicting installations, and ensures you get high-quality, validated tools instead of unvetted, untested options.

Core Features & Use Cases

  • Multi-ecosystem search: Scans internal organizational repositories, Claude Code marketplace, Codex marketplace, and public open-source ecosystems to find plugins matching your task.
  • Quality-tiered ranking: Ranks results by validation level (from platform built-ins to community-reviewed plugins) so you get the most reliable options first.
  • Duplicate and conflict detection: Checks if you already have a similar plugin installed, warns about name conflicts, and guides resolution.
  • Use Case: If you need to automate Jira ticket updates, this Skill will search all relevant ecosystems, show you the top 2-3 validated options, check if you already have a Jira tool installed, and walk you through setup if you choose a new one.

Quick Start

Ask the plugin-recommender to find a plugin for automating Jira ticket creation and status updates.

Frequently Asked Questions about plugin-recommender

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

FAQPage Schema
How do I find the best plugins for automating development workflows in Claude Code?

To find plugins for Claude Code, provide a task description to search internal repositories and external marketplaces. The system applies quality-tiered ranking to recommend validated plugins, ensuring you install reliable tools instead of unvetted options.

What is the best way to avoid duplicate plugin installations across multiple marketplaces?

Avoiding duplicate plugin installations requires scanning your existing environment before setup. The system detects conflicting plugins already installed, warns about name conflicts, and guides resolution so you maintain a clean toolset across Claude Code and Codex ecosystems.

Does plugin discovery work with internal organizational plugin inventories?

Yes, plugin discovery works with internal organizational plugin inventories. It searches your internal repositories alongside public open-source ecosystems, applying the same quality-tiered ranking and validation to internal tools as it does to marketplace options.

Can I search for plugins across both Claude Code and Codex marketplaces at the same time?

You can search across both Claude Code and Codex marketplaces simultaneously. The tool scans multiple ecosystems in a single query, returning a unified list of validated plugins ranked by quality tier to streamline cross-platform tool discovery.

How to resolve conflicts when installing a new plugin that overlaps with an existing tool?

Resolving plugin conflicts involves checking your installed tools against new search results. The system warns about overlapping names or duplicate functionalities, then guides you through selecting the highest quality option and uninstalling redundant packages.

When should I not use automated plugin recommendation for tool discovery?

You should not use automated plugin recommendation if you require an unindexed, highly niche tool or a custom-built internal package not yet registered in any marketplace. Discovery relies on searching mapped internal inventories and public open-source ecosystems.