triage-finding Skill
Use when the user supplies or imports existing security findings, vulnerability reports, or security/vulnerability Jira/Linear tickets from scanners, advisories, GitHub, Atlassian Rovo, Linear, or similar backlog sources and wants static repo-impact triage. Do not use for discovery, duplicate-bug triage, validation, or Published by openai in plugins.
What is triage-finding Skill?
Use when the user supplies or imports existing security findings, vulnerability reports, or security/vulnerability Jira/Linear tickets from scanners, advisories, GitHub, Atlassian Rovo, Linear, or similar backlog sources and wants static repo-impact triage. Do not use for discovery, duplicate-bug triage, validation, or Published by openai in plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Security review
- Security review use cases
Technical details
- Install or run with Copy skill directory
When to use triage-finding Skill
- Use it for security review.
Built with
Editorial notes
Source
- Creator: openai
- Repository: openai/plugins
- Skill file: plugins/codex-security/skills/triage-finding/SKILL.md
What it does
Use when the user supplies or imports existing security findings, vulnerability reports, or security/vulnerability Jira/Linear tickets from scanners, advisories, GitHub, Atlassian Rovo, Linear, or similar backlog sources and wants static repo-impact triage. Do not use for discovery, duplicate-bug triage, validation, or
Skill instructions
Triage Finding Objective Triage existing security findings against the current repository using static code evidence. Return one evidence-backed verdict per supplied finding: confirmed, notactionable, or needsreview. For confirmed and needsreview findings, also assign a discrete exploitability stack rank inside that verdict's own queue. This skill is for backlog burn-down. It starts from findings the user already has, such as SARIF results, CVEs, advisories, scanner tickets, bug bounty reports, Jira/Linear issues, or Codex Security finding artifacts. It is not a repository-wide scan, dynamic validation run, fix implementation, dashboard, or queue manager. Backlog Burn-Down Scope Treat multiple supplied findings as one backlog-reduction problem, not as a set of unrelated one-off triages. The goal is to turn noisy existing finding sources into a ranked, evidence-backed action queue while preserving one result per input for auditability and app rendering. For now, run the workflow inline
Explore related resources
Frequently asked questions
What is triage-finding?
triage-finding is a open-source AI agent skill with Copy skill directory. Use when the user supplies or imports existing security findings, vulnerability reports, or security/vulnerability Jira/Linear tickets from scanners, advisories, GitHub, Atlassian Rovo, Linear, or similar.
Who is triage-finding best for?
triage-finding is best for reusing agent instructions, scripts, and references, security review workflows.
How do I install triage-finding?
Install or run triage-finding using Copy skill directory. Check triage-finding for the latest setup command.
Is triage-finding actively maintained?
triage-finding may need a closer maintenance check before production use.
Auto-fetched from GitHub.
