tap-deps-authoring

Author octomind-tap dep scripts with standardized headers and platform.sh validation.

3|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Muvon/octomind-tap --skill tap-deps-authoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tap-deps-authoring
Source: https://github.com/Muvon/octomind-tap/tree/main/skills/tap-deps-authoring
Command: npx skills add https://github.com/Muvon/octomind-tap --skill tap-deps-authoring

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about tap-deps-authoring

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

FAQPage Schema
How do I write dep scripts that install tools reliably across macOS and Linux?

To write reliable dep scripts, source deps/lib/platform.sh for OS/arch detection, enforce fast-path checks with post-install verification, and validate using scripts/lint-deps.sh.

What metadata is required for octomind-tap dep script headers?

Required dep script header metadata includes dep, type (mcp|dep), description, check, and a homepage URL. This standardization ensures registry consistency and allows automated validation scripts to pass.

How do I create an MCP server installation script versus a plain CLI tool dep?

MCP server scripts provision runtimes using npx or uvx to make the server runnable, while plain dep scripts install standalone CLI tools used directly by agents, with both requiring matching companion .md documentation.

Why does my dep script fail validation during automated checks?

Dep script validation fails when required header metadata is missing, platform.sh is not sourced, fast-path pkg_check and post-install verification are absent, or a matching companion .md file lacks required sections.

Can I use platform.sh to standardize package manager detection for dep scripts?

Yes, sourcing deps/lib/platform.sh standardizes package manager detection across macOS and major Linux distributions, providing deterministic cross-platform installation patterns and fast-path checks for dep scripts.