Minimal portable file
---
name: dependency-review
description: Review dependency changes for provenance and risk. Use when manifests or lockfiles change.
---
# Workflow
1. Read the changed dependency entries.
2. Verify source, version, and install scripts.
3. Report findings with file paths.Name
Use a concise lowercase identifier with digits and hyphens. Keep the directory name aligned with the skill name when the target ecosystem requires it.
Description
The description is activation metadata. State both capability and trigger: what the skill does, what output it produces, and the user situations that should select it.
Optional fields
License, compatibility, metadata, and allowed tools vary across hosts. Treat product-specific fields as compatibility decisions and test every target agent.
Package validation needs the whole directory. A pasted SKILL.md cannot prove that relative links resolve or that scripts and assets are benign.