add skills for report-tool

skills/android-automation/SKILL.md

@@ -152,6 +152,17 @@ The same `locate` JSON shape also works for other commands that accept a `locate
 npx @midscene/android@1 disconnect
 ```
 
+### Consume Report Files
+
+The generated HTML report is recommended for human reading first. It includes step-by-step execution details and replay videos for each operation, which makes it much easier to understand what happened and troubleshoot problems.
+
+If another skill or tool needs to consume the report, first convert it with `report-tool` from the same platform CLI package. Prefer Markdown for LLM-based workflows. Use JSON when the report needs to be processed programmatically.
+
+```bash
+npx @midscene/android@1 report-tool --action to-markdown --htmlPath ./midscene_run/report/.../index.html --outputDir ./output-markdown
+npx @midscene/android@1 report-tool --action split --htmlPath ./midscene_run/report/.../index.html --outputDir ./output-data
+```
+
 ## Workflow Pattern
 
 Since CLI commands are stateless between invocations, follow this pattern:

skills/browser/SKILL.md

@@ -220,6 +220,18 @@ Close the browser completely when finished (Puppeteer mode only):
 npx @midscene/web@1 close
 ```
 
+
+### Consume Report Files
+
+The generated HTML report is recommended for human reading first. It includes step-by-step execution details and replay videos for each operation, which makes it much easier to understand what happened and troubleshoot problems.
+
+If another skill or tool needs to consume the report, first convert it with `report-tool` from the same platform CLI package. Prefer Markdown for LLM-based workflows. Use JSON when the report needs to be processed programmatically.
+
+```bash
+npx @midscene/web@1 report-tool --action to-markdown --htmlPath ./midscene_run/report/.../index.html --outputDir ./output-markdown
+npx @midscene/web@1 report-tool --action split --htmlPath ./midscene_run/report/.../index.html --outputDir ./output-data
+```
+
 ## Workflow Pattern
 
 The browser **persists across CLI calls** via a background Chrome process. Follow this pattern:

skills/computer-automation/SKILL.md

@@ -140,6 +140,17 @@ The same `locate` JSON shape also works for other commands that accept a `locate
 npx @midscene/computer@1 disconnect
 ```
 
+### Consume Report Files
+
+The generated HTML report is recommended for human reading first. It includes step-by-step execution details and replay videos for each operation, which makes it much easier to understand what happened and troubleshoot problems.
+
+If another skill or tool needs to consume the report, first convert it with `report-tool` from the same platform CLI package. Prefer Markdown for LLM-based workflows. Use JSON when the report needs to be processed programmatically.
+
+```bash
+npx @midscene/computer@1 report-tool --action to-markdown --htmlPath ./midscene_run/report/.../index.html --outputDir ./output-markdown
+npx @midscene/computer@1 report-tool --action split --htmlPath ./midscene_run/report/.../index.html --outputDir ./output-data
+```
+
 ## Workflow Pattern
 
 Since CLI commands are stateless between invocations, follow this pattern:

skills/harmony-automation/SKILL.md

@@ -165,6 +165,17 @@ The same `locate` JSON shape also works for other commands that accept a `locate
 npx @midscene/harmony@1 disconnect
 ```
 
+### Consume Report Files
+
+The generated HTML report is recommended for human reading first. It includes step-by-step execution details and replay videos for each operation, which makes it much easier to understand what happened and troubleshoot problems.
+
+If another skill or tool needs to consume the report, first convert it with `report-tool` from the same platform CLI package. Prefer Markdown for LLM-based workflows. Use JSON when the report needs to be processed programmatically.
+
+```bash
+npx @midscene/harmony@1 report-tool --action to-markdown --htmlPath ./midscene_run/report/.../index.html --outputDir ./output-markdown
+npx @midscene/harmony@1 report-tool --action split --htmlPath ./midscene_run/report/.../index.html --outputDir ./output-data
+```
+
 ## Workflow Pattern
 
 Since CLI commands are stateless between invocations, follow this pattern:

skills/ios-automation/SKILL.md

@@ -144,6 +144,17 @@ The same `locate` JSON shape also works for other commands that accept a `locate
 npx @midscene/ios@1 disconnect
 ```
 
+### Consume Report Files
+
+The generated HTML report is recommended for human reading first. It includes step-by-step execution details and replay videos for each operation, which makes it much easier to understand what happened and troubleshoot problems.
+
+If another skill or tool needs to consume the report, first convert it with `report-tool` from the same platform CLI package. Prefer Markdown for LLM-based workflows. Use JSON when the report needs to be processed programmatically.
+
+```bash
+npx @midscene/ios@1 report-tool --action to-markdown --htmlPath ./midscene_run/report/.../index.html --outputDir ./output-markdown
+npx @midscene/ios@1 report-tool --action split --htmlPath ./midscene_run/report/.../index.html --outputDir ./output-data
+```
+
 ## Workflow Pattern
 
 Since CLI commands are stateless between invocations, follow this pattern: