keep-clis-sharp

Solid

Audit and update CLI tools, npm packages, and repo scripts; ensure versions are current and documented. Use when the user says CLIs are outdated, tools need updating, keeping knives sharp, or when doing periodic tool maintenance.

Data & Documents 364 stars 68 forks Updated today MIT

Install

Quality Score: 89/100

Stars 20%

85

Recency 20%

100

Frontmatter 20%

70

Documentation 15%

100

Issue Health 10%

80

License 10%

100

Description 5%

100

Skill Content

# Keep CLIs Sharp (Tool Keeper) You are the **tool keeper**: keep repo CLIs, npm deps, and scripts current and documented so JARVIS and humans can rely on them. ## When to use - User says "CLIs are outdated", "keep our knives sharp", "update our tools", or "tool maintenance" - Periodic upkeep (e.g. after major Node/npm or platform releases) - Before a release or deep-work cycle ## Workflow 1. **Inventory** — List what to sharpen: - **npm:** Root `package.json`, `apps/jarvis-ui/package.json`, `olive-e2e/package.json` - **Platform CLIs:** Per `jarvis/TOOLS.md` → Platform CLIs (Maestro): Vercel, Railway, Stripe, Fly.io, Supabase, Netlify, Wrangler, Cursor - **Repo scripts:** Prefer scripts in `scripts/`; note any that call external CLIs or pinned versions 2. **Check versions** — Run, then interpret: - **npm (each package root):** `npm outdated` (or `npm ls --depth=0`). Note major vs minor/patch. - **CLIs:** `vercel --version`, `railway --version`, `stripe --version`, `supabase --version`, etc. Compare to latest from docs or `npm view <cli> version` if installed via npm. 3. **Update safely** — Prefer non-breaking first: - **npm:** `npm update` for in-range; for major bumps, update one dependency at a time, run tests, then commit. - **CLIs:** Install/upgrade via official method (e.g. `npm i -g vercel`, `brew upgrade supabase`, or vendor docs). Do not guess; check each CLI’s recommended install/upgrade path. 4. **Document** — Keep the shop ledger: - ...

Details

Author: majiayu000
Repository: majiayu000/claude-skill-registry
Created: 5 months ago
Last Updated: today
Language: HTML
License: MIT

Integrates with

Vercel · Cloud Netlify · Cloud Supabase · Cloud Fly.io · Cloud npm · DevTools

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

maintain

Updates dependencies, applies security patches, and manages package versions on a regular cadence. This skill should be used when the user asks to "update dependencies", "run dependency maintenance", "check for outdated packages", "apply security patches", "update npm packages", "run stage 9", "check for vulnerabilities", or "upgrade dependencies", or when the transmute-pipeline agent reaches Stage 9 of the pipeline.

4 Updated yesterday

AI & Automation Listed

openclaw-tune

OpenClaw **system-level** maintenance — cleans sessions/.bak rotation, disk bloat under ~/.openclaw/, validates model fallback chain, audits cron health, prunes short-term-recall noise. Run after `openclaw update` or every 1-2 weeks. Different from **workspace document tune-up** (single-responsibility canonical .md files, token waste scan) which is handled by Claude auto-memory `openclaw-workspace-tuneup` — triggered when user says "优化下 openclaw 的文档/skill/canonical". This skill is for `openclaw` daemon/CLI maintenance, NOT for workspace docs.

2 Updated today

AI & Automation Listed

claude-md

Keep the CLAUDE.md your agents rely on accurate and lean instead of stale. Use when maintaining (not first creating) a CLAUDE.md — syncing it with architecture, conventions and commands as the project evolves, and pruning bloat so it stays scannable. Complements the built-in /init by owning the ongoing upkeep.

3 Updated yesterday

AI & Automation Solid

check-sdk-updates

Check whether Claude Code, Claude Agent SDK, and Codex SDK have new versions on npm. Use when the user asks to check for SDK/CLI updates, e.g. "check sdk updates", "check claude code update", "有沒有更新", "檢查 SDK 版本".

399 Updated today

Data & Documents Solid

docs-keeper

Documentation organization, maintenance, and cleanup. USE WHEN: organizing docs, cleaning project root, updating documentation, checking for redundancy, maintaining docs structure. NOT FOR: technical implementation (use relevant technical skill). Examples: <example> Context: User added documentation to wrong location. user: "I added a new API doc file to the root directory" assistant: "I'll use docs-keeper to organize it in the proper docs/ location." <commentary>File organization is docs-keeper responsibility.</commentary> </example> <example> Context: User needs to update docs after code changes. user: "I modified the auth system and need to update the docs" assistant: "I'll use docs-keeper to update the authentication documentation." <commentary>Documentation updates are docs-keeper responsibility.</commentary> </example>

364 Updated today