fix: remove duplicated Automate This content, link back to examples page

The Automate This sections were duplicating the prompt already defined
in frontmatter. Now use-case pages just have a simple card linking back
to the automation examples page (with an anchor to the specific use
case). The prompt content lives in one place only — the frontmatter —
and the sync script copies it to examples.mdx.

- Remove generated Automate This blocks and markers from use-case pages
- Replace with a static Card linking to examples page anchor
- Remove unused intro field from frontmatter
- Simplify sync script to only generate the examples page

Co-authored-by: openhands <openhands@all-hands.dev>

Author: openhands-agent

.github/scripts/sync_use_case_automations.py

@@ -4,24 +4,19 @@
 
 Each use-case page under ``openhands/usage/use-cases/`` is the **source of
 truth**.  If a page's YAML frontmatter contains an ``automation:`` block, the
-script treats it as an automation-enabled use case and:
+script copies that content into the "Use Case Automations" section of
+``openhands/usage/automations/examples.mdx``.
 
-1. Generates the "Use Case Automations" card grid + Tabs section in
-   ``openhands/usage/automations/examples.mdx`` (between markers).
-2. Generates the "Automate This" section in the use-case page itself
-   (between markers).
-
-Marker format (JSX comments, ignored by Mintlify):
+The generated section lives between marker comments in examples.mdx:
   {/* BEGIN:use-case-automations */}  …  {/* END:use-case-automations */}
-  {/* BEGIN:automate-this */}          …  {/* END:automate-this */}
 
 Usage:
   python .github/scripts/sync_use_case_automations.py          # write mode
   python .github/scripts/sync_use_case_automations.py --check  # CI check
 
 Exit codes:
-  0 — all files are in sync (or were updated in write mode)
-  1 — files are out of sync (check mode)
+  0 — examples page is in sync (or was updated in write mode)
+  1 — examples page is out of sync (check mode)
 """
 
 from __future__ import annotations
@@ -38,14 +33,12 @@
 EXAMPLES_PAGE = REPO_ROOT / "openhands" / "usage" / "automations" / "examples.mdx"
 USE_CASES_DIR = REPO_ROOT / "openhands" / "usage" / "use-cases"
 
-# Frontmatter delimiters
 FRONTMATTER_RE = re.compile(r"\A---\n(.*?)\n---", re.DOTALL)
 
 
 # ── Frontmatter parsing ──────────────────────────────────────────────
 
 def parse_frontmatter(text: str) -> dict:
-    """Extract YAML frontmatter from an MDX file."""
     m = FRONTMATTER_RE.match(text)
     if not m:
         return {}
@@ -64,7 +57,7 @@ def collect_use_cases() -> list[tuple[str, dict]]:
     return results
 
 
-# ── Generators ────────────────────────────────────────────────────────
+# ── Generator ─────────────────────────────────────────────────────────
 
 def _indent(text: str, n: int = 4) -> str:
     return textwrap.indent(text, " " * n)
@@ -119,26 +112,6 @@ def generate_examples_section(use_cases: list[tuple[str, dict]]) -> str:
     return "\n".join(parts)
 
 
-def generate_automate_this(auto: dict) -> str:
-    """Generate the ``automate-this`` block for a single use-case page."""
-    prompt = auto["prompt"].rstrip("\n")
-    return (
-        f"## Automate This\n"
-        f"\n"
-        f'{auto["intro"]}\n'
-        f"\n"
-        f"```\n"
-        f"{prompt}\n"
-        f"```\n"
-        f"\n"
-        f'<Card title="More Automation Templates" icon="clock" '
-        f'href="/openhands/usage/automations/examples">\n'
-        f"  Browse all automation examples, including vulnerability scanning, "
-        f"code review, monitoring, and more.\n"
-        f"</Card>"
-    )
-
-
 # ── Marker replacement ───────────────────────────────────────────────
 
 def replace_marker_section(content: str, marker: str, new_body: str) -> str:
@@ -185,50 +158,26 @@ def main() -> int:
         print("No use-case pages with automation frontmatter found.")
         return 0
 
-    diffs: list[str] = []
-
-    # 1. Regenerate the examples page card section
     original = EXAMPLES_PAGE.read_text()
     generated = generate_examples_section(use_cases)
     updated = replace_marker_section(original, "use-case-automations", generated)
 
-    if updated != original:
-        diffs.append(str(EXAMPLES_PAGE.relative_to(REPO_ROOT)))
-        if not args.check:
-            EXAMPLES_PAGE.write_text(updated)
-            print(f"  ✏️  Updated {EXAMPLES_PAGE.relative_to(REPO_ROOT)}")
+    if updated == original:
+        print("✅  Automation examples page is in sync.")
+        return 0
 
-    # 2. Regenerate the "Automate This" section in each use-case page
-    for slug, auto in use_cases:
-        page = USE_CASES_DIR / f"{slug}.mdx"
-        original = page.read_text()
-        generated = generate_automate_this(auto)
-        updated = replace_marker_section(original, "automate-this", generated)
-
-        if updated != original:
-            rel = str(page.relative_to(REPO_ROOT))
-            diffs.append(rel)
-            if not args.check:
-                page.write_text(updated)
-                print(f"  ✏️  Updated {rel}")
-
-    if diffs:
-        if args.check:
-            print(
-                "\n❌  The automation examples page is out of sync with "
-                "use-case frontmatter:"
-            )
-            for d in diffs:
-                print(f"     - {d}")
-            print(
-                "\nRun:  python .github/scripts/sync_use_case_automations.py\n"
-                "Then commit the updated files."
-            )
-            return 1
-        print(f"\n✅  Updated {len(diffs)} file(s).")
-    else:
-        print("✅  All files are in sync.")
+    if args.check:
+        print(
+            "❌  openhands/usage/automations/examples.mdx is out of sync "
+            "with use-case frontmatter.\n"
+            "\n"
+            "Run:  python .github/scripts/sync_use_case_automations.py\n"
+            "Then commit the updated file."
+        )
+        return 1
 
+    EXAMPLES_PAGE.write_text(updated)
+    print(f"✅  Updated {EXAMPLES_PAGE.relative_to(REPO_ROOT)}")
     return 0
 
 

openhands/usage/use-cases/code-review.mdx

@@ -7,9 +7,6 @@ automation:
   card_description: >-
     Review PRs automatically on every push. Pairs with the
     [pr-review plugin](https://github.com/OpenHands/extensions/tree/main/plugins/pr-review).
-  intro: >-
-    Schedule daily code reviews with an OpenHands automation.
-    Copy this prompt into a conversation:
   prompt: |
     Create an automation called "Daily Code Review" that runs every weekday at 9 AM.
 
@@ -287,27 +284,12 @@ See real automated reviews in action on the OpenHands Software Agent SDK reposit
   </Accordion>
 </AccordionGroup>
 
-{/* BEGIN:automate-this — auto-generated from frontmatter */}
-
 ## Automate This
 
-Schedule daily code reviews with an OpenHands automation. Copy this prompt into a conversation:
-
-```
-Create an automation called "Daily Code Review" that runs every weekday at 9 AM.
-
-It should:
-1. Find all open PRs that have no reviews yet
-2. For each PR, review the diff for bugs, style issues, and security concerns
-3. Post a summary of findings as a comment on each PR
-```
-
-<Card title="More Automation Templates" icon="clock" href="/openhands/usage/automations/examples">
-  Browse all automation examples, including vulnerability scanning, code review, monitoring, and more.
+<Card title="Code Review Automation" icon="clock" href="/openhands/usage/automations/examples#automated-code-review">
+  Run this use case as a scheduled automation — copy a ready-to-use prompt from the Automation Examples page.
 </Card>
 
-{/* END:automate-this */}
-
 ## Related Resources
 
 - [PR Review Workflow Reference](https://github.com/OpenHands/software-agent-sdk/tree/main/examples/03_github_workflows/02_pr_review) - Full workflow example and agent script

openhands/usage/use-cases/dependency-upgrades.mdx

@@ -6,9 +6,6 @@ automation:
   icon: arrow-up-right-dots
   card_description: >-
     Check for outdated packages weekly and report available updates.
-  intro: >-
-    Schedule weekly dependency checks with an OpenHands automation.
-    Copy this prompt into a conversation:
   prompt: |
     Create an automation called "Dependency Checker" that runs every Monday at 8 AM.
 
@@ -298,28 +295,12 @@ Create an upgrade plan that handles all these together,
 addressing breaking changes in the correct order.
 ```
 
-{/* BEGIN:automate-this — auto-generated from frontmatter */}
-
 ## Automate This
 
-Schedule weekly dependency checks with an OpenHands automation. Copy this prompt into a conversation:
-
-```
-Create an automation called "Dependency Checker" that runs every Monday at 8 AM.
-
-It should:
-1. Scan all package.json and requirements.txt files
-2. Check for outdated dependencies
-3. Create a report listing packages with available updates (grouped by major/minor/patch)
-4. Post the report to #engineering
-```
-
-<Card title="More Automation Templates" icon="clock" href="/openhands/usage/automations/examples">
-  Browse all automation examples, including vulnerability scanning, code review, monitoring, and more.
+<Card title="Dependency Upgrades Automation" icon="clock" href="/openhands/usage/automations/examples#dependency-upgrades">
+  Run this use case as a scheduled automation — copy a ready-to-use prompt from the Automation Examples page.
 </Card>
 
-{/* END:automate-this */}
-
 ## Related Resources
 
 - [Vulnerability Remediation](/openhands/usage/use-cases/vulnerability-remediation) - Fix security vulnerabilities

openhands/usage/use-cases/incident-triage.mdx

@@ -7,9 +7,6 @@ automation:
   card_description: >-
     Monitor APIs, analyze errors, and alert your team. Pairs with the
     [Datadog debugging workflow](https://github.com/OpenHands/software-agent-sdk/tree/main/examples/03_github_workflows/04_datadog_debugging).
-  intro: >-
-    Set up continuous health monitoring with an OpenHands automation.
-    Copy this prompt into a conversation:
   prompt: |
     Create an automation called "API Health Monitor" that runs every 30 minutes.
 
@@ -277,26 +274,12 @@ Avoid these common incident response mistakes:
 For production incidents, always follow your organization's incident response procedures. OpenHands is a tool to assist your investigation, not a replacement for proper incident management.
 </Note>
 
-{/* BEGIN:automate-this — auto-generated from frontmatter */}
-
 ## Automate This
 
-Set up continuous health monitoring with an OpenHands automation. Copy this prompt into a conversation:
-
-```
-Create an automation called "API Health Monitor" that runs every 30 minutes.
-
-It should check https://api.example.com/health and:
-- If the response is not 200 OK, send an alert to #alerts with the status code and response body
-- If healthy, just log success without alerting anyone
-```
-
-<Card title="More Automation Templates" icon="clock" href="/openhands/usage/automations/examples">
-  Browse all automation examples, including vulnerability scanning, code review, monitoring, and more.
+<Card title="Incident Monitoring Automation" icon="clock" href="/openhands/usage/automations/examples#incident-monitoring">
+  Run this use case as a scheduled automation — copy a ready-to-use prompt from the Automation Examples page.
 </Card>
 
-{/* END:automate-this */}
-
 ## Related Resources
 
 - [OpenHands SDK Repository](https://github.com/OpenHands/software-agent-sdk) - Build custom AI agents

openhands/usage/use-cases/vulnerability-remediation.mdx

@@ -7,9 +7,6 @@ automation:
   card_description: >-
     Scan dependencies for known CVEs and post a report. Pairs with the
     [vulnerability-remediation plugin](https://github.com/OpenHands/extensions/tree/main/plugins/vulnerability-remediation).
-  intro: >-
-    Run vulnerability scans on a schedule with an OpenHands automation.
-    Copy this prompt into a conversation:
   prompt: |
     Create an automation called "Security Scan" that runs daily at 3 AM.
 
@@ -299,29 +296,12 @@ To build your own vulnerability remediation agent:
 
 As agent capabilities continue to evolve, an increasing number of repetitive and time-consuming security tasks can be automated, enabling developers to focus on higher-level design, innovation, and problem-solving rather than routine maintenance.
 
-{/* BEGIN:automate-this — auto-generated from frontmatter */}
-
 ## Automate This
 
-Run vulnerability scans on a schedule with an OpenHands automation. Copy this prompt into a conversation:
-
-```
-Create an automation called "Security Scan" that runs daily at 3 AM.
-
-It should run a security audit:
-1. Check for known vulnerabilities in dependencies
-2. Scan for hardcoded secrets or API keys
-3. Look for common security misconfigurations
-
-Create a detailed report and alert #security if any high or critical issues are found.
-```
-
-<Card title="More Automation Templates" icon="clock" href="/openhands/usage/automations/examples">
-  Browse all automation examples, including vulnerability scanning, code review, monitoring, and more.
+<Card title="Vulnerability Scan Automation" icon="clock" href="/openhands/usage/automations/examples#vulnerability-scan">
+  Run this use case as a scheduled automation — copy a ready-to-use prompt from the Automation Examples page.
 </Card>
 
-{/* END:automate-this */}
-
 ## Related Resources
 
 - [Vulnerability Fixer Example](https://github.com/OpenHands/vulnerability-fixer) - Full implementation example