The description lists a concrete action: 'Check if a specific dependency has known vulnerabilities or malware using Endor Labs.' It clearly specifies the tool (Endor Labs), the target (a specific dependency/package), and what it checks for (vulnerabilities, malware).

Clearly answers both 'what' (check a specific dependency for vulnerabilities/malware using Endor Labs) and 'when' (explicit 'Use when...' clause with multiple trigger scenarios). Additionally includes negative boundaries ('Do NOT use for...') which further clarifies scope.

Excellent coverage of natural trigger terms: 'check lodash', 'is express vulnerable', 'any CVEs in django', 'endor check', 'is this package safe', 'package name', 'dependency'. These are phrases users would naturally say when wanting to check a package's safety.

Highly distinctive with explicit negative boundaries distinguishing it from related skills (/endor-scan for repo scanning, /endor-findings for viewing findings). The focus on single-package vulnerability checking creates a clear, non-overlapping niche.

The content is lean and well-structured. Every section serves a purpose—input parsing, ecosystem mapping, workflow steps, output templates, and error handling. No unnecessary explanations of what vulnerabilities are or how MCP tools work.

Provides specific MCP tool names (`check_dependency_for_risks`, `check_dependency_for_vulnerabilities`), exact parameter names, concrete output templates with markdown formatting, and a clear error handling table with specific actions. The ecosystem mapping table is immediately usable.

Clear two-step workflow with a preferred/fallback pattern for the check step. The output formatting is explicitly templated for both positive and negative results. Error handling covers key failure modes with specific recovery actions. The workflow is simple enough that validation checkpoints aren't needed—it's a read-only check operation.

References `references/install-commands.md` and `references/data-sources.md` which shows good intent for progressive disclosure, but no bundle files are provided to verify these exist. The main content is well-organized with clear sections, but the inline output templates are somewhat lengthy and could potentially be referenced externally.