cli-packaging-patterns Skill
Use when building a new CLI tool that needs one-line install, subcommand dispatch, or layered config. Covers uv/npm install, a default-action dispatcher, and 3-tier config resolution (flags, config file, defaults). Published by microsoft in amplifier-bundle-skills.
Decision snapshot
Is this a fit?
Deployment, Design and media, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is cli-packaging-patterns Skill?
Use when building a new CLI tool that needs one-line install, subcommand dispatch, or layered config. Covers uv/npm install, a default-action dispatcher, and 3-tier config resolution (flags, config file, defaults). Published by microsoft in amplifier-bundle-skills. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Deployment
- Design and media
- Deployment use cases
- Design and media use cases
Declared skill metadata
- Source file: skills/cli-packaging-patterns/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use cli-packaging-patterns Skill
- Use it for deployment.
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/amplifier-bundle-skills
- Skill file: skills/cli-packaging-patterns/SKILL.md
What it does
Use when building a new CLI tool that needs one-line install, subcommand dispatch, or layered config. Covers uv/npm install, a default-action dispatcher, and 3-tier config resolution (flags, config file, defaults).
Skill instructions
CLI Packaging & Distribution The Pattern Problem: You want a CLI tool that installs cleanly from a git URL with zero manual steps — no cloning, no virtual env, no PATH fiddling. Approach: Combine pyproject.toml [project.scripts] with hatchling build backend, a main.py dual entry point, and argparse with a default-action subcommand design so mytool and mytool serve do the same thing. Pattern proven in production across multiple Python CLI tools and web services. When this skill is NOT the right answer This skill assumes a pure Python CLI distributed via uv tool install. If your project does not fit that profile, use a different pattern: | Project shape | Use instead | |--------------|-------------| | Multi-language stack (Python + Node + Docker) | one-line-installer-patterns | | Raw TS/React app with no Python wrapper | one-line-installer-patterns (or publish to npm) | | Tool that bootstraps system prerequisites | one-line-installer-patterns | | Containerized multi-service app | Ship do
Verified compatibility and discovery
Frequently asked questions
What is cli-packaging-patterns?
cli-packaging-patterns is a open-source AI agent skill with Copy skill directory. Use when building a new CLI tool that needs one-line install, subcommand dispatch, or layered config.
Who is cli-packaging-patterns best for?
cli-packaging-patterns is best for reusing agent instructions, scripts, and references, deployment workflows, design and media workflows.
How do I install cli-packaging-patterns?
Install or run cli-packaging-patterns using Copy skill directory. Check cli-packaging-patterns for the latest setup command.
Is cli-packaging-patterns actively maintained?
cli-packaging-patterns may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
