Installs into .claude/skills of the current project.
Are you the author of Vcp Dependency Check?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/z-m-huang-vcp-dependency-check)
---
name: vcp-dependency-check
description: >
Verify project dependencies against VCP dependency management standards.
Checks lockfile hygiene, version ranges, package existence, and suspicious packages.
user-invocable: true
allowed-tools: Read, Glob, Grep, Bash, WebFetch
argument-hint: ""
---
# VCP Dependency Check
This skill is a thin slash-command launcher. The authoritative workflow lives in the VCP MCP prompt `vcp_dependency_check` and resource `vcp://prompts/vcp-dependency-check`.
1. Fetch the MCP prompt `vcp_dependency_check` with the caller-supplied host, current project path, and raw command arguments.
2. If MCP prompts are not directly available, call VCP MCP tool `get_prompt({ command: "vcp-dependency-check", host, project_path, arguments })` and follow the returned prompt text.
3. The returned prompt may instruct you to call VCP MCP tools such as `detect_installation`, `validate_plugin_root`, or `resolve_config`. Use those tools for deterministic work.
4. If the VCP MCP server is unavailable, stop and tell the user to enable the VCP MCP server for this plugin.
Do not reimplement the workflow in this file; update the MCP prompt instead.
