security-posture-analyzer

Analyze HTTP, DNS, HTML, and repository signals to produce prioritized security recommendations.

Updated May 27, 2026
One-click install
npx skills add https://github.com/hoanghn61/.agents --skill security-posture-analyzer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-posture-analyzer
Source: https://github.com/hoanghn61/.agents/tree/main/skills/techstack-identification/security_posture_analyzer
Command: npx skills add https://github.com/hoanghn61/.agents --skill security-posture-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps identify weaknesses in an organization’s web and email security posture by reviewing HTTP security headers, Content Security Policy behavior, HSTS configuration, DNS-based email authentication records, and common security-discovery endpoints.

Core Features & Use Cases

  • HTTP security header assessment: Detects presence and strength of key headers like HSTS, CSP, X-Frame-Options, X-Content-Type-Options, and Referrer-Policy to highlight missing protections and risky configurations.
  • Content Security Policy analysis: Evaluates CSP directives for unsafe allowances (such as unsafe-inline or unsafe-eval), derives third-party domains, and estimates overall CSP strength.
  • Email security DNS record review: Checks SPF, DKIM, and DMARC values to assess spoofing resistance and enforcement/reporting posture.
  • Security discovery file validation: Verifies availability and content signals of security.txt (and related paths) to ensure security contact and operational expectations are present.

Quick Start

Ask it to analyze your Phase 2 HTTP, DNS, HTML, and repository signals for missing or weak security headers, risky CSP directives, weak email authentication records, and absent security-discovery files.

Frequently Asked Questions about security-posture-analyzer

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

FAQPage Schema
How do I check HTTP security headers and CSP for risky configurations?

Analyze HTTP security headers and CSP by parsing raw http_signals to detect missing protections, unsafe-inline or unsafe-eval directives, and third-party domains. This process highlights risky configurations and estimates overall Content Security Policy strength.

How do I validate SPF, DKIM, and DMARC DNS records for email spoofing resistance?

Evaluate SPF, DKIM, and DMARC DNS records by parsing dns_signals to assess email spoofing resistance. This review checks enforcement and reporting posture, converting raw text records into actionable findings for email security.

What is a security.txt file and how do I verify its presence for security reviews?

A security.txt file provides security contact and operational expectations for vulnerability disclosure. Verify its availability and content signals by analyzing repository and html signals to ensure proper discovery endpoints are present during security reviews.

Can I use raw scanning outputs for continuous security monitoring?

Yes, you can use raw http_signals, dns_signals, html_signals, and repository_signals for continuous monitoring. The analysis converts these outputs into prioritized recommendations, tracking security posture changes across ongoing review scenarios.

What is the best way to audit HSTS and X-Frame-Options header strength?

Audit HSTS and X-Frame-Options by parsing http_signals to detect header presence and evaluate configuration strength. This identifies missing protections and risky settings, producing a prioritized report of header-level weaknesses.

What limitations exist when analyzing raw signals for security posture gaps?

Analysis requires pre-collected raw scanning outputs including http, dns, html, and repository signals. It focuses on parsing and scoring these specific inputs, meaning it cannot evaluate vulnerabilities outside the provided signal data.