tool-protocol

Standardize automation tool discovery, composition, and building with metadata and safety checks.

7|2|Updated Dec 14, 2025
One-click install
npx skills add https://github.com/asafelobotomy/iCloud-Drive-Downloader --skill tool-protocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tool-protocol
Source: https://github.com/asafelobotomy/iCloud-Drive-Downloader/tree/main/.github/skills/tool-protocol
Command: npx skills add https://github.com/asafelobotomy/iCloud-Drive-Downloader --skill tool-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents ad-hoc scripting by guiding you to find existing tools, reuse built-in or plugin capabilities, and only then build new automation in a consistent, repeatable, and well-documented way.

Core Features & Use Cases

  • Tool discovery before building: checks a local toolbox index first, then considers built-in runtime capabilities and installed plugin tools before attempting a scratch build.
  • Decision-tree driven tool creation: enforces a structured process for locating, adapting, composing, or building tools with clear acceptance criteria.
  • Quality and safety guardrails: requires standardized headers, risk tiering (safe vs destructive), idempotency guidance, and reusability evaluation before saving to the toolbox.
  • Use Cases: creating a repeatable helper for a recurring workflow, adapting a near-match tool already in the toolbox, or composing multiple toolbox tools into a pipeline.

Quick Start

Ask an AI to automate a task, then instruct it to follow the Tool Protocol decision tree to find an existing tool, adapt or compose it when possible, and otherwise produce a small single-purpose tool with the required header and safety risk tiering.

Frequently Asked Questions about tool-protocol

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

FAQPage Schema
How do I stop writing one-off scripts and build reusable automation tools?

To stop writing one-off scripts, standardize automation utility discovery and creation by checking a local toolbox index, built-in runtime capabilities, and plugin tools before building new ones. This enforces idempotency, risk tiering, and metadata headers for safe reusability.

What is the best way to discover existing dev workflow tools before building a new one?

The best way to discover existing dev workflow tools is following a decision tree that sequentially checks a local toolbox index, evaluates built-in runtime capabilities, reviews installed plugin tools, and searches online before attempting a scratch build.

How do I add safety risk tiering to my automation scripts?

You add safety risk tiering to automation scripts by enforcing a standardized creation protocol that categorizes operations as safe versus destructive. This requires evaluating idempotency, adding metadata headers, and assessing reusability before saving the tool.

Can I compose multiple toolbox tools into a single pipeline?

Yes, you can compose multiple toolbox tools into a pipeline. The protocol supports adapting near-match tools already in the toolbox and composing them into repeatable command sequences for development, operations, or scripting workflows.

When should I build a new automation tool from scratch instead of reusing existing ones?

You should build a new automation tool from scratch only after exhausting a decision tree that checks local toolbox indexing, built-in runtime capabilities, plugin tools, and online search. The new tool must include metadata headers, idempotency, and risk tiering.