track-findings Skill
Track validated Codex Security findings in Linear, Jira, GitHub issues, or draft GitHub security advisories. Supports issue batches, duplicate checks, and reviewed writes. Do not use for scans or fixes. Published by openai in plugins.
Decision snapshot
Is this a fit?
Browser automation, Security review, Writing, Research
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
23 days ago
No specific cautions were detected. Review the source and requested permissions before installing.
What is track-findings Skill?
Track validated Codex Security findings in Linear, Jira, GitHub issues, or draft GitHub security advisories. Supports issue batches, duplicate checks, and reviewed writes. Do not use for scans or fixes. 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. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Browser automation
- Security review
- Writing
- Research
- Browser automation use cases
Declared skill metadata
- Source file: plugins/codex-security/skills/track-findings/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use track-findings Skill
- Use it for browser automation.
- Use it for security review.
- Use it for writing.
- Use it for research.
Built with
Editorial notes
Source
- Creator: openai
- Repository: openai/plugins
- Skill file: plugins/codex-security/skills/track-findings/SKILL.md
What it does
Track validated Codex Security findings in Linear, Jira, GitHub issues, or draft GitHub security advisories. Supports issue batches, duplicate checks, and reviewed writes. Do not use for scans or fixes.
Skill instructions
Track findings Track findings from one sealed scan in one provider and destination. Keep the scan bundle unchanged. Preview the exact payload and get approval before writing. Use the native Linear, Atlassian, or GitHub app. Read references/jira.md before Jira work and references/github-security-advisories.md before advisory work. GitHub CLI (gh) is also supported when the user selects its active account and exact destination; it is required for advisories. If an app cannot reach the destination, validate the source, show the CLI account, hostname, repository, and visibility, and ask to use them unless already selected. Never switch transports or accounts silently. Do not substitute browser automation, copied search results, or direct HTTP calls. 1. Validate the source Before provider calls or destination discovery, run the helper at the plugin root, two directories above this skill: text <pythoncommand <plugin-root/scripts/validatetrackingsource.py <user-supplied-scan-dir [--finding-id
Verified compatibility and discovery
Frequently asked questions
What is track-findings?
track-findings is a open-source AI agent skill with Copy skill directory. Track validated Codex Security findings in Linear, Jira, GitHub issues, or draft GitHub security advisories. Supports issue batches, duplicate checks, and reviewed writes. Do not use for scans or fixes.
Who is track-findings best for?
track-findings is best for reusing agent instructions, scripts, and references, browser automation workflows, security review workflows, writing workflows.
How do I install track-findings?
Install or run track-findings using Copy skill directory. Check track-findings for the latest setup command.
Is track-findings actively maintained?
track-findings may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
