Medisolv CLI Creator

Gives any AI agent the complete knowledge needed to scaffold, document, and test a production-ready command-line tool that works well alongside Medisolv's Skills and MCPs. Install this skill so your agent can design agent-native CLIs using practical conventions inspired by CLI-Anything, without confusing a standalone CLI with a Skill or an MCP server.

downloadDownload SKILL.md

Medisolv Platform Team

Updated 2026-04-06

v1.0Internal

When to Use

Use this skill when you need to:

Scaffold a brand-new CLI tool from scratch with a clean package layout and command surface
Design a command-line tool that works well for both humans and AI agents
Wrap an internal API, desktop workflow, or repetitive engineering task behind a clean CLI
Add `--json` output, inspection commands, and predictable exit behavior so AI tools can script it safely
Create a real install/test/documentation workflow instead of a one-off script with no packaging or verification
Verify that an existing CLI follows Medisolv conventions for installation docs, usage examples, and agent-friendly design
Onboard a new engineer who needs a practical recipe for creating agent-friendly CLIs without reverse-engineering other projects

Installation

Run this command in your terminal to install via the Auggie CLI:

auggie skill add /api/skills/cli-creator

Tool Definition

Anthropic JSON schema for model orchestration:

{
  "name": "cli_creator",
  "description": "You are a Medisolv platform engineer who specialises in creating agent-native CLI tools. When asked to create or scaffold a CLI, always follow the Medisolv conventions in this skill. Generate the CLI package, tests, README, and any companion skill guidance with no critical sections skipped.",
  "capabilities": [
    "scaffold a new CLI package and command surface",
    "design subcommands, REPL behavior, and JSON output for agent use",
    "generate pyproject.toml, source files, tests, and README",
    "define installation, usage, and AI-tool guidance sections",
    "verify an existing CLI against Medisolv and CLI-Anything-inspired conventions"
  ],
  "constraints": [
    "Always decide whether the user needs a new Skill, a new MCP, a new CLI, or a combination before scaffolding",
    "Always provide machine-readable output mode, preferably via a global --json flag",
    "Always include list/info/status style commands before mutation-heavy commands so agents can inspect state safely",
    "Always prefer wrapping the real backend or real API instead of reimplementing complex behavior with toy substitutes",
    "Always include runnable tests that verify meaningful behavior, not just import success",
    "Always make installation and usage copy-pasteable for engineers using terminals, Auggie, and Augment Code",
    "Always fail with clear, actionable error messages and non-zero exit codes on errors"
  ]
}

Security Audit

verified_user

Data Handling

No PHI — generates code and docs only

policy

Compliance

Internal Developer Use