dependency-tracker

Identify outdated dependencies across OpenClaw skills, npm/pip packages, and CLI tools.

55|5|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/blessonism/openclaw-skills --skill dependency-tracker-blessonism
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependency-tracker
Source: https://github.com/blessonism/openclaw-skills/tree/main/dependency-tracker
Command: npx skills add https://github.com/blessonism/openclaw-skills --skill dependency-tracker-blessonism

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Track and verify updates for all OpenClaw dependencies across managed, bundled, and workspace skills, as well as npm packages, pip packages, and CLI tools.

Core Features & Use Cases

  • Centralized dependency health: builds a manifest and compares local vs remote versions to surface updates.
  • Cross-skill maintenance: monitors GitHub/ClewHub skills, bundled assets, and workspace installations, plus package managers.
  • Use Case: when planning upgrades or responding to a user asking which components are out of date.

Quick Start

Run the scan to build the manifest, then run the check and generate a report to see current dependency status.

Frequently Asked Questions about dependency-tracker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check for outdated npm and pip dependencies in my workspace?

Dependency tracking scans local manifests and queries remote sources like npm and pip to compare local versus remote versions. It then generates a structured results object showing update statuses and release notes.

What is the best way to monitor OpenClaw skills and bundled assets for updates?

Monitoring OpenClaw dependencies involves building a centralized manifest and querying GitHub and ClewHub to surface available updates. This tracks managed, bundled, and workspace installations for comprehensive health checks.

Can I use this to plan CLI tool upgrades across my development environment?

Yes, you can use it to plan CLI tool upgrades during dependency health checks. It identifies outdated CLI tools alongside packages and skills, producing a report with statuses and release notes to guide upgrade planning.

Does dependency scanning work with both local manifests and remote package sources?

Dependency scanning works by reading local manifests to determine current versions and querying remote sources including GitHub, ClewHub, npm, and pip. It compares these to surface outdated components and structured update statuses.

How do I generate a dependency health report for my OpenClaw skills?

To generate a dependency health report, run the scan to build the manifest, then run the check to compare versions. The process produces a structured results object detailing statuses and release notes for your components.

Why does my dependency update check show different versions for workspace and bundled skills?

Update checks differentiate versions because the tool monitors managed, bundled, and workspace OpenClaw skills separately. It queries distinct remote sources for each installation type, resulting in varied statuses reflecting specific release tracks.