agentleFS
jmolzjmolz/m0lz.01/.agents/skills/claude-automation-recommender/SKILL.md

Codex-automation-recommender

Skill0 starsChanged 6 months agoMITView on GitHub

Analyze a codebase and recommend Codex automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Codex setup, mentions improving Codex workflows, asks how to first set up Codex for a project, or wants to know what Codex features they should use.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Recommend 1-2 of each type: Don't overwhelm - surface the top 1-2 most valuable automations per category

    line 15
  2. Very specific:

    Create skills in .Codex/skills/<name>/SKILL.md.

    line 91
  3. Distinctive:

    Document generation (docx, xlsx, pptx, pdf — also in plugins)

    line 225
  4. Distinctive:

    Default (omit both) — Both can invoke

    line 235
  5. Very specific:

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

    line 258
  6. Very specific:

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

    line 260

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Codex Automation Recommender

Analyze codebase patterns to recommend tailored Codex 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 Codex 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)
  • Go beyond the reference lists: The reference files contain common patterns, but use web search to find recommendations specific to the codebase's tools, frameworks, and libraries
  • Tell users they can ask for more: End by noting they can request more recommendations for any specific category

Automation Types Overview

TypeBest For
HooksAutomatic actions on tool events (format on save, lint, block edits)
SubagentsSpecialized reviewers/analyzers that run in parallel
SkillsPackaged expertise, workflows, and repeatable tasks (invoked by Codex or user via /skill-name)
PluginsCollections of skills that can be installed
MCP ServersExternal tool integrations (databases, APIs, browsers, docs)

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 Codex config
ls -la .Codex/ AGENTS.md 2>/dev/null

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

Key Indicators to Capture:

CategoryWhat to Look ForInforms Recommendations For
Language/Frameworkpackage.json, pyproject.toml, import patternsHooks, MCP servers
Frontend stackReact, Vue, Angular, Next.jsPlaywright MCP, frontend skills
Backend stackExpress, FastAPI, DjangoAPI documentation tools
DatabasePrisma, Supabase, raw SQLDatabase MCP servers
External APIsStripe, OpenAI, AWS SDKscontext7 MCP for docs
TestingJest, pytest, Playwright configsTesting hooks, subagents
CI/CDGitHub Actions, CircleCIGitHub MCP server
Issue trackingLinear, Jira referencesIssue tracker MCP
Docs patternsOpenAPI, JSDoc, docstringsDocumentation skills

Phase 2: Generate Recommendations

Based on analysis, generate recommendations across all categories:

A. MCP Server Recommendations

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

Codebase SignalRecommended MCP Server
Uses popular libraries (React, Express, etc.)context7 - Live documentation lookup
Frontend with UI testing needsPlaywright - Browser automation/testing
Uses SupabaseSupabase MCP - Direct database operations
PostgreSQL/MySQL databaseDatabase MCP - Query and schema tools
GitHub repositoryGitHub MCP - Issues, PRs, actions
Uses Linear for issuesLinear MCP - Issue management
AWS infrastructureAWS MCP - Cloud resource management
Slack workspaceSlack MCP - Team notifications
Memory/context persistenceMemory MCP - Cross-session memory
Sentry error trackingSentry MCP - Error investigation
Docker containersDocker MCP - Container management

B. Skills Recommendations

See references/skills-reference.md for details.

Create skills in .Codex/skills/<name>/SKILL.md. Some are also available via plugins:

Codebase SignalSkillPlugin
Building pluginsskill-developmentplugin-dev
Git commitscommitcommit-commands
React/Vue/Angularfrontend-designfrontend-design
Automation ruleswriting-ruleshookify
Feature planningfeature-devfeature-dev

Custom skills to create (with templates, scripts, examples):

Codebase SignalSkill to CreateInvocation
API routesapi-doc (with OpenAPI template)Both
Database projectcreate-migration (with validation script)User-only
Test suitegen-test (with example tests)User-only
Component librarynew-component (with templates)User-only
PR workflowpr-check (with checklist)User-only
Releasesrelease-notes (with git context)User-only
Code styleproject-conventionsCodex-only
Onboardingsetup-dev (with prereq script)User-only

C. Hooks Recommendations

See references/hooks-patterns.md for configurations.

Codebase SignalRecommended Hook
Prettier configuredPostToolUse: auto-format on edit
ESLint/Ruff configuredPostToolUse: auto-lint on edit
TypeScript projectPostToolUse: type-check on edit
Tests directory existsPostToolUse: run related tests
.env files presentPreToolUse: block .env edits
Lock files presentPreToolUse: block lock file edits
Security-sensitive codePreToolUse: require confirmation

D. Subagent Recommendations

See references/subagent-templates.md for templates.

Codebase SignalRecommended Subagent
Large codebase (>500 files)code-reviewer - Parallel code review
Auth/payments codesecurity-reviewer - Security audits
API projectapi-documenter - OpenAPI generation
Performance criticalperformance-analyzer - Bottleneck detection
Frontend heavyui-reviewer - Accessibility review
Needs more teststest-writer - Test generation

E. Plugin Recommendations

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

Codebase SignalRecommended Plugin
General productivityanthropic-agent-skills - Core skills bundle
Document workflowsInstall docx, xlsx, pdf skills
Frontend developmentfrontend-design plugin
Building AI toolsmcp-builder for MCP development

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.

## Codex 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**: `Codex mcp add context7`

---

### 🎯 Skills

#### [skill name]
**Why**: [specific reason]
**Create**: `.Codex/skills/[name]/SKILL.md`
**Invocation**: User-only / Both / Codex-only
**Also available in**: [plugin-name] plugin (if applicable)
```yaml
---
name: [skill-name]
description: [what it does]
disable-model-invocation: true  # for user-only
---

⚡ Hooks

[hook name]

Why: [specific reason based on detected config] Where: .Codex/settings.json


🤖 Subagents

[agent name]

Why: [specific reason based on codebase patterns] Where: .Codex/agents/[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

- Document generation (docx, xlsx, pptx, pdf — also in plugins)
- Frequently repeated prompts or workflows
- Project-specific tasks with arguments
- Applying templates or scripts to tasks (skills can bundle supporting files)
- Quick actions invoked with `/skill-name`
- Workflows that should run in isolation (`context: fork`)

**Invocation control:**
- `disable-model-invocation: true` — User-only (for side effects: deploy, commit, send)
- `user-invocable: false` — Codex-only (for background knowledge)
- Default (omit both) — Both can invoke

### 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 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 Codex for automated pipelines:

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

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

Permissions for Hooks

Configure allowed tools in .Codex/settings.json:

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.