Back to list
oakoss

my-reviewer

by oakoss

Open-source SaaS starter kit with React, TanStack, and Better Auth

0🍴 0📅 Jan 26, 2026

SKILL.md


name: meta:agent-creator description: Create specialized agents for Claude Code. Use for agent, sub-agent, subagent, autonomous, task agent, custom agent, agent definition, agent config

Agent Creator

Quick Start

Step 1: Create the agent

# .claude/agents/my-reviewer.md

---

name: my-reviewer
description: Review code for specific patterns. Use proactively after implementing features.
tools: Read, Grep, Glob
model: haiku

---

# My Reviewer

You are a code reviewer. Check for:

- Pattern 1
- Pattern 2

## Output Format

\`\`\`markdown

## Summary

[Assessment]

## Issues

1. [Issue]: [File:line] - [Description]

## Verdict

[APPROVE / REQUEST CHANGES]
\`\`\`

Step 2: Validate (required)

Always run validation after creating or modifying an agent:

uv run .claude/skills/meta-agent-creator/scripts/validate-agent.py .claude/agents/my-reviewer.md

Fix any errors before committing.

Agent Locations

TypeLocationScopePriority
Project.claude/agents/Current projectHighest
CLI--agents flag (JSON)Session onlyMedium
User~/.claude/agents/All projectsLower
PluginPlugin's agents/ dirPlugin usersLowest

When names conflict, higher priority wins.

Managing Agents

Use /agents command for interactive agent management (view, create, edit, delete).

Built-in Agents

AgentModelToolsPurpose
general-purposeSonnetAllComplex multi-step tasks, can modify files
PlanSonnetRead, Glob, Grep, BashResearch in plan mode
ExploreHaikuRead, Glob, Grep, Bash (read-only)Fast codebase search

Explore Thoroughness Levels

Specify: quick (fast lookups), medium (balanced), or very thorough (comprehensive).

YAML Frontmatter

Required Fields

---
name: agent-name # Lowercase, hyphens
description: What this agent does. Use proactively when [triggers].
---

Optional Fields

FieldPurposeDefault
toolsComma-separated tool listInherits ALL tools if omitted
modelModel to usesonnet (or use inherit)
permissionModePermission handlingdefault
skillsAuto-load skillsNone (agents DON'T inherit skills from parent)
---
name: agent-name
description: Description with triggers
tools: Read, Grep, Glob, Bash # Omit to inherit all tools
model: inherit # Use parent's model
permissionMode: default
skills: auth, database # Must explicitly list - no inheritance
---

Important: Subagents do NOT inherit skills from the parent conversation. You must explicitly list skills in the skills field.

Permission Modes

ModeBehavior
defaultNormal permission prompts
acceptEditsAuto-approve file edits
dontAskSkip all permission dialogs
bypassPermissionsNo permission checks at all
planPlanning mode (research only)
ignoreIgnore permission requirements

CLI-based Agents

Define agents dynamically with --agents flag:

claude --agents '{
  "code-reviewer": {
    "description": "Expert code reviewer. Use proactively after code changes.",
    "prompt": "You are a senior code reviewer...",
    "tools": ["Read", "Grep", "Glob", "Bash"],
    "model": "sonnet"
  }
}'

Useful for quick testing, session-specific agents, or automation scripts.

Resumable Agents

Agents can be resumed to continue previous conversations:

> Use code-analyzer to review the auth module
[Agent completes, returns agentId: "abc123"]

> Resume agent abc123 and also check the authorization logic
[Agent continues with full previous context]
  • Each execution gets a unique agentId
  • Transcripts stored in agent-{agentId}.jsonl
  • Use resume parameter with the agent ID to continue

Disabling Agents

Disable specific agents using permission rules:

{
  "permissions": {
    "deny": ["Task(Explore)", "Task(Plan)"]
  }
}

Or via CLI:

claude --disallowedTools "Task(Explore)"

Model Selection Guide

ModelCostSpeedUse Case
haikuLowFastCode review, style checks, simple validation
sonnetMediumMediumDebugging, security analysis, complex reasoning
opusHighSlowArchitecture decisions, multi-system analysis

Decision Tree

Is this a simple checklist task?
  → Yes: haiku
  → No: Does it require deep reasoning or security analysis?
    → Yes: sonnet
    → No: Does it involve architecture or cross-system decisions?
      → Yes: opus
      → No: sonnet

Tool Selection Guide

ToolPurposeInclude When
ReadRead file contentsAlways (basic exploration)
GrepSearch content patternsPattern matching needed
GlobFind files by nameFile discovery needed
BashRun shell commandsDiagnostics, tests, builds
WriteCreate new filesAgent creates artifacts
EditModify existing filesAgent makes code changes
WebFetchFetch web contentDocumentation lookup
WebSearchSearch the webResearch tasks

Common Tool Combinations

# Read-only reviewer
tools: Read, Grep, Glob

# Investigator with diagnostics
tools: Read, Grep, Glob, Bash

# Agent that can fix issues
tools: Read, Grep, Glob, Edit

# Research agent
tools: Read, Grep, Glob, WebFetch, WebSearch

Agent Templates

See reference.md for complete templates:

  • Review Agent - Code review with checklist and structured output
  • Investigation Agent - Debugging with systematic process
  • Exploration Agent - Codebase discovery and documentation
  • Security Audit Agent - Vulnerability assessment

Best Practices

  1. Start with Claude-generated agents: Use /agents to generate initial agent, then customize
  2. Design focused agents: One clear responsibility per agent
  3. Write detailed prompts: Include instructions, examples, and constraints
  4. Limit tool access: Only grant necessary tools for security and focus
  5. Version control: Check project agents into git for team sharing
  6. Use proactive triggers: Include "use PROACTIVELY" or "MUST BE USED" in descriptions

Common Mistakes

MistakeImpactCorrect Pattern
Using opus for simple reviewsSlow, expensiveUse haiku for checklist tasks
No output format templateInconsistent responsesAlways include structured format
Explicit tools when not neededLoses MCP toolsOmit tools to inherit all
Expecting skill inheritanceMissing contextExplicitly list skills needed
Generic role descriptionPoor focusBe specific about domain/project
Too many responsibilitiesUnfocused agentOne clear purpose per agent
No checklist for reviewersInconsistent reviewsInclude explicit checklist

Validation

Run the validator to check agent structure:

uv run .claude/skills/meta-agent-creator/scripts/validate-agent.py .claude/agents/my-agent.md

Checklist

  • File location: .claude/agents/<name>.md
  • YAML has name, description, tools, model
  • Description includes trigger phrases
  • Model appropriate for task complexity
  • Tools list matches actual usage
  • Role description is project-specific
  • Output format template included
  • All code blocks have language specifiers

Delegation

  • After creating/modifying agents: Run uv run .claude/skills/meta-agent-creator/scripts/validate-agent.py <agent.md>
  • Pattern discovery: For existing agent patterns, use Explore agent

References

Score

Total Score

65/100

Based on repository quality metrics

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

+10
説明文

100文字以上の説明がある

0/10
人気

GitHub Stars 100以上

0/15
最近の活動

1ヶ月以内に更新

+10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

+5

Reviews

💬

Reviews coming soon