/add-cli

Automate adding Python CLIs to the EarlBear ecosystem with brew formulas and cowork plugins.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/EarlBear/homebrew-tap --skill add-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: /add-cli
Source: https://github.com/EarlBear/homebrew-tap/tree/main/.claude/skills/add-cli
Command: npx skills add https://github.com/EarlBear/homebrew-tap --skill add-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides an end-to-end blueprint for adding a new Python CLI to the EarlBear ecosystem, covering source setup, brew formula creation, cowork plugin wiring, and release orchestration.

Core Features & Use Cases

  • Stepwise guidance across source preparation, syncing into the EarlBear Homebrew mirror, template formula creation, cowork plugin generation, and validation pipelines.
  • Real-world scenarios include introducing a new CLI to EarlBear's clis, packaging it for brew, and enabling Claude cowork sessions via a prebuilt plugin binary.

Quick Start

Follow the steps to add a new Python CLI to EarlBear by preparing the source, generating a brew formula, implementing a cowork plugin, and wiring the release.

Frequently Asked Questions about /add-cli

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

FAQPage Schema
How do I add a new Python CLI to the EarlBear ecosystem and make it brew installable?

To add a Python CLI to the EarlBear ecosystem, you follow an end-to-end process covering source preparation, syncing into the Homebrew mirror, formula generation, cowork plugin creation, and release wiring.

What does generating a cowork plugin for a Python CLI involve?

Generating a cowork plugin involves creating a prebuilt plugin binary that enables Claude cowork sessions for your Python CLI, integrated into the end-to-end release wiring and validation pipelines.

How do I create a Homebrew formula for a Python CLI project?

Creating a Homebrew formula involves scaffolding a template formula during the source syncing phase to structure your Python CLI for brew installability within the EarlBear Homebrew mirror.

Do I need a specific source organization to package my Python CLI for brew?

Yes, a specific source organization is required to package your Python CLI for brew, mandating proper source preparation and syncing to satisfy EarlBear's requirements for formula scaffolding and marketplace integration.

What's the best way to wire release pipelines for a Python CLI with cowork integration?

The best way to wire release pipelines is using an end-to-end automation blueprint that connects source setup, formula scaffolding, and cowork plugin packaging to validate the Python CLI release comprehensively.