Back to the catalog

why-is-my-claude-dumb

Analyze your environment and recommend official marketplace plugins to make Claude Code smarter

Open source Open in the app JSON README (API)

About

Analyze your environment and recommend official marketplace plugins to make Claude Code smarter

Details

Kind
Plugins
Topic
No topic detected
Publisher
jeongph
Origin
marketplace
Category
ferramentas
Stars
1
Last push
2026-08-01T14:22:55Z
Repository state
ativo
License
MIT
Added
2026-08-30 01:48:58
Updated
2026-08-30 01:48:58
Origin id
jeongph/why-is-my-claude-dumb/why-is-my-claude-dumb

README

# why-is-my-claude-dumb

[![version](https://img.shields.io/github/v/release/jeongph/why-is-my-claude-dumb?label=version&color=blue)](https://github.com/jeongph/why-is-my-claude-dumb/releases)
[![license](https://img.shields.io/github/license/jeongph/why-is-my-claude-dumb?color=lightgrey)](LICENSE)

> Why is my Claude so dumb? Let's find out.

Your Claude Code environment might be missing plugins that could make it significantly smarter. This plugin analyzes your local environment, codebase, and current setup, then recommends official marketplace plugins tailored to your workflow.

## Installation

**1. Add the [jeongph/claude-plugins](https://github.com/jeongph/claude-plugins) marketplace** (one-time)

```
/plugin marketplace add jeongph/claude-plugins
```

**2. Install the plugin**

```
/plugin install why-is-my-claude-dumb@jeongph-claude-plugins
```

**3. Run it**

```
/why-is-my-claude-dumb:why-dumb
```

## How it works

### Full analysis (`/why-dumb`)

Walks you through a guided analysis:

1. Asks about your workflow and pain points
2. Scans your environment (OS, languages, installed plugins, Claude settings, MCP servers)
3. Reads the official marketplace catalog (80+ plugins)
4. Recommends what's missing with clear explanations
5. Installs selected plugins on the spot

### Auto-trigger (dumb-doctor)

When you express frustration with Claude's performance, the `dumb-doctor` agent automatically offers to run an environment check and suggest 1-2 high-impact plugins.

## What gets analyzed

| Category | Details |
|----------|---------|
| System | OS, platform, architecture |
| Languages | Installed runtimes (Node, Python, Java, Go, Rust, etc.) |
| Plugins | Currently installed plugins vs. available catalog |
| Configuration | Claude Code settings, hooks, permissions |
| Integrations | Connected MCP servers |
| Project context | Project type, CLAUDE.md presence (when run inside a repo) |

## Examples

```
/why-is-my-claude-dumb:why-dumb

๐Ÿ” Environment Analysis
โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”
OS: Linux x86_64 | Languages: Java 17, Node 20, Python 3.11
Project: Spring Boot | Installed plugins: 3

๐Ÿ’ก These plugins would make a difference
โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”
1. jdtls-lsp (Java Language Server)
   Catches type errors and missing imports in real-time as you edit.
   Right now you only see errors after building.

2. claude-md-management (Project Context Manager)
   Creates and maintains a CLAUDE.md project description.
   Without it, Claude has to re-learn your project every session.

๐Ÿ‘‰ Tell me which ones to install! (e.g. "install 1 and 2")
```

## License

[MIT](LICENSE)

More