Open-Source Devs Need To Ship Distribution, Not Just Code.
Summary
Open-source developers must now ship "distribution" alongside their code to ensure tools are discoverable and invokable by AI coding agents like Cursor, Claude Code, and Codex. This distribution layer, comprising CLIs, skill files, plugin bundles, and marketplace manifests, allows agents to find, understand, and use tools without human intervention, unlike traditional `npm install` methods. The article explains that a CLI provides a machine-invokable contract, a plugin bundle (e.g., `SKILL.md`) offers operational context and usage rules, and marketplace manifests (`.cursor-plugin/marketplace.json`) enable discovery and installation. Examples like a hypothetical `pollgate` tool and the author's `sixthextinction/knn` project illustrate how a lack of this layer hinders agent adoption, even with good code. Developers are urged to integrate minimum viable distribution early, treating it as a critical product surface.
Key takeaway
For open-source developers aiming for agent adoption, prioritize shipping a distribution layer on day one, not after 1.0. Your project needs a CLI with `--help` as documentation, a `SKILL.md` explaining usage and pitfalls, and marketplace JSON for your primary ecosystem. This ensures AI coding agents can find, understand, and invoke your tool, preventing common setup failures and enabling early adopters to integrate your solution effectively. Neglecting this makes your tool invisible to the new "package managers."
Key insights
Open-source tools require distribution layers like CLIs, skill files, and marketplace manifests to be discoverable and invokable by AI coding agents.
Principles
- Distribution is now part of the product surface, not just code.
- Agents prioritize tools with discoverable CLIs, plugin bundles, and marketplace entries.
- CLIs serve as stable external APIs for machine invocation, surviving internal refactors.
Method
Ship a CLI with predictable flags and JSON output, create a plugin bundle with `SKILL.md` for context and rules, and provide marketplace manifests for primary agent ecosystems.
In practice
- Design CLIs with idempotent operations and JSON output flags for agent parsing.
- Document execution order and dependencies in `SKILL.md` to guide agent workflows.
- Test distribution by having a fresh agent session install and use the tool successfully.
Topics
- Open-Source Software
- AI Coding Agents
- Software Distribution
- CLI Design
- Agent Plugins
- Marketplace Manifests
- Model Context Protocol
Code references
Best for: AI Engineer, Software Engineer, MLOps Engineer
Related on AIssential
Editorial summary, takeaway, and curation by AIssential. Original article published by Artificial Intelligence in Plain English - Medium.