result-with-file

Aggregate security analysis results into a hierarchical Markdown report with evidence and fid anchors.

83|8|Updated May 6, 2026
One-click install
npx skills add https://github.com/Q16G/aster --skill result-with-file
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: result-with-file
Source: https://github.com/Q16G/aster/tree/main/skills/common/result-with-file
Command: npx skills add https://github.com/Q16G/aster --skill result-with-file

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

将安全分析/测试结果持久化为按入口点/主题组织的分级 Markdown 报告,内嵌 POC

Core Features & Use Cases

  • 将各子报告的分析结果整理为可追溯的、按入口点与主题分组的分级 Markdown 报告,保留完整证据与明细。
  • 支持嵌入 PoC,便于复现和验证;方便审计、合规和后续修复跟踪。
  • 提供统一的输出入口,将多源分析整合为单一、可检索的报告体。

Quick Start

直接将完成的分析结果输出为一个包含所有证据和 fid 锚点的单一 Markdown 报告。

Frequently Asked Questions about result-with-file

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

FAQPage Schema
How do I generate a hierarchical Markdown report for security audit trails?

Generating a hierarchical Markdown report for security audit trails involves aggregating multiple analysis sources into a single document organized by entry points and themes, preserving full evidence and fid anchors for traceability.

What is the best way to embed PoC in a compliance evidence report?

Embedding PoC in a compliance evidence report requires persisting security analysis results as a hierarchical Markdown document that directly integrates proof of concept snippets alongside detailed evidence for reproduction and verification.

Can I aggregate multiple security analysis results into a single traceable document?

Aggregating multiple security analysis results into a single traceable document is possible by unifying multi-source post-analysis outputs into one searchable Markdown report body that maintains complete details and structural anchors.

Does this Markdown reporting approach support post-mortem investigations across multiple entry points?

This Markdown reporting approach supports post-mortem investigations by grouping security findings hierarchically across multiple entry points and themes, ensuring complete evidence and traceability anchors are retained for comprehensive review.

How do I maintain traceability anchors when persisting security analysis findings?

Maintaining traceability anchors when persisting security analysis findings requires outputting results into a hierarchical Markdown report that explicitly preserves fid anchors, linking summary findings back to the original detailed evidence.