tool-presets_skill

This skill provides standardized tool presets for Claude Code agents to ensure consistent tool access across similar agent types.
  • Python

2

GitHub Stars

6

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill 89jobrien/steve --skill tool-presets

  • analysis.md610 B
  • dev-tools.md635 B
  • file-ops.md699 B
  • orchestration.md704 B
  • research.md657 B
  • SKILL.md2.0 KB

Overview

This skill provides standardized tool-set presets for Claude Code agents so teams can apply consistent capabilities across similar agent types. Presets map common tool names (Read, Write, Edit, Bash, WebSearch, etc.) to named profiles like dev-tools, file-ops, analysis, research, orchestration, and full-stack. Using these presets reduces configuration drift and speeds agent creation.

How this skill works

Declare a preset name in an agent's frontmatter to automatically assign the associated tool list. Each preset bundles a curated set of tool permissions and roles suited to a class of tasks (development, file manipulation, analysis, research, orchestration, or full capability). The skill enforces a clear, repeatable mapping so agents of the same type have identical tool access.

When to use it

  • Set up new agents that should share identical capabilities across a team
  • Standardize tool access for different agent roles (dev, researcher, analyst, orchestrator)
  • Quickly prototype agents without hand-selecting every tool
  • Create governance and security baselines for agent tool permissions
  • Replace ad-hoc tool lists with named, documented presets

Best practices

  • Choose the narrowest preset that satisfies the agent’s tasks to minimize unnecessary tool exposure
  • Document which preset is used and why in the agent frontmatter for future reviewers
  • Use dev-tools for active coding agents and file-ops for file-focused tasks to reduce risk
  • Reserve full-stack only for trusted meta agents that must delegate broadly
  • Keep preset definitions updated in a single source so changes affect all agents consistently

Example use cases

  • A coding assistant that writes and runs tests using the dev-tools preset (Read, Write, Edit, Bash)
  • A batch refactoring agent that searches and updates repositories using the file-ops preset
  • A static analysis agent that inspects codebases without execution using the analysis preset
  • A research agent that fetches web resources and drafts documentation with the research preset
  • A coordinator agent that assigns subtasks and updates trackers using the orchestration preset

FAQ

Reference the preset pattern in the agent frontmatter tools field so the agent tooling layer maps the preset to its tool list.

Can I customize a preset?

Yes — presets are templates. You can extend or restrict the tool list per agent, but prefer updating the canonical preset when many agents must change.

When should I use full-stack?

Use full-stack only for trusted agents that legitimately need comprehensive capabilities, such as meta-orchestration agents that delegate tasks across specialized agents.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
tool-presets skill by 89jobrien/steve | VeilStrat