Common Step: Generate Report File
SkillFiles & storageUse when writing markdown investigation or incident reports to standard
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Common Step: Generate Report File skill
What this skill tells your AI
The instructions your AI receives, as published by dandye/adk_runbooks in skills/common/generate-report-file/SKILL.md and read by ahel’s review.
Objective
Save generated report content (typically Markdown) to a file with a standardized naming convention.
Scope
This sub-runbook executes the write_report action. It assumes the report content and report name are provided by the calling runbook.
Inputs
${REPORT_CONTENTS}: The full content of the report (usually Markdown text).${REPORT_NAME}: The desired name for the report file (e.g., "ioc_investigation_report_case123_20250519.md"). The.mdextension will be added by the tool if not present. The report will be saved in a defaultreports/directory.
Outputs
${REPORT_FILE_PATH}: The full path to the saved report file.${WRITE_STATUS}: Confirmation or status of the file writing attempt.
Tools
write_report
Workflow Steps & Diagram
- Receive Input: Obtain
${REPORT_CONTENTS}and${REPORT_NAME}from the calling runbook. - Prepare Report Details:
- The
${REPORT_NAME}is provided directly. - The
${REPORT_CONTENTS}is provided directly.
- The
- Write Report: Call
write_reportwithreport_name=${REPORT_NAME}andreport_contents=${REPORT_CONTENTS}. The tool will handle saving this to a predefined reports directory (e.g.reports/) and adding a.mdextension if needed. - Return Status: Store the result/status of the write operation in
${WRITE_STATUS}and the actual file path (returned bywrite_report) in${REPORT_FILE_PATH}. Return${REPORT_FILE_PATH}and${WRITE_STATUS}to the calling runbook.
sequenceDiagram
participant CallingRunbook
participant GenerateReportFile as generate_report_file.md (This Runbook)
CallingRunbook->>GenerateReportFile: Execute Report Generation\nInput: REPORT_CONTENTS, REPORT_NAME
%% Step 2: Prepare Report Details
Note over GenerateReportFile: REPORT_NAME and REPORT_CONTENTS are provided
%% Step 3: Write Report
GenerateReportFile->>GenerateReportFile: write_report(report_name=REPORT_NAME, report_contents=REPORT_CONTENTS)
Note over GenerateReportFile: Store write status (WRITE_STATUS) and returned REPORT_FILE_PATH
%% Step 4: Return Status
GenerateReportFile-->>CallingRunbook: Return Results:\nREPORT_FILE_PATH,\nWRITE_STATUS
Completion Criteria
The write_report action has been attempted. The status (${WRITE_STATUS}) and the actual file path (${REPORT_FILE_PATH}) are available.
Signals
- GitHub stars
- 84
- Forks
- 14
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
generate-report-file- Source
- github.com/dandye/adk_runbooks