tap-deps-authoring

What problem does it solve?

Writing correct octomind-tap dep scripts is error-prone because scripts must follow strict header conventions, use shared platform logic, support multiple OS/package managers, and include matching companion documentation so automated validation can pass.

Core Features & Use Cases

• Standardized dep script headers: Ensures each deps/<org>/<tool>.sh declares dep, type (mcp|dep), description, check, and a homepage URL for registry consistency.
• Deterministic cross-platform installation pattern: Uses deps/lib/platform.sh to standardize OS/arch/package-manager detection, fast-path checks, and post-install verification.
• Correct MCP vs plain CLI behavior: Guides authors on whether the script’s goal is to make an MCP server runnable (via npx/uvx/runtime) or to install a standalone CLI tool used directly by agents.
• Companion documentation requirement: Enforces a matching deps/<org>/<tool>.md and the required sections for MCP servers and plain deps, enabling searchable, explainable registry entries.

Quick Start

Create or edit deps/<org>/<tool>.sh using the required header comments and the shared platform.sh flow, then run bash scripts/lint-deps.sh deps/<org>/<tool>.sh to verify it passes.