Claude Automation Recommender

Analyze codebase patterns to recommend tailored Claude Code automations across all extensibility options.

This skill is read-only. It analyzes the codebase and outputs recommendations. It does NOT create or modify any files. Users implement the recommendations themselves or ask Claude separately to help build them.

Output Guidelines

• •Recommend 1-2 of each type: Don't overwhelm - surface the top 1-2 most valuable automations per category
• •If user asks for a specific type: Focus only on that type and provide more options (3-5 recommendations)
• •Tell users they can ask for more: End by noting they can request more recommendations for any specific category

Automation Types Overview

Workflow

Phase 1: Codebase Analysis

Gather project context:

# Detect project type and tools
ls -la package.json pyproject.toml Cargo.toml go.mod pom.xml 2>/dev/null
cat package.json 2>/dev/null | head -50

# Check dependencies for MCP server recommendations
cat package.json 2>/dev/null | grep -E '"(react|vue|angular|next|express|fastapi|django|prisma|supabase|stripe)"'

# Check for existing Claude Code config
ls -la .claude/ CLAUDE.md 2>/dev/null

# Analyze project structure
ls -la src/ app/ lib/ tests/ components/ pages/ api/ 2>/dev/null

Key Indicators to Capture:

Phase 2: Generate Recommendations

Based on analysis, generate recommendations across all categories:

A. MCP Server Recommendations

See references/mcp-servers.md for detailed patterns.

B. Skills Recommendations

See references/skills-reference.md for patterns.

C. Hooks Recommendations

See references/hooks-patterns.md for configurations.

D. Subagent Recommendations

See references/subagent-templates.md for templates.

E. Slash Command Recommendations

See references/slash-command-examples.md for templates.

F. Plugin Recommendations

See references/plugins-reference.md for available plugins.

Phase 3: Output Recommendations Report

Format recommendations clearly. Only include 1-2 recommendations per category - the most valuable ones for this specific codebase. Skip categories that aren't relevant.

## Claude Code Automation Recommendations

I've analyzed your codebase and identified the top automations for each category. Here are my top 1-2 recommendations per type:

### Codebase Profile
- **Type**: [detected language/runtime]
- **Framework**: [detected framework]
- **Key Libraries**: [relevant libraries detected]

---

### 🔌 MCP Servers

#### context7
**Why**: [specific reason based on detected libraries]
**Install**: `claude mcp add context7`

---

### 🎯 Skills

#### [skill name]
**Why**: [specific reason]
**How**: [invocation method]

---

### ⚡ Hooks

#### [hook name]
**Why**: [specific reason based on detected config]
**Where**: `.claude/settings.json`

---

### 🤖 Subagents

#### [agent name]
**Why**: [specific reason based on codebase patterns]
**Where**: `.claude/agents/[name].md`

---

### 📝 Slash Commands

#### /[command]
**Why**: [specific reason]
**Where**: `.claude/commands/[name].md`

---

**Want more?** Ask for additional recommendations for any specific category (e.g., "show me more MCP server options" or "what other hooks would help?").

**Want help implementing any of these?** Just ask and I can help you set up any of the recommendations above.

Decision Framework

When to Recommend MCP Servers

• •External service integration needed (databases, APIs)
• •Documentation lookup for libraries/SDKs
• •Browser automation or testing
• •Team tool integration (GitHub, Linear, Slack)
• •Cloud infrastructure management

When to Recommend Skills

• •Complex multi-step workflows
• •Document generation needs
• •Specialized domain knowledge needed
• •Repeatable processes with templates

When to Recommend Hooks

• •Repetitive post-edit actions (formatting, linting)
• •Protection rules (block sensitive file edits)
• •Validation checks (tests, type checks)

When to Recommend Subagents

• •Specialized expertise needed (security, performance)
• •Parallel review workflows
• •Background quality checks

When to Recommend Slash Commands

• •Frequently repeated prompts
• •Commands with arguments
• •Quick project-specific workflows

When to Recommend Plugins

• •Need multiple related skills
• •Want pre-packaged automation bundles
• •Team-wide standardization

Configuration Tips

MCP Server Setup

Team sharing: Check .mcp.json into repo so entire team gets same MCP servers

Debugging: Use --mcp-debug flag to identify configuration issues

Prerequisites to recommend:

• •GitHub CLI (gh) - enables native GitHub operations
• •Puppeteer/Playwright CLI - for browser MCP servers

Headless Mode (for CI/Automation)

Recommend headless Claude for automated pipelines:

# Pre-commit hook example
claude -p "fix lint errors in src/" --allowedTools Edit,Write

# CI pipeline with structured output
claude -p "<prompt>" --output-format stream-json | your_command

Permissions for Hooks

Configure allowed tools in .claude/settings.json:

{
  "permissions": {
    "allow": ["Edit", "Write", "Bash(npm test:*)", "Bash(git commit:*)"]
  }
}