# Standardize Claude Code Tool Presets

Agent tool access can vary across similar roles, creating inconsistent workflows. This skill documents reusable Claude Code presets for development, analysis, research, and coordination agents.

## Install

```bash
npx skillstore add joseph obrien/89jobrien-tool-presets
```

## Metadata

- Status: approved
- Slug: 89jobrien-tool-presets
- Version: 1.0.1
- Author version: 1.0.1
- Skillstore revision: r1
- Version status: valid
- Tree hash: ed742ef669d04cd49701fb3a33028b97b0c22140222905c6ed50495e0d490bb9
- Author: Joseph OBrien
- GitHub username: 89jobrien
- License: MIT
- Repository: https://github.com/89jobrien/steve/tree/main/steve/skills/tool-presets
- Ref: c4037264bbd363c572662d6154a3ab28f5ca4f53
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/89jobrien-tool-presets
- Manifest: https://skillstore.pages.dev/api/skills/89jobrien-tool-presets/manifest

## Capabilities

- Lists six named tool presets and their included tool sets.
- Explains when to choose development, file operations, analysis, research, orchestration, and full-stack presets.
- Provides a frontmatter example for applying a preset pattern to an agent definition.
- Documents separate reference files for development, file operations, analysis, research, and orchestration presets.
- Identifies example agent roles that fit each detailed preset.

## Use Cases

- Configure Developer Agents: Choose consistent tool access for agents that write code, run tests, and handle build tasks.
- Document Agent Standards: Create a shared reference for teams that maintain several Claude Code agent definitions.
- Review Tool Access: Compare preset choices before granting Bash, web access, write access, or coordination tools.

## Prompt Templates

### Choose a Preset

```
I am creating a Claude Code agent for documentation updates. Use the tool-presets skill to recommend the best preset and explain why.
```

### Apply a Preset

```
Use the tool-presets skill to update my agent plan with the right tools for code refactoring without shell execution.
```

### Compare Access Levels

```
Compare dev-tools, file-ops, and analysis for a code review agent. Recommend the least privileged preset that still supports the work.
```

### Design an Agent Matrix

```
Use the tool-presets skill to build a permission matrix for developer, reviewer, researcher, and coordinator agents across our team.
```

## Limitations

- Does not enforce permissions or update agent files automatically.
- Does not include executable scripts or runtime validation.
- Full-stack guidance is broad and should be reviewed before use.
- Preset names still require tool names to be copied into each agent definition.

## Best Practices

- Select the least capable preset that can complete the agent task.
- Review Bash, WebSearch, WebFetch, and Task access before copying a preset.
- Document the reason for each preset choice in the agent definition.

## Anti Patterns

- Assigning full-stack to every agent for convenience.
- Giving Bash access to agents that only need read-only analysis.
- Treating preset documentation as permission enforcement.

## Security Audit

- Audited at: 2026-07-05T14:07:20.778\+00:00
- Summary: The static analyzer flagged Markdown backticks in SKILL.md as Ruby or shell execution. All static findings are documentation formatting or inline preset names, not executable code, but the full-stack preset should be used with least-privilege review.

## Stats

- Views: 212
- Downloads: 12
- Favorites: 0
- Popularity score: 0