dependency-tracker

What This Skill Does

The Dependency Tracker is an automated maintenance tool designed to keep your development environment clean, secure, and up-to-date. By periodically auditing your local system, it identifies outdated Node.js versions, npm versions, and global packages that may pose security risks or compatibility issues. The agent follows a structured workflow: it reads your project's technical specifications, performs a comprehensive audit, checks for available package updates, and compiles a detailed status report. This ensures that your local environment stays consistent with best practices and project requirements.

Installation

To install this skill, use the ClawHub command-line interface. Open your terminal and run the following command:

clawhub install openclaw/skills/skills/axelhu/dependency-tracker

Ensure you have the necessary permissions in your environment to execute commands and read system configurations before initiating the installation.

Use Cases

• Proactive Maintenance: Schedule the tool to run weekly via a cron job to ensure no security vulnerabilities linger in your global packages.
• Environment Standardization: Use the tool to ensure that multiple team members are using the same version of Node.js and npm across their machines.
• Tech Debt Reduction: Regularly identify outdated packages to plan and execute updates before major releases, preventing breaking changes during critical development phases.

Example Prompts

1. "Run the dependency tracker now and send me a full report of all outdated global npm packages."
2. "Please audit my environment dependencies and report back if my Node.js version is currently deprecated."
3. "Check for updates on all my global packages and output the results to the exec-logs folder."

Tips & Limitations

• Reporting Limits: The skill is configured to handle large reports gracefully. If your report exceeds 3800 characters, it will automatically segment the content into multiple, semantically complete messages to prevent data truncation.
• Error Handling: The tool includes a retry mechanism for Feishu delivery. If a network issue occurs, it will attempt one retry before explicitly alerting you, ensuring you are never left wondering if the report was sent successfully.
• Formatting: Always ensure that your references/spec.md is updated, as the agent relies on this file to tailor its audit logic to your specific project needs.
• Permissions: Ensure the agent has read access to your system's package manager directories and write access to the data/exec-logs/ directory for report generation.