skills.rest
iiammae
iiammaeCOMMUNITY
Explore all skills by this author →
GitHub

fp-check

Verify suspected security bugs and classify them as true or false positives.

Updated Jun 9, 2026
Search Tags:#code review#security analysis#false positive#security verification#bug elimination
One-click install
npx skills add https://github.com/iiammae/opero --skill fp-check-iiammae
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fp-check
Source: https://github.com/iiammae/opero/tree/main/.agents/skills/fp-check
Command: npx skills add https://github.com/iiammae/opero --skill fp-check-iiammae

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill systematically verifies suspected security bugs to eliminate false positives, providing TRUE POSITIVE or FALSE POSITIVE verdicts with documented evidence.

Core Features & Use Cases

  • False Positive Elimination: Provides a structured approach to verify and eliminate false positives in security bug analysis.
  • Custom Verification Paths: Offers both standard and deep verification paths to handle different complexity levels of bugs.
  • Documentation and Evidence: Generates detailed evidence and documentation for each verification step to ensure transparency and accountability.

Quick Start

To verify a suspected bug, activate the fp-check skill and follow the prompts to input the vulnerability details and context.

Frequently Asked Questions about fp-check

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

FAQPage Schema
How do I eliminate false positives in security bug verification?▼

You can eliminate false positives by using a structured verification process that systematically evaluates suspected vulnerabilities, providing documented TRUE POSITIVE or FALSE POSITIVE verdicts supported by detailed evidence.

What is the best way to document evidence during code review and security analysis?▼

Documenting evidence during security analysis requires generating detailed records for each verification step, ensuring transparency and accountability for both straightforward and complex bug verification scenarios.

How do I verify complex security bugs without skipping steps?▼

Verifying complex security bugs requires a deep verification path that handles different complexity levels, enforcing a structured verification process and detailed documentation to ensure accurate TRUE POSITIVE or FALSE POSITIVE outcomes.

Can I get a TRUE POSITIVE or FALSE POSITIVE verdict for straightforward security bugs?▼

Yes, you can obtain a TRUE POSITIVE or FALSE POSITIVE verdict for straightforward security bugs by using a standard verification path that systematically evaluates the suspected vulnerability and generates documented evidence.

Related Skills

Explore More Software Engineering Skills→
RedHatProductSecurityRedHatProductSecurity
47

fp-check

Guide security teams through data flow analysis and exploitability assessment for suspected security bugs.

Official
Intermediate
Ramprasad4121Ramprasad4121
1

fp-check

Verify suspected security bugs and produce documented TRUE POSITIVE or FALSE POSITIVE verdicts.

Community
Advanced
Ramprasad4121Ramprasad4121
1

audit-prep-assistant

Prepare codebases for security review with static analysis and documentation.

Community
Advanced
trailofbitstrailofbits
6.5k

fp-check

Verify suspected security bugs and classify them as true or false positives.

Official
Advanced