deadangle

Validate and label security findings as confirmed, inferred, or assumed.

30|6|Updated May 13, 2026
One-click install
npx skills add https://github.com/Rifteo/skills --skill deadangle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deadangle
Source: https://github.com/Rifteo/skills/tree/main/deadangle
Command: npx skills add https://github.com/Rifteo/skills --skill deadangle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the problem of incomplete and unverified security findings in offensive security work by providing a final accuracy check before findings are delivered.

Core Features & Use Cases

  • Confidence Labeling: Ensures each conclusion is labeled as confirmed, inferred, or assumed based on evidence.
  • Selective Assumption Audit: Targets only uncertain elements and labels them honestly.
  • Position Shift: Offers different perspectives to re-examine findings and conclusions.
  • Chain Stress Test: Assesses the viability of multi-step attack paths.
  • Confidence Calibration: Provides honest labels to conclusions before delivery.

Quick Start

Run 'deadangle' to apply a final accuracy check to your security findings.

Frequently Asked Questions about deadangle

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

FAQPage Schema
How do I verify security findings for accuracy before delivery?

You can verify security findings by applying a structured confidence labeling process that categorizes each conclusion as confirmed, inferred, or assumed based on available evidence. This ensures accuracy and completeness in offensive security reporting.

What is confidence labeling in offensive security reports?

Confidence labeling is the process of tagging security findings as confirmed, inferred, or assumed to honestly represent the evidence supporting each conclusion. It targets uncertain elements to ensure conclusions are accurately portrayed before delivery.

How do I assess the viability of multi-step attack paths?

You can assess multi-step attack paths by applying a chain stress test, which evaluates the viability of each step in the attack sequence. This structured verification ensures complex offensive security findings are reliable before reporting.

Can I audit assumptions in my security findings without checking everything?

Yes, you can perform a selective assumption audit that targets only uncertain elements within your security findings. This allows you to honestly label inferred or assumed conclusions without needing to re-verify every confirmed detail.

What is the best way to re-examine security conclusions from different perspectives?

To re-examine security conclusions, you can apply a position shift technique that offers different analytical perspectives on your findings. This structured approach helps identify inaccuracies and ensures offensive security work maintains high precision before delivery.

Does this structured verification approach work for all offensive security engagements?

This structured verification is designed for offensive security engagements requiring precision in reporting findings. It requires careful reasoning and analysis of evidence to accurately label conclusions as confirmed, inferred, or assumed before final delivery.