Configuration
Claude Automation Recommender
Analyze a codebase and recommend Claude Code automations: hooks, subagents, skills, custom slash commands, and MCP servers.
Last reviewed Mar 2, 2026
Install
Create this file in your project:
.claude/skills/claude-automation-recommender/SKILL.md---
name: claude-automation-recommender
description: Use this skill when analyzing a project for automation opportunities, setting up Claude Code integrations, or optimizing an AI-assisted workflow.
---
# Claude Automation Recommender
## When to Use
- Setting up Claude Code for a new project
- Optimizing an existing Claude Code workflow
- Looking for ways to automate repetitive tasks
- Evaluating which MCP servers would be useful
## Process
1. **Audit the codebase** -- Examine project structure, tech stack, build pipeline, CI/CD, and common development patterns.
2. **Identify automation opportunities** in these categories:
- **Hooks** -- Pre/post-commit hooks, file save hooks, or session hooks that automate repetitive checks (linting, formatting, test runs).
- **Skills** -- Reusable instruction sets for common workflows in this project (deployment procedures, migration steps, review checklists).
- **Subagents** -- Specialized agents for specific tasks (test writing, documentation, code review).
- **MCP servers** -- External tool integrations that would benefit the workflow (database access, API testing, design tool connections).
3. **Evaluate each recommendation** -- For each automation, explain:
- What it does and when it triggers
- The specific benefit (time saved, errors prevented)
- Implementation complexity (one-line config vs. custom development)
4. **Prioritize** -- Rank recommendations by impact-to-effort ratio. Quick wins first.
## Rules
- Only recommend automations with clear, specific value. No "nice to have" suggestions.
- Explain the concrete benefit of each recommendation, not just what it does.
- Consider the project's actual workflow, not a theoretical ideal.
- Do not recommend MCP servers unless the project would genuinely benefit from external integrations.
- Prioritize by impact-to-effort ratio. A 5-minute hook setup that saves 30 seconds per commit beats a complex subagent setup.
- Check what automations already exist before recommending new ones.What this skill does
Claude Automation Recommender analyzes your project and development workflow to suggest concrete automations that save time and prevent errors. Instead of manually exploring the Claude Code documentation for what's possible, this skill scans your codebase and tells you exactly which automations would benefit your specific project.
The recommendations span four categories: hooks for automatic checks, skills for reusable workflows, subagents for specialized tasks, and MCP servers for external integrations. Each recommendation includes not just what to set up, but why it matters for your particular project and how much effort it takes.
The prioritization by impact-to-effort ratio ensures you get the biggest wins first. A simple pre-commit hook that runs the linter might prevent more errors than a sophisticated multi-agent setup, and it takes one minute to configure.
Example workflow
You ask the agent to recommend automations for your Next.js e-commerce project. It analyzes the codebase and recommends:
- Pre-commit hook (5 min setup): Run
tsc --noEmitbefore every commit -- prevents 60% of CI failures. - Deployment skill (10 min setup): A checklist for production deployments covering database migrations, cache invalidation, and feature flags.
- Stripe MCP server (15 min setup): Connect to Stripe for checking webhook configurations and testing payment flows directly from the editor.
- Review subagent (30 min setup): A specialized code review agent pre-loaded with your project's security requirements and performance benchmarks.
Tips
- Run this skill when you first set up Claude Code on a project to get a quick automation roadmap
- Revisit every few months as your project evolves -- new patterns may suggest new automations
- Start with hooks and skills (low effort, high impact) before investing in subagents and MCP servers
- The recommendations are project-specific, so they'll differ for a mobile app vs. a backend service
Best with tools
Related MCP servers
- No linked MCP servers yet.