Menu
Install the maverick CLI tool system-wide from the plugin directory.
| name | do-install |
| description | Install the maverick CLI tool system-wide from the plugin directory. |
| user-invocable | true |
| disable-model-invocation | false |
Install the maverick CLI from wherever this plugin is loaded — marketplace cache or local dev checkout.
Dispatch the maverick agent with task install and any user-provided arguments. The agent will follow the process below and return a structured result.
Locate the plugin root. This is the directory containing pyproject.toml. If ${CLAUDE_PLUGIN_ROOT} is set, use that. Otherwise resolve two levels above this SKILL.md (i.e. the parent of skills/do-install/). Fail with a clear error if pyproject.toml is not found at the resolved path.
Run the installer. From a shell:
uv run --directory <plugin-root> python -m maverick.install_cli
The module performs the install procedure end-to-end:
uv is on PATHgh (GitHub CLI) is on PATH — Maverick workflows depend on it for issue and PR operations; the installer fails with platform-specific install instructions if missingpyproject.toml exists at the plugin rootuv tool install --force <plugin-root>maverick is on PATH (warns about ~/.local/bin if not)Read(~/.claude/plugins/cache/thermite/maverick/**) to ~/.claude/settings.json permissions.allow (idempotent)Verify. Run maverick --help and capture the first line.
Report. Return a structured result: install path, whether the settings file was modified or already had the permission entry, and any PATH warnings.
Scan a project for missing best-practice areas and implement the top recommendation for each gap. Currently covers linting and unit testing. Installs tools, writes configs, and adds CI steps.
Implement a focused code change. Use this skill as the wrapper for any implementation work so the Maverick workflow report captures what was done and so the agent applies the project's coding standards before editing. Intended to be invoked once per task from inside a do-issue-* or do-epic phase, not standalone.
Run a security audit of the project's existing codebase and write a findings report to docs/security-audit.md. Covers secrets exposure, dependency vulnerabilities, authentication and authorisation patterns, input validation, transport security, and common OWASP risks. Run as part of do-init or on demand.
Create, restructure, or update technical documentation. Handles greenfield projects, refactoring non-compliant docs, and incremental updates after code changes.
Work on a multi-story GitHub epic end-to-end. Builds a DAG from the child stories, groups them into waves, runs waves in parallel via per-story worktrees, ejects PRs that fail agent-code-review for human handling, and propagates blocks to downstream stories. Requires git worktrees.
Initialise a project for use with Maverick — verifies the GitHub App, installs the CLI if needed, writes the project config with integration tracking, scaffolds docs, generates project skills, runs an initial cybersecurity audit, then commits the changes and opens a PR.