@openhands/extensions 0.8.0 → 0.9.0

package/skills/datadog/references/windows.md

@@ -0,0 +1,45 @@
+# Windows Notes for Datadog Commands
+
+Use these PowerShell forms when running the Datadog examples natively on Windows.
+
+## Check Required Environment Variables
+
+```powershell
+foreach ($name in "DD_API_KEY", "DD_APP_KEY", "DD_SITE") {
+  if ([Environment]::GetEnvironmentVariable($name)) {
+    "$name is set"
+  } else {
+    "$name is NOT set"
+  }
+}
+```
+
+## Run the Curl Examples
+
+In PowerShell, call `curl.exe` so the examples use real curl rather than the `curl` alias. Replace `${DD_SITE}` with `$env:DD_SITE` and `${DD_API_KEY}` / `${DD_APP_KEY}` with `$env:DD_API_KEY` / `$env:DD_APP_KEY`.
+
+```powershell
+curl.exe -s -X POST "https://api.$env:DD_SITE/api/v2/logs/events/search" `
+  -H "DD-API-KEY: $env:DD_API_KEY" `
+  -H "DD-APPLICATION-KEY: $env:DD_APP_KEY" `
+  -H "Content-Type: application/json" `
+  -d '{"filter":{"query":"service:my-service status:error","from":"now-1h","to":"now"},"sort":"-timestamp","page":{"limit":50}}' |
+  ConvertFrom-Json
+```
+
+## Replace Linux Date and Jq
+
+The metrics example uses `date -d` and `jq`. In PowerShell, compute Unix timestamps with .NET and pipe JSON to `ConvertFrom-Json`.
+
+```powershell
+$from = [DateTimeOffset]::UtcNow.AddHours(-1).ToUnixTimeSeconds()
+$to = [DateTimeOffset]::UtcNow.ToUnixTimeSeconds()
+
+curl.exe -s -G "https://api.$env:DD_SITE/api/v1/query" `
+  -H "DD-API-KEY: $env:DD_API_KEY" `
+  -H "DD-APPLICATION-KEY: $env:DD_APP_KEY" `
+  --data-urlencode "query=avg:system.cpu.user{*}" `
+  --data-urlencode "from=$from" `
+  --data-urlencode "to=$to" |
+  ConvertFrom-Json
+```

package/skills/discord/SKILL.md

@@ -49,6 +49,8 @@ Use this skill when implementing or automating Discord integrations.
 
 ## Quick recipes
 
+The shell snippets below use POSIX-style environment variables and line continuations. On Windows PowerShell, use `curl.exe` for the shown flags and `$env:DISCORD_WEBHOOK_URL` / `$env:DISCORD_BOT_TOKEN` for environment variables, or translate the request to `Invoke-RestMethod`.
+
 ### Post a message via an incoming webhook (recommended)
 
 Discord requires at least one of `content`, `embeds`, `components`, `file`, or `poll`.

package/skills/docker/SKILL.md

@@ -20,10 +20,14 @@ sudo dockerd > /tmp/docker.log 2>&1 &
 sleep 5
 ```
 
+On Windows, start Docker Desktop or the Docker service instead of running `sudo dockerd`; then run Docker commands from PowerShell without `sudo`.
+
 ## Verifying Docker Installation
 
 To verify Docker is working correctly, run the hello-world container:
 
 ```bash
 sudo docker run hello-world
-```
+```
+
+PowerShell equivalent after Docker Desktop is running: `docker run hello-world`.

package/skills/github/SKILL.md

@@ -19,6 +19,8 @@ Examples:
 - `gh pr checks 200 --watch --interval 10` to check until completed.
 </IMPORTANT>
 
+Windows PowerShell equivalents for the multi-line shell snippets below are in `references/windows.md`.
+
 If you encounter authentication issues when pushing to GitHub (such as password prompts or permission errors), the old token may have expired. In such case, update the remote URL to include the current token: `git remote set-url origin https://${GITHUB_TOKEN}@github.com/username/repo.git`
 
 Here are some instructions for pushing, but ONLY do this if the user asks you to:
@@ -103,4 +105,4 @@ gh run list --repo <OWNER>/<REPO> --branch <BRANCH> --limit 5
 
 # Rerun failed jobs
 gh run rerun <RUN_ID> --repo <OWNER>/<REPO> --failed
-```
+```

package/skills/github/references/windows.md

@@ -0,0 +1,48 @@
+# Windows Notes for GitHub Commands
+
+Use these PowerShell forms when running this skill's GitHub commands natively on Windows.
+
+## Environment Variables
+
+PowerShell environment variables use `$env:NAME`:
+
+```powershell
+git remote set-url origin "https://$($env:GITHUB_TOKEN)@github.com/username/repo.git"
+```
+
+## Chained Git Commands
+
+If the installed shell does not support `&&`, run the commands separately and stop if one fails:
+
+```powershell
+git remote -v
+git branch
+git checkout -b create-widget
+git add .
+git commit -m "Create widget"
+git push -u origin create-widget
+```
+
+## GraphQL Requests with gh
+
+For multi-line GraphQL queries, use a PowerShell here-string and pass it to `gh api`.
+
+```powershell
+$query = @'
+{
+  repository(owner: "<OWNER>", name: "<REPO>") {
+    pullRequest(number: <PR_NUMBER>) {
+      reviewThreads(first: 20) {
+        nodes { id isResolved }
+      }
+    }
+  }
+}
+'@
+
+gh api graphql -f query="$query"
+```
+
+## Redirects
+
+Replace POSIX redirects such as `2>/dev/null` with PowerShell redirects such as `2>$null`.

package/skills/github-pr-review/SKILL.md

@@ -8,6 +8,7 @@ triggers:
 # GitHub PR Review
 
 Post structured code review feedback using the GitHub API with inline comments on specific lines.
+Windows PowerShell equivalents for JSON file creation, temp paths, line lookup, and fallback `curl` are in `references/windows.md`.
 
 ## Key Rule: One API Call
 

package/skills/github-pr-review/references/windows.md

@@ -0,0 +1,47 @@
+# Windows Notes for GitHub PR Review Commands
+
+Use these PowerShell forms for the JSON-file, line-check, and fallback API snippets.
+
+## Create the Review JSON File
+
+```powershell
+$reviewJson = Join-Path $env:TEMP "review.json"
+@'
+{
+  "commit_id": "{commit_sha}",
+  "event": "COMMENT",
+  "body": "Brief 1-3 sentence summary.",
+  "comments": []
+}
+'@ | Set-Content -LiteralPath $reviewJson -Encoding utf8
+```
+
+Then pass the file to `gh`:
+
+```powershell
+gh api -X POST repos/{owner}/{repo}/pulls/{pr_number}/reviews --input $reviewJson
+```
+
+## Verify File Lines
+
+Use `Select-String` for pattern lookup and `Get-Content` for exact ranges.
+
+```powershell
+Select-String -Path filename -Pattern "pattern"
+
+$lines = Get-Content -LiteralPath filename
+$lines[41]  # line 42, because arrays are zero-based
+$lines[($start - 1)..($end - 1)]
+```
+
+## Fallback Curl
+
+Use `curl.exe` so PowerShell does not resolve `curl` to its alias.
+
+```powershell
+curl.exe -X POST `
+  -H "Authorization: token $env:GITHUB_TOKEN" `
+  -H "Accept: application/vnd.github+json" `
+  "https://api.github.com/repos/{owner}/{repo}/pulls/{pr_number}/reviews" `
+  --data-binary "@$reviewJson"
+```

package/skills/github-pr-reviewer/SKILL.md

@@ -14,6 +14,7 @@ triggers:
 Create a cron automation that watches a GitHub repository for pull requests
 with a review trigger label, starts an OpenHands review conversation once per
 label event, and posts the AI review as a GitHub comment.
+Windows PowerShell equivalents for the setup, packaging, upload, and API-check shell snippets are in `references/windows.md`.
 
 The automation script is deterministic: PR discovery, label-event tracking,
 state persistence, stale-result suppression, and GitHub comment posting are

package/skills/github-pr-reviewer/references/windows.md

@@ -0,0 +1,61 @@
+# Windows Notes for GitHub PR Reviewer Setup
+
+Use these PowerShell forms when creating the reviewer automation from Windows.
+
+## Validate the GitHub Token
+
+```powershell
+Invoke-RestMethod `
+  -Uri "https://api.github.com/user" `
+  -Headers @{ Authorization = "Bearer $env:GITHUB_PERSONAL_ACCESS_TOKEN" }
+```
+
+## Build Directory and Syntax Check
+
+```powershell
+$buildDir = Join-Path $env:TEMP "pr-reviewer-build"
+New-Item -ItemType Directory -Force $buildDir | Out-Null
+# write the customised main.py to (Join-Path $buildDir "main.py")
+
+python -m py_compile (Join-Path $buildDir "main.py")
+if ($LASTEXITCODE -eq 0) { "Syntax OK" }
+```
+
+## Package and Upload
+
+Modern Windows includes `tar.exe`. Use it to create the `.tar.gz` expected by the automation API.
+
+```powershell
+$tarball = Join-Path $env:TEMP "pr-reviewer.tar.gz"
+tar.exe -czf $tarball -C $buildDir .
+
+$upload = curl.exe -s -X POST `
+  "$env:OPENHANDS_HOST/api/automation/v1/uploads?name=github-pr-reviewer" `
+  -H "X-Session-API-Key: $env:OPENHANDS_AUTOMATION_API_KEY" `
+  -H "Content-Type: application/gzip" `
+  --data-binary "@$tarball" | ConvertFrom-Json
+
+$tarballPath = $upload.tarball_path
+"Uploaded: $tarballPath"
+```
+
+## Register the Automation
+
+Use a double-quoted here-string when the body needs PowerShell variable interpolation.
+
+```powershell
+$body = @"
+{
+  "name": "GitHub PR Reviewer: {owner}/{repo}",
+  "trigger": {"type": "cron", "schedule": "{cron_schedule}"},
+  "tarball_path": "$tarballPath",
+  "entrypoint": "python3 main.py",
+  "timeout": 300
+}
+"@
+
+curl.exe -s -X POST "$env:OPENHANDS_HOST/api/automation/v1" `
+  -H "X-Session-API-Key: $env:OPENHANDS_AUTOMATION_API_KEY" `
+  -H "Content-Type: application/json" `
+  -d $body
+```

package/skills/github-repo-monitor/SKILL.md

@@ -16,6 +16,7 @@ triggers:
 
 Create a cron automation that polls a single GitHub repository on a
 configurable schedule (default: every minute).
+Windows PowerShell equivalents for the setup, packaging, upload, and API-check shell snippets are in `references/windows.md`.
 
 When a comment on an issue or PR contains the **trigger phrase**
 (default: `@OpenHands`) it:

package/skills/github-repo-monitor/references/windows.md

@@ -0,0 +1,61 @@
+# Windows Notes for GitHub Repository Monitor Setup
+
+Use these PowerShell forms when creating the monitor automation from Windows.
+
+## Validate the GitHub Token and Repo
+
+```powershell
+Invoke-RestMethod `
+  -Uri "https://api.github.com/user" `
+  -Headers @{ Authorization = "Bearer $env:GITHUB_PERSONAL_ACCESS_TOKEN"; Accept = "application/vnd.github+json" }
+
+Invoke-RestMethod `
+  -Uri "https://api.github.com/repos/{owner}/{repo}" `
+  -Headers @{ Authorization = "Bearer $env:GITHUB_PERSONAL_ACCESS_TOKEN"; Accept = "application/vnd.github+json" }
+```
+
+## Build Directory and Syntax Check
+
+```powershell
+$buildDir = Join-Path $env:TEMP "github-monitor-build"
+New-Item -ItemType Directory -Force $buildDir | Out-Null
+# write the customised main.py to (Join-Path $buildDir "main.py")
+
+python -m py_compile (Join-Path $buildDir "main.py")
+if ($LASTEXITCODE -eq 0) { "Syntax OK" }
+```
+
+## Package and Upload
+
+```powershell
+$tarball = Join-Path $env:TEMP "github-monitor.tar.gz"
+tar.exe -czf $tarball -C $buildDir .
+
+$upload = curl.exe -s -X POST `
+  "$env:OPENHANDS_HOST/api/automation/v1/uploads?name=github-repo-monitor" `
+  -H "X-Session-API-Key: $env:OPENHANDS_AUTOMATION_API_KEY" `
+  -H "Content-Type: application/gzip" `
+  --data-binary "@$tarball" | ConvertFrom-Json
+
+$tarballPath = $upload.tarball_path
+"Uploaded: $tarballPath"
+```
+
+## Create the Automation
+
+```powershell
+$body = @"
+{
+  "name": "GitHub Monitor: {owner}/{repo}",
+  "trigger": {"type": "cron", "schedule": "{cron_schedule}"},
+  "tarball_path": "$tarballPath",
+  "entrypoint": "python3 main.py",
+  "timeout": 55
+}
+"@
+
+curl.exe -s -X POST "$env:OPENHANDS_HOST/api/automation/v1" `
+  -H "X-Session-API-Key: $env:OPENHANDS_AUTOMATION_API_KEY" `
+  -H "Content-Type: application/json" `
+  -d $body
+```

package/skills/gitlab/SKILL.md

@@ -29,4 +29,6 @@ Here are some instructions for pushing, but ONLY do this if the user asks you to
 ```bash
 git remote -v && git branch # to find the current org, repo and branch
 git checkout -b create-widget && git add . && git commit -m "Create widget" && git push -u origin create-widget
-```
+```
+
+On Windows PowerShell, use `$env:GITLAB_TOKEN` in remote URLs and run the `git` commands as separate commands if `&&` is not supported by the installed shell.

package/skills/incident-retrospective/SKILL.md

@@ -85,6 +85,8 @@ curl -s -X POST "${OPENHANDS_HOST}/api/automation/v1/preset/prompt" \
   }'
 ```
 
+PowerShell note: use `curl.exe` for this exact flag syntax, and replace `${OPENHANDS_HOST}` / `$OPENHANDS_AUTOMATION_API_KEY` with `$env:OPENHANDS_HOST` / `$env:OPENHANDS_AUTOMATION_API_KEY` if running it natively.
+
 ### Step 5 — Confirm
 
 Tell the user: