tool-presets
npx machina-cli add skill aiskillstore/marketplace/tool-presets --openclawTool Presets Skill
Standardized tool set definitions for Claude Code agents. Use these presets to ensure consistent tool access across similar agent types.
Available Presets
| Preset | Tools | Best For |
|---|---|---|
dev-tools | Read, Write, Edit, Bash | Development/coding agents |
file-ops | Read, Write, Edit, Grep, Glob | File manipulation agents |
analysis | Read, Grep, Glob, Bash | Code analysis agents |
research | Read, Write, WebSearch, WebFetch | Research agents |
orchestration | Read, Write, Edit, Task, TodoWrite | Coordinator agents |
full-stack | All tools | Comprehensive agents |
Usage
Reference a preset in your agent's frontmatter:
---
name: my-agent
description: Agent description
tools: Read, Write, Edit, Bash # Use dev-tools preset pattern
skills: tool-presets
---
Preset Selection Guide
When to use dev-tools
- Writing or modifying code
- Running build/test commands
- General development tasks
When to use file-ops
- Searching codebases
- Refactoring across files
- Code analysis without execution
When to use analysis
- Read-only code review
- Pattern detection
- Static analysis
When to use research
- Documentation lookup
- External API research
- Web-based information gathering
When to use orchestration
- Multi-agent coordination
- Complex task breakdown
- Workflow management
When to use full-stack
- Comprehensive agents needing all capabilities
- Meta agents that delegate to others
Reference Files
For detailed tool lists per preset, see:
dev-tools.md- Development tools presetfile-ops.md- File operations presetanalysis.md- Code analysis presetresearch.md- Research tools presetorchestration.md- Multi-agent orchestration preset
Source
git clone https://github.com/aiskillstore/marketplace/blob/main/skills/89jobrien/tool-presets/SKILL.mdView on GitHub Overview
Tool Presets standardizes tool access by grouping tools into named presets (dev-tools, file-ops, analysis, research, orchestration, full-stack). They ensure consistent capabilities across similar agent types, reducing setup drift. Reference a preset in the agent frontmatter to align tools with the agent's role.
How This Skill Works
Presets are selected by listing a preset name in the agent's frontmatter tools field, such as dev-tools. Each preset maps to a curated set of capabilities (Read, Write, Edit, Bash, Grep, WebSearch, Task, etc.), delivering consistent access across agents. This makes it easy to swap tool access without reconfiguring individual agents.
When to Use It
- When you want coding agents to have a ready-made DevTools toolkit for development tasks.
- When you need file-manipulation agents with Read, Write, Edit and search capabilities.
- When performing code analysis or reviews with Read, Grep, Glob and Bash.
- When research agents must perform web lookup and data gathering.
- When coordinating multiple agents with orchestration needs for task management.
Quick Start
- Step 1: Choose a preset that fits the agent role, e.g. dev-tools.
- Step 2: Reference the preset in the agent's frontmatter Tools field.
- Step 3: Deploy the agent and verify tool access is as expected.
Best Practices
- Align the agent's role with the most appropriate preset.
- Document the selected preset in the agent's frontmatter for clarity.
- Avoid mixing tool sets across dissimilar agent types.
- Test presets in a staging environment before production use.
- Keep presets up to date as tooling evolves.
Example Use Cases
- Dev bot uses dev-tools for coding tasks, builds, and tests.
- File-ops bot searches codebases and refactors files.
- Code-analysis bot runs static checks with analysis preset.
- Research bot gathers external sources using the research preset.
- Coordinator bot orchestrates workflows with the orchestration preset.
