triage-vulnerabilities

Aggregates and prioritizes CVEs from four sources for remediation planning.

37|1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/terzigolu/warp-lite --skill triage-vulnerabilities-terzigolu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-vulnerabilities
Source: https://github.com/terzigolu/warp-lite/tree/main/resources/channel-gated-skills/dogfood/triage-vulnerabilities
Command: npx skills add https://github.com/terzigolu/warp-lite --skill triage-vulnerabilities-terzigolu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage and remediate security vulnerabilities across Warp infrastructure. It aggregates Dependabot alerts (GitHub), GCP Artifact Registry scans, Docker Scout results, and Linear security issues to provide a unified view for faster, safer remediation.

Core Features & Use Cases

  • Multi-source vulnerability aggregation: collects open alerts and vulnerability reports from Dependabot, GCP Artifact Registry, Docker Scout, and Linear into a single view.
  • Deduplication and prioritization: groups the same CVE reported across sources and ranks by severity to guide remediation focus.
  • Remediation guidance and tracking: suggests upstream fixes, tracks PRs, and coordinates actions across production and staging environments.
  • Use Case: A security engineer wants to triage critical CVEs across Warp services and generate an actionable remediation plan.

Quick Start

Query all four sources to compile open vulnerabilities into a single prioritized backlog for remediation.

Frequently Asked Questions about triage-vulnerabilities

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I aggregate Dependabot alerts and Docker Scout vulnerabilities into a single backlog?

You can aggregate Dependabot alerts, Docker Scout results, GCP Artifact Registry scans, and Linear issues into a single prioritized backlog. This workflow collects open alerts from all four sources to provide a unified view for faster vulnerability remediation.

What is the best way to deduplicate CVEs reported across multiple security scanning tools?

Deduplicating CVEs across multiple scanning tools involves grouping identical vulnerabilities reported by Dependabot, GCP Artifact Registry, and Docker Scout. This process ranks duplicates by severity to guide remediation focus and eliminate redundant alerts across infrastructure environments.

Can I track vulnerability remediation across both production and staging environments?

Yes, you can track vulnerability remediation across production and staging environments. The workflow coordinates actions, suggests upstream fixes, and tracks pull requests to ensure safe remediation across different infrastructure deployment targets.

How do I generate a remediation plan for critical CVEs found in GCP Artifact Registry?

Generating a remediation plan for critical CVEs involves querying GCP Artifact Registry scans, prioritizing by severity, and suggesting upstream fixes. The workflow guides PR creation and coordinates tracking through Linear issues to resolve vulnerabilities.

Do I need to manually check Linear issues if I am already using Dependabot for vulnerability alerts?

Checking Linear issues alongside Dependabot alerts provides a complete vulnerability picture. Aggregating both sources ensures no security issues are missed, as Linear may contain tracked vulnerabilities or remediation tasks not captured by automated dependency scanning.

What limitations exist when triaging vulnerabilities from Docker Scout and GCP Artifact Registry simultaneously?

Triage limitations depend on the scan coverage and reporting frequency of Docker Scout and GCP Artifact Registry. If either tool lacks recent scan data or fails to report specific CVEs, the aggregated backlog may miss vulnerabilities not detected by the upstream scanning tools.