skill-deps-doctor_skill

This skill preflight-checks runtime dependencies for skills, detecting missing binaries, version mismatches, libraries, fonts, and project requirements before
  • Python

2.5k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill skill-deps-doctor

  • _meta.json289 B
  • SKILL.md4.1 KB

Overview

This skill performs a preflight dependency check for skills and projects to catch missing binaries, version mismatches, system libraries, fonts, and runtime probes before execution. It targets cross-platform issues including Playwright/Chromium native deps, CJK font availability, and project-level package hints. Use it to fail fast and produce actionable remediation steps rather than discovering problems at runtime.

How this skill works

The tool scans skill metadata (requires.bins) and project manifests (package.json, pyproject.toml, requirements.txt, Dockerfile) to detect missing executables and version violations. It probes live runtimes when requested (Playwright Chromium launches, node/python version checks) and inspects system-level artifacts like shared libraries (ldconfig on Linux) and fonts (fc-list). Results can be emitted as human-readable reports, CI-friendly JSON, or baseline snapshots for regression gating.

When to use it

  • Before running or deploying a skill to catch runtime dependency failures early.
  • In CI pipelines to gate changes with --snapshot and --baseline to detect regressions.
  • When onboarding a new development environment or provisioning containers/images.
  • During monorepo maintenance to scan many skills and projects recursively.
  • Before producing artifacts that rely on headless browsers, multimedia, or native extensions.

Best practices

  • Run with --probe for runtime smoke tests when networkless Chromium checks are required.
  • Use --check-dir to include project-level presets and cross-reference npm/pip hints against system libs.
  • Save a baseline snapshot and use --fail-on-new to prevent new environmental issues from landing in CI.
  • Enable --json output for machine parsing and --fix to generate remediation scripts you can review and apply.
  • Combine --profile presets (eg slidev, whisper, pdf-export) to validate curated dependency groups for common workflows.

Example use cases

  • Local developer runs skill-deps-doctor before starting work to ensure node/python versions and required binaries are present.
  • CI job runs the tool with --snapshot baseline.json and --fail-on-new to block builds that introduce new missing-dep findings.
  • Ops team scans a container image or VM with --check-dir to ensure Playwright/Chromium and its native .so deps are satisfied on Linux.
  • Documentation/packaging workflow generates a --fix script to automate apt/dnf/pacman hints for missing system packages.
  • Monorepo maintainers run a recursive scan to produce a dependency graph (dot/tree) and audit transitive native deps.

FAQ

No. It detects and reports missing or mismatched dependencies and can generate fix scripts; it does not install packages itself (except when you run generated fix scripts manually).

Does it support Windows and macOS?

Yes. Binary, version, and font checks work cross-platform. Native shared-library inspections are Linux-focused; Playwright runtime probes are supported via --probe on all platforms.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational