enhance-plugins

# enhance-plugins

Analyze plugin structures, MCP tools, and security patterns against best practices.

## Plugin Locations

| Platform | Location |
|----------|----------|
| Claude Code | `plugins/*/`, `.claude-plugin/plugin.json` |
| OpenCode | `.opencode/plugins/`, MCP in `opencode.json` |
| Codex | MCP in `~/.codex/config.toml` |

## Workflow

1. **Discover** - Find plugins in `plugins/` directory
2. **Load** - Read `plugin.json`, agents, commands, skills
3. **Analyze** - Run pattern checks by certainty level
4. **Report** - Generate markdown output
5. **Fix** - Apply auto-fixes if `--fix` (HIGH certainty only)

## Detection Patterns

### 1. Tool Schema Design (HIGH)

Based on function calling best practices:

**Required elements:**
```json
{
  "name": "verb_noun",
  "description": "What it does. When to use. What it returns.",
  "input_schema": {
    "type": "object",
    "properties": {
      "param": {
        "type": "string",
        "description": "Format and example"
      }
    },
    "required": ["param"],
    "additionalProperties": false
  }
}
```

**The "Intern Test"** - Can someone use this tool given only the description?

| Issue | Certainty | Auto-Fix |
|-------|-----------|----------|
| Missing `additionalProperties: false` | HIGH | Yes |
| Missing `required` array | HIGH | Yes |
| Missing tool description | HIGH | No |
| Missing param descriptions | MEDIUM | No |
| Vague names (`search`, `process`) | MEDIUM | No |

### 2. Description Quality (HIGH)

**Tool descriptions must include:**
- What the function does
- When to use it (trigger context)
- What it returns

```json
// Bad - vague
"description": "Search for things"

// Good - complete
"description": "Search product catalog by keyword. Use for inventory queries or price checks. Returns matching products with prices."
```

**Parameter descriptions must include:**
- Format expectations
- Example values
- Relationships to other params

```json
// Bad
"query": { "type": "string" }

// Good
"quer