Skip to content
Back to skills

Built In Tools

ASecurity

"Routes OpenHands built-in tool names, default presets, tool

  • 247 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 9, 2026
toolsgoshell

Works with

  • terminal

Security analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned September 9, 2026

npx -y skills add VectorSpaceLab/AREX-Skill --skill built-in-tools --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Built In Tools?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Built In Tools
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/vectorspacelab-built-in-tools/badge)](https://www.skillsdirectory.com/skills/vectorspacelab-built-in-tools)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: built-in-tools
description: "Routes OpenHands built-in tool names, default presets, tool
  registration, browser availability, workflow scripts, and sub-agent tool
  wiring."
disable-model-invocation: true
metadata:
  disco-role: operating
license: MIT
---

# Built-in Tools

Use this sub-skill for `openhands-tools`: tool names, registration, resolution, default presets, browser availability, workflow scripts, and the built-in sub-agent tool sets.

## What this route owns

- `register_tool`, `resolve_tool`, `list_registered_tools`, `list_usable_tools`, and module qualnames.
- `TerminalTool`, `FileEditorTool`, `TaskTrackerTool`, `BrowserToolSet`, `WorkflowToolSet`, `TaskToolSet`, and related helper tools.
- Default presets such as `get_default_tools()`, `get_default_agent()`, and `register_default_tools()`.
- Tool-set usability checks and the registry behavior that surfaces tool availability.
- Workflow tool validation and safe script execution constraints.

## Start here

Read [`references/tool-catalog.md`](references/tool-catalog.md) for the public tool names and their primary roles. Read [`references/workflow-tool.md`](references/workflow-tool.md) for the dynamic workflow script model. Read [`references/troubleshooting.md`](references/troubleshooting.md) when a tool is missing, browser support is unavailable, or a workflow script is rejected.

Run [`scripts/list_default_tools.py`](scripts/list_default_tools.py) to print the default tool names and registry state.

## Typical triggers

- "Which tool should I use for shell commands or file edits?"
- "Why is the browser tool missing?"
- "How do I register a custom tool?"
- "How do workflow scripts work?"
- "Why does `/server_info` omit a tool?"

## Cross-links

- For local agent lifecycle and `Conversation` creation, go to [`../agent-core/SKILL.md`](../agent-core/SKILL.md).
- For remote custom-tool imports on agent-server, go to [`../remote-runtime/SKILL.md`](../remote-runtime/SKILL.md).
- For maintainer checks on tool registration, go to [`../repo-development/SKILL.md`](../repo-development/SKILL.md).

Files in this skill

  • SKILL.md2 KB
  • references/tool-catalog.md1.9 KB
  • references/troubleshooting.md781 B
  • references/workflow-tool.md1 KB
  • scripts/list_default_tools.py878 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…