| name | dependency-vulnerability-check-manus-familytools-fullinstr-v2-skill |
| description | Family-scoped SkillLearnBench skill for dependency-vulnerability-check using latest full-instruction v2 family injection. |
| allowed-tools | ["list_dir","npm_vulnerability_audit","parse_package_lock","read_file","run_python","run_shell","search_text","vulnerability_db_lookup","write_file","write_table"] |
| metadata | {"benchmark":"SkillLearnBench","generator":"Manus","baseline":"manus_familytools_fullinstr_v2","generation_constraints":"slb_no_instance_memory_familytools_v2","allowed_gold_input":"familytools_full_instruction_v2","skill_injection_scope":"family_scoped","date":"2026-05-23"} |
Skill: Dependency Vulnerability Check
When to use this skill
Use this skill for the dependency-vulnerability-check family to perform security audits on dependency files (e.g., package-lock.json). It guides parsing lockfiles, querying vulnerability metadata, filtering by severity/CVSS policies, and writing structured CSV audit reports.
Visible input and artifact inventory
- Input: Dependency file at
/root/package-lock.json and instruction file detailing severity/CVSS thresholds.
- Output: CSV artifact at
/root/security_audit.csv with columns: Package, Version, CVE_ID, Severity, CVSS_Score, Fixed_Version, Title, Url.
Execution procedure for the current task
- Read Instructions: Extract target severity levels (e.g., HIGH/CRITICAL) or CVSS thresholds (e.g., > 8.0) from visible instructions.
- Parse Lockfile: Extract installed packages and versions from
/root/package-lock.json.
- Query Metadata: Retrieve CVE IDs, severities, CVSS scores, fixed versions, titles, and URLs for each package.
- Filter: Keep only vulnerabilities meeting the requested severity/CVSS criteria.
- Generate Report: Write the filtered data to
/root/security_audit.csv using the exact required columns.
Family tool routing and useful placeholder snippets
parse_package_lock: Extract package names/versions.npm_vulnerability_audit: Audit npm dependencies.vulnerability_db_lookup: Query CVE details and fixed versions.write_table: Write the final CSV report.
Validation checks before final submission
- Verify
/root/security_audit.csv exists.
- Check exact column headers:
Package,Version,CVE_ID,Severity,CVSS_Score,Fixed_Version,Title,Url.
- Ensure data strictly matches filtering criteria (e.g., only HIGH/CRITICAL).
- Confirm
Fixed_Version is "N/A" if unavailable.
Common failure modes and repair actions
- Missing File: Verify write path is exactly
/root/security_audit.csv.
- Schema Mismatch: Fix column names/order to match instructions.
- Bad Filtering: Adjust logic to strictly enforce severity/CVSS thresholds.
Finalizer capsule
If nearing max steps, create /root/security_audit.csv with the exact required column headers, even if empty, to satisfy minimum artifact shape checks.
