suggest-plugins

Analyze projects and existing skills to suggest plugins for automation gaps.

1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/mattbobambrose/mattbobambrose-claude-skills --skill suggest-plugins
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: suggest-plugins
Source: https://github.com/mattbobambrose/mattbobambrose-claude-skills/tree/main/plugins/project-tools/skills/suggest-plugins
Command: npx skills add https://github.com/mattbobambrose/mattbobambrose-claude-skills --skill suggest-plugins

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Projects and marketplaces often accumulate repetitive manual work and missing automation but lack a concise way to discover non-duplicative plugins that would save time and reduce errors. This Skill streamlines the discovery of high-impact plugin ideas by analyzing the codebase, build manifests, existing skills, and git history to reveal repetitive tasks and tooling gaps.

Core Features & Use Cases

  • Inventory existing skills: Locate and read nearby SKILL.md files to avoid suggesting duplicate functionality.
  • Project analysis: Parse build manifests and scan source and config files to detect language, frameworks, and recurring patterns.
  • Git mining for patterns: Inspect recent commits to surface repetitive actions like frequent endpoint additions, version bumps, or scaffolding that merit automation.
  • Use Case: For a repository with Gradle scripts and repeated "bump version" commits, recommend a version-bump plugin and a changelog generator to automate release chores.

Quick Start

Ask the assistant to analyze the repository and existing skills and return a ranked list of five suggested slash-commands with invocation examples and rationale.

Frequently Asked Questions about suggest-plugins

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

FAQPage Schema
How do I discover automation gaps and missing tooling in my project repository?▼

Discover automation gaps by analyzing the codebase, build manifests, existing skills, and recent git history to identify repetitive tasks and suggest non-duplicative plugins that fill those uncovered tooling needs.

What is the best way to suggest plugins based on git commit patterns?▼

Suggesting plugins based on git commit patterns involves inspecting recent commits to surface repetitive actions like endpoint additions or version bumps, then recommending automation plugins to streamline those chores.

Can I analyze SKILL.md files to avoid recommending duplicate plugins?▼

Yes, you can analyze SKILL.md files to inventory existing skills and prevent recommending duplicate plugins, ensuring any new suggestions target only uncovered automation gaps within the local marketplace.

How do I find high-value plugin ideas for a local skill marketplace?▼

Find high-value plugin ideas by inspecting build manifests, scanning source and config files, and mining commit history to produce a ranked list of suggested slash-commands with invocation examples and rationale.

Does this project audit approach work without external dependencies?▼

Yes, the project audit approach works without external dependencies, relying solely on reading local files, parsing manifests, and optionally running git commands to extract commit patterns.

When should I not use automated plugin suggestions for a codebase?▼

Avoid automated plugin suggestions when the codebase lacks build manifests, SKILL.md files, or sufficient git history, as the analysis depends on these inputs to accurately detect repetitive manual work.