keep-clis-sharp — community keep-clis-sharp, JARVIS, community, ide skills

v1.0.0
GitHub

About this Skill

Perfect for DevOps Agents needing automated CLI and dependency management capabilities. 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 doi

repairman29 repairman29
[0]
[0]
Updated: 3/2/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reviewed Landing Page Review Score: 9/11

Killer-Skills keeps this page indexable because it adds recommendation, limitations, and review signals beyond the upstream repository text.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Quality floor passed for review Locale and body language aligned
Review Score
9/11
Quality Score
51
Canonical Locale
en
Detected Body Locale
en

Perfect for DevOps Agents needing automated CLI and dependency management capabilities. 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 doi

Core Value

Empowers agents to maintain up-to-date repository CLIs, npm dependencies, and scripts using natural language workflow automation, ensuring seamless interaction with tools like JARVIS and facilitating efficient periodic upkeep and release cycles through Node/npm and platform releases.

Ideal Agent Persona

Perfect for DevOps Agents needing automated CLI and dependency management capabilities.

↓ Capabilities Granted for keep-clis-sharp

Automating CLI updates for improved productivity
Maintaining accurate documentation for human and AI collaboration
Synchronizing npm dependencies for consistent project environments

! Prerequisites & Limits

  • Requires access to repository and package.json files
  • Limited to Node/npm and compatible platforms
  • Dependent on periodic upkeep for optimal performance

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is keep-clis-sharp?

Perfect for DevOps Agents needing automated CLI and dependency management capabilities. 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 doi

How do I install keep-clis-sharp?

Run the command: npx killer-skills add repairman29/JARVIS/keep-clis-sharp. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for keep-clis-sharp?

Key use cases include: Automating CLI updates for improved productivity, Maintaining accurate documentation for human and AI collaboration, Synchronizing npm dependencies for consistent project environments.

Which IDEs are compatible with keep-clis-sharp?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for keep-clis-sharp?

Requires access to repository and package.json files. Limited to Node/npm and compatible platforms. Dependent on periodic upkeep for optimal performance.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add repairman29/JARVIS/keep-clis-sharp. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use keep-clis-sharp immediately in the current project.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

keep-clis-sharp

Install keep-clis-sharp, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

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:

    • jarvis/TOOLS.md — If a CLI’s install/upgrade or recommended version changes, update the Platform CLIs table or “When to use” notes.
    • RUNBOOK.md — If a script or CLI command changes (e.g. new Supabase CLI flags), update the relevant section.
    • Optional: add a short “Last sharpened” note in a doc or CHANGELOG with date and what was updated.

Conducting rules

  • One sweep, then report: Run the checks; summarize what’s outdated, what you updated, and what you deferred (and why).
  • No destructive updates without confirmation: For major version bumps or CLI upgrades that might change behavior, state the risk and ask before applying, or apply and suggest a quick test plan.
  • Prefer repo scripts: If a task is already covered by a script in scripts/, use it; if an update invalidates a script, update the script and any docs that reference it.

Quick checklist (copy and track)

- [ ] npm outdated (root, apps/jarvis-ui, olive-e2e)
- [ ] Platform CLIs: vercel, railway, stripe, supabase, fly, netlify, wrangler — version check
- [ ] Apply safe npm updates; document major bumps
- [ ] Update jarvis/TOOLS.md if CLI install/usage changed
- [ ] Update RUNBOOK.md if script/CLI commands changed

Reference

  • Tool inventory and CLI list: reference.md
  • Repo scripts and when to use: jarvis/TOOLS.md (Repairman29 Repo Automation, Platform CLIs)

Related Skills

Looking for an alternative to keep-clis-sharp or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

The React Framework

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

★ 98.6k
⑂ 0
Developer