meticulous-cli-update

Install or update the Meticulous CLI The @alwaysmeticulous/cli package is under active development and ships frequent changes and improvements. Other Meticulous skills assume the meticulous command is on PATH and up to date, so run this skill once at the start of any Meticulous workflow. This only needs to run once per conversation . If you've already run it earlier in this conversation, skip it — there's no need to re-check the version or re-update on every Meticulous skill invocation. How to handle the install/update commands This skill normally runs as a sub-step of another Meticulous skill. The install/update commands below (Steps 1, 3, and 5) are security-sensitive — they install packages and reach the network — so treat them as best-effort and non-blocking : You generally can't tell in advance whether a command is whitelisted. If it's whitelisted it runs silently; if not, attempting it surfaces a permission prompt. Either outcome is fine — let that be how you find out. If a command needs permission you don't have (a prompt appears, or the user declines it), treat that as the signal to recommend rather than force . Tell the user it's recommended to do XYZ — e.g. "It's recommended to update the Meticulous CLI by running npm install --global @alwaysmeticulous/cli@latest " — and move on. A declined prompt is not a failure; it just means "do it later." If the user doesn't want to run it now, continue anyway. Do not stop the workflow; carry on with the remaining steps and then return to the calling skill. The only hard requirement is that the meticulous command exists at all (Step 1) — if it's genuinely not installed and the user declines to install it, no Meticulous skill can proceed, so stop there. The read-only checks ( meticulous --version , npm view … , meticulous auth whoami ) are safe to run directly. Step 1 — Check the installed version Show more Installs 557 Repository alwaysmeticulous/skills GitHub Stars 2 First Seen May 15, 2026 Security Audits Gen Agent Trust Hub Pass Snyk Warn