output

To format AWS security audit results, this skill structures raw query outputs into a two-phase response with an audit trail and a clean manager-readable results section. It enforces mandatory separators and standardizes findings, impact, recommendations, and confidence fields for easy scanning.

To ensure complete resource enumeration across multi-account AWS queries, this skill applies strict activation rules that prevent partial answers. It requires full resource listing within the structured output and omits inactive sections to keep the evidence reporting concise and accurate.

To structure evidence and risk scoring for policy validation findings, this skill ties claims to concrete command evidence. It enforces deterministic, evidence-first presentation by requiring severity confirmation and confidence fields alongside structured findings for all policy and configuration workflows.

Yes, this output formatting approach works for compound AWS security queries. It applies consistent two-phase response formatting across inventory, external probe, policy, configuration, compound, and general question workflows in both single- and multi-account modes.

Your AWS security audit response lacks clear separation because it misses mandatory separators. This skill enforces a strict two-phase structure, showing full CLI command outputs inline for the audit trail, then presenting clean results after a mandatory separator.

Yes, you can use this structured output formatter for single-account AWS security checks. It handles both single- and multi-account modes, applying consistent two-phase response rules and structured findings to ensure manager-readable results regardless of account scope.