skills.rest
RideMatch1
RideMatch1COMMUNITY
Explore all skills by this author →
GitHub

ops-triage-aegis-finding

Standardize severity, verification, and routing decisions for AEGIS findings.

Updated Aug 23, 2026
Search Tags:#workflow#security#triage#severity#findings#aegis
One-click install
npx skills add https://github.com/RideMatch1/a.e.g.i.s --skill ops-triage-aegis-finding
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ops-triage-aegis-finding
Source: https://github.com/RideMatch1/a.e.g.i.s/tree/main/packages/skills/skills/ops/aegis-native/triage-finding
Command: npx skills add https://github.com/RideMatch1/a.e.g.i.s --skill ops-triage-aegis-finding

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage consistency for AEGIS findings is achieved by standardizing severity, verification, and ownership decisions to accelerate risk response and reduce rework.

Core Features & Use Cases

  • Standardized severity handling (BLOCKER/HIGH/MEDIUM/LOW)
  • Verification steps and evidence gathering before decisions
  • Ownership routing and SLA guidance for timely remediation
  • Use cases include new findings from PRs, SARIF/code-scanning outputs, backlog reviews, and onboarding new teammates

Quick Start

Routinely apply the triage playbook to incoming AEGIS findings to determine fix, suppress, defer, or dispute actions.

Frequently Asked Questions about ops-triage-aegis-finding

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

FAQPage Schema
How do I triage security findings from SARIF and code-scanning output?▼

Triage security findings from SARIF and code-scanning output by standardizing severity levels, running verification drills, and applying fix-vs-suppress routing decisions. The process evaluates confidence and routes ownership to ensure timely remediation.

What is the standard severity classification for AEGIS findings?▼

Standard severity classification for AEGIS findings uses four levels: BLOCKER, HIGH, MEDIUM, and LOW. Categorizing findings by severity drives ownership routing and SLA defaults to accelerate risk response and reduce rework.

How do I verify security findings before deciding to fix or suppress?▼

Verify security findings before deciding to fix or suppress by executing verification steps and gathering evidence. This workflow requires confidence handling and verification drills to validate the finding before recording an inline fix, defer, or dispute decision.

Can I use this triage workflow for backlog reviews and onboarding new teammates?▼

Yes, you can use this triage workflow for backlog reviews and onboarding new teammates. The standardized playbook covers severity handling, verification, and ownership routing to ensure consistent triage decisions across both incoming PR comments and historical backlog items.

What are the default SLA and ownership routing rules for security findings?▼

Default SLA and ownership routing rules for security findings map severity levels to remediation timelines and assign ownership accordingly. The workflow records routing decisions inline to maintain accountability and ensure timely remediation across the team.

Related Skills

Explore More Software Engineering Skills→
SuperlendSuperlend

sarif-parsing

Parse SARIF 2.1.0 files and extract structured findings for reporting.

Official
Intermediate
saolalabsaolalab
37

vulnerability-management

Track security vulnerabilities with CVSS severity mapping and SLA-aligned remediation timelines.

Official
Intermediate
apacheapache
79

magpie-security-issue-import-from-scan

Import security scanner findings into Magpie for operator-reviewed triage.

Official
Advanced
dnvitidnviti
10

vulnerability-create

Generate structured remediation tasks from security vulnerability findings with severity classification.

Community
Intermediate