opencode-tool-authoring

Define and validate OpenCode tool schemas with YAML frontmatter.

6|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/open-hax/opencode-skills --skill opencode-tool-authoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opencode-tool-authoring
Source: https://github.com/open-hax/opencode-skills/tree/main/.opencode/skills/opencode-tool-authoring
Command: npx skills add https://github.com/open-hax/opencode-skills --skill opencode-tool-authoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps ensure OpenCode tools are defined with proper schemas, predictable execution behavior, and clear documentation.

Core Features & Use Cases

  • Define input/output schemas for tools to enforce consistent usage.
  • Validate tool registration, execution, and documentation across projects.
  • Provide a guided workflow for creating and updating tools with safety checks.

Quick Start

Create or update a tool by adding a SKILL.md with a valid YAML frontmatter and implement the corresponding tool logic per the guidelines.

Frequently Asked Questions about opencode-tool-authoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define input and output schemas for OpenCode tools?

You validate tool registration and execution by applying schema checks to the YAML frontmatter and tool logic. This ensures consistent frontmatter structure, safe tool execution wiring, and clear documentation across projects.

What's the best way to create a custom OpenCode tool?

The best way to create a custom OpenCode tool is following a guided workflow: add a SKILL.md with valid YAML frontmatter, define input and output schemas, and implement the execution logic. This ensures safe, deterministic tool behavior.

Do I need YAML frontmatter to implement a new OpenCode tool?

Yes, you need YAML frontmatter to implement an OpenCode tool. It must include at least the name and description fields to satisfy the schema requirements and ensure the tool is registered and documented correctly.

Why does my OpenCode tool execution fail during validation?

OpenCode tool execution validation fails when the tool definition lacks proper YAML frontmatter structure, valid schemas, or deterministic execution wiring. Ensuring accurate steps, outputs, and references prevents these validation failures.