@openhands/extensions 0.0.1-alpha → 0.2.0

package/skills/slack-standup-digest/.plugin/plugin.json

@@ -0,0 +1,21 @@
+{
+  "name": "slack-standup-digest",
+  "version": "1.0.0",
+  "description": "Create an automation that generates an async standup digest from Slack. Searches selected channels for messages since the previous workday, groups updates by project, highlights blockers and decisions, and posts a summary to a target channel.",
+  "author": {
+    "name": "OpenHands",
+    "email": "contact@all-hands.dev"
+  },
+  "homepage": "https://github.com/OpenHands/extensions",
+  "repository": "https://github.com/OpenHands/extensions",
+  "license": "MIT",
+  "keywords": [
+    "slack",
+    "standup",
+    "digest",
+    "summary",
+    "daily",
+    "cron",
+    "automation"
+  ]
+}

package/skills/slack-standup-digest/README.md

@@ -0,0 +1,34 @@
+# Slack Standup Digest
+
+Create an automation that generates an async standup digest from Slack channels.
+
+## Triggers
+
+This skill is activated by keywords:
+
+- `standup digest`
+- `daily summary from Slack`
+- `async standup automation`
+
+## Features
+
+- **Scans selected Slack channels for recent messages**
+- **Groups updates by project with blockers and decisions highlighted**
+- **Configurable schedule and timezone**
+- **Auto-post or draft mode for review before posting**
+- **Smart lookback**: Friday→Monday for weekend gaps
+
+## Prerequisites
+
+Slack MCP installed in Settings → MCP
+
+## Quick Start
+
+Ask OpenHands:
+
+> "Set up a daily standup digest that summarizes #engineering and
+> #frontend channels and posts to #standup at 9 AM ET"
+
+## See Also
+
+- [SKILL.md](SKILL.md) — Full setup workflow reference

package/skills/slack-standup-digest/SKILL.md

@@ -0,0 +1,92 @@
+---
+name: slack-standup-digest
+description: >
+  Create an automation that generates an async standup digest from Slack.
+  Searches selected channels for messages since the previous workday, groups
+  updates by project, highlights blockers and decisions, and posts a summary
+  to a target channel.
+triggers:
+  - /standup-digest:setup
+---
+
+# Slack Standup Digest Automation
+
+Set up a recurring automation that summarizes Slack activity into an async
+standup digest.
+
+---
+
+## Prerequisites
+
+### Required integration
+
+- **Slack MCP** must be installed in Settings → MCP.
+
+### Information to collect
+
+Ask the user for:
+
+1. **Source channels** — which Slack channels to scan for updates (e.g. `#engineering`, `#frontend`, `#backend`)
+2. **Target channel** — where the digest should be posted (e.g. `#standup`, `#team-updates`)
+3. **Schedule** — when should the digest run? Default: weekday mornings at 9 AM
+4. **Timezone** — user's timezone (e.g. `America/New_York`, `Europe/London`)
+5. **Auto-post or draft** — should the digest post automatically, or be saved for the user to review and approve first?
+6. **Grouping** — how should updates be organized? Default: by project/channel, with sections for shipped work, active work, blockers, and decisions
+
+---
+
+## Setup Workflow
+
+### Step 1 — Verify Slack MCP access
+
+Confirm the Slack MCP integration is working:
+```
+Use the Slack MCP to search for recent messages in one of the source channels.
+```
+
+If it fails, tell the user to install the Slack MCP integration first.
+
+### Step 2 — Configure the schedule
+
+Build a cron schedule from the user's preferences:
+- Weekday mornings at 9 AM ET: `0 9 * * 1-5` with timezone `America/New_York`
+- Daily at 8 AM UTC: `0 8 * * *`
+
+### Step 3 — Build the digest prompt
+
+Construct a prompt that includes:
+- Source channels to scan
+- Target channel for posting
+- Lookback window (typically "since previous workday" — Friday→Monday for Monday digests)
+- Grouping structure (by project, by channel, etc.)
+- Whether to auto-post or draft
+- What to highlight: blockers, decisions, shipped items, unanswered questions
+
+### Step 4 — Create the automation
+
+Read the Automation backend URL and auth from `<RUNTIME_SERVICES>`:
+- Use the **Automation backend** `url_from_agent` as `OPENHANDS_HOST`
+- Auth: `X-Session-API-Key: $OPENHANDS_AUTOMATION_API_KEY`
+
+Use the **prompt preset** endpoint:
+```bash
+curl -s -X POST "${OPENHANDS_HOST}/api/automation/v1/preset/prompt" \
+  -H "X-Session-API-Key: $OPENHANDS_AUTOMATION_API_KEY" \
+  -H "Content-Type: application/json" \
+  -d '{
+    "name": "Slack Standup Digest",
+    "prompt": "<constructed digest prompt>",
+    "trigger": {"type": "cron", "schedule": "<schedule>", "timezone": "<tz>"}
+  }'
+```
+
+### Step 5 — Confirm
+
+Tell the user:
+> ✅ **Slack Standup Digest** is running!
+>
+> - Automation ID: `{id}`
+> - Source channels: `{channel list}`
+> - Target channel: `{target}`
+> - Schedule: `{cron description}`
+> - Mode: `{auto-post or draft}`

package/skills/slack-standup-digest/commands/standup-digest:setup.md

@@ -0,0 +1,8 @@
+---
+# auto-generated by sync_extensions.py
+description: Create an automation that generates an async standup digest from Slack. Searches selected channels for messages since the previous workday, groups updates by project, highlights blockers and decisions, and posts a summary to a target channel.
+---
+
+Read and follow the complete instructions in the SKILL.md file located in this skill's directory.
+
+$ARGUMENTS

package/skills/spark-version-upgrade/.plugin/plugin.json

@@ -0,0 +1,20 @@
+{
+  "name": "spark-version-upgrade",
+  "version": "1.0.0",
+  "description": "Upgrade Apache Spark applications between major versions (2.x\u21923.x, 3.x\u21924.x). Covers build files, deprecated APIs, configuration changes, SQL/DataFrame updates, and test validation.",
+  "author": {
+    "name": "OpenHands",
+    "email": "contact@all-hands.dev"
+  },
+  "homepage": "https://github.com/OpenHands/extensions",
+  "repository": "https://github.com/OpenHands/extensions",
+  "license": "MIT",
+  "keywords": [
+    "spark",
+    "upgrade",
+    "migration",
+    "pyspark",
+    "scala",
+    "big-data"
+  ]
+}

package/skills/spark-version-upgrade/README.md

@@ -0,0 +1,54 @@
+# spark-version-upgrade
+
+Upgrade Apache Spark applications between major versions (2.x→3.x, 3.x→4.x). Covers build files, deprecated APIs, configuration changes, SQL/DataFrame updates, and test validation.
+
+## Triggers
+
+This skill is activated by the following keywords:
+
+- `spark upgrade`
+- `spark migration`
+- `spark version`
+- `upgrade spark`
+- `spark 3`
+- `spark 4`
+- `pyspark upgrade`
+
+## Overview
+
+This skill provides a structured, six-phase workflow for upgrading Apache Spark applications:
+
+| Phase | Description |
+|-------|-------------|
+| 1. Inventory & Impact Analysis | Scan the codebase, identify Spark usage, document scope |
+| 2. Build File Updates | Bump Spark/Scala/Java versions in Maven, SBT, Gradle, or pip |
+| 3. API Migration | Replace removed/deprecated APIs (SQLContext, Accumulator, etc.) |
+| 4. Configuration Migration | Rename/remove deprecated Spark config properties |
+| 5. SQL & DataFrame Migration | Fix breaking SQL behavior (ANSI mode, type coercion, date parsing) |
+| 6. Test Validation | Compile, test, compare output to pre-upgrade baseline |
+
+## Supported Upgrade Paths
+
+- **Spark 2.x → 3.x** — Major API removals (SQLContext, HiveContext, Accumulator v1), Scala 2.12/2.13
+- **Spark 3.x → 4.x** — ANSI mode default, Java 17+ requirement, Scala 2.13 only, legacy flag removal
+
+## Languages & Build Systems
+
+- **Languages**: Scala, Java, Python (PySpark)
+- **Build systems**: Maven, SBT, Gradle, pip/uv
+
+## Reference Material
+
+- [Apache Spark Migration Guide](https://spark.apache.org/docs/latest/migration-guide.html) — The official, up-to-date guide covering API removals, configuration changes, SQL behavior, PySpark, Structured Streaming, and MLlib for every Spark release
+
+## Example Usage
+
+Ask the agent:
+
+> "Upgrade this project from Spark 2.4 to Spark 3.5"
+
+> "Migrate our PySpark codebase to Spark 4.0"
+
+> "Fix all Spark deprecation warnings in this repo"
+
+The agent will follow the six-phase workflow, producing a `spark_upgrade_impact.md` document and systematically updating build files, code, configuration, and SQL queries.

package/skills/spark-version-upgrade/SKILL.md

@@ -0,0 +1,233 @@
+---
+name: spark-version-upgrade
+description: Upgrade Apache Spark applications between major versions (2.x→3.x, 3.x→4.x). Covers build files, deprecated APIs, configuration changes, SQL/DataFrame updates, and test validation.
+license: MIT
+compatibility: Requires Java 8+/11+/17+, Scala 2.12/2.13, Maven/Gradle/SBT, Apache Spark
+triggers:
+  - spark upgrade
+  - spark migration
+  - spark version
+  - upgrade spark
+  - spark 3
+  - spark 4
+  - pyspark upgrade
+---
+
+Upgrade Apache Spark applications between major versions with a structured, phase-by-phase workflow.
+
+## When to Use
+
+- Migrating from Spark 2.x → 3.x or Spark 3.x → 4.x
+- Updating PySpark, Spark SQL, or Structured Streaming applications
+- Resolving deprecation warnings before a Spark version bump
+
+## Workflow Overview
+
+1. **Inventory & Impact Analysis** — Scan the codebase and assess scope
+2. **Build File Updates** — Bump Spark/Scala/Java dependencies
+3. **API Migration** — Replace deprecated and removed APIs
+4. **Configuration Migration** — Update Spark config properties
+5. **SQL & DataFrame Migration** — Fix query-level breaking changes
+6. **Test Validation** — Compile, run tests, verify results
+
+---
+
+## Phase 1: Inventory & Impact Analysis
+
+Before changing any code, assess what needs to change. Read the official Apache Spark migration guide for the target version — it documents every API removal, config rename, and behavioral change per release:
+https://spark.apache.org/docs/latest/migration-guide.html
+
+### Checklist
+
+- [ ] Read the migration guide section for the target Spark version
+- [ ] Identify current Spark version (check `pom.xml`, `build.sbt`, `build.gradle`, or `requirements.txt`)
+- [ ] Identify target Spark version
+- [ ] Search for deprecated APIs: `grep -rn 'import org.apache.spark' --include='*.scala' --include='*.java' --include='*.py'`
+- [ ] List all Spark config properties: `grep -rn 'spark\.' --include='*.conf' --include='*.properties' --include='*.scala' --include='*.java' --include='*.py' | grep -v 'test'`
+- [ ] Check for custom `SparkSession` or `SparkContext` extensions
+- [ ] Identify connector dependencies (Hive, Kafka, Cassandra, Delta, Iceberg)
+- [ ] Document findings in `spark_upgrade_impact.md`
+
+### Output
+
+```
+spark_upgrade_impact.md   # Summary of affected files, APIs, and configs
+```
+
+---
+
+## Phase 2: Build File Updates
+
+Update dependency versions and resolve compilation.
+
+### Maven (`pom.xml`)
+
+```xml
+<!-- Update Spark version property -->
+<spark.version>3.5.1</spark.version>    <!-- or 4.0.0 -->
+<scala.version>2.13.12</scala.version>  <!-- Spark 3.x: 2.12/2.13; Spark 4.x: 2.13 -->
+
+<!-- Update artifact IDs if Scala cross-version changed -->
+<artifactId>spark-core_2.13</artifactId>
+<artifactId>spark-sql_2.13</artifactId>
+```
+
+### SBT (`build.sbt`)
+
+```scala
+val sparkVersion = "3.5.1" // or "4.0.0"
+scalaVersion := "2.13.12"
+
+libraryDependencies += "org.apache.spark" %% "spark-core" % sparkVersion
+libraryDependencies += "org.apache.spark" %% "spark-sql" % sparkVersion
+```
+
+### Gradle (`build.gradle`)
+
+```groovy
+ext {
+    sparkVersion = '3.5.1' // or '4.0.0'
+}
+dependencies {
+    implementation "org.apache.spark:spark-core_2.13:${sparkVersion}"
+    implementation "org.apache.spark:spark-sql_2.13:${sparkVersion}"
+}
+```
+
+### PySpark (`requirements.txt` / `pyproject.toml`)
+
+```
+pyspark==3.5.1   # or 4.0.0
+```
+
+### Checklist
+
+- [ ] Update Spark version in build file
+- [ ] Update Scala version if crossing 2.12→2.13 boundary
+- [ ] Update Java source/target level if required (Spark 4.x requires Java 17+)
+- [ ] Update connector library versions to match new Spark version
+- [ ] Resolve dependency conflicts (`mvn dependency:tree` / `sbt dependencyTree`)
+- [ ] Confirm project compiles (errors at this stage are expected — they guide Phase 3)
+
+---
+
+## Phase 3: API Migration
+
+Replace removed and deprecated APIs. Work through compiler errors systematically.
+
+### Common Patterns
+
+Consult the official Apache Spark migration guide for the complete list of changes for each version:
+https://spark.apache.org/docs/latest/migration-guide.html
+
+#### SparkSession Creation (2.x → 3.x)
+
+```scala
+// BEFORE (Spark 1.x/2.x)
+val sc = new SparkContext(conf)
+val sqlContext = new SQLContext(sc)
+
+// AFTER (Spark 2.x+/3.x)
+val spark = SparkSession.builder()
+  .config(conf)
+  .enableHiveSupport() // if needed
+  .getOrCreate()
+val sc = spark.sparkContext
+```
+
+#### RDD to DataFrame (2.x → 3.x)
+
+```scala
+// BEFORE
+rdd.toDF()  // implicit from SQLContext
+
+// AFTER
+import spark.implicits._
+rdd.toDF()  // implicit from SparkSession
+```
+
+#### Accumulator API (2.x → 3.x)
+
+```scala
+// BEFORE
+val acc = sc.accumulator(0)
+
+// AFTER
+val acc = sc.longAccumulator("name")
+```
+
+### Checklist
+
+- [ ] Replace `SQLContext` / `HiveContext` with `SparkSession`
+- [ ] Replace deprecated `Accumulator` with `AccumulatorV2`
+- [ ] Update `DataFrame` → `Dataset[Row]` where needed
+- [ ] Replace removed `RDD.mapPartitionsWithContext` with `mapPartitions`
+- [ ] Fix `SparkConf` deprecated setters
+- [ ] Update custom `UserDefinedFunction` registration
+- [ ] Migrate `Experimental` / `DeveloperApi` usages that were removed
+- [ ] Verify all compilation errors from Phase 2 are resolved
+
+---
+
+## Phase 4: Configuration Migration
+
+Spark renames and removes configuration properties between versions. The official migration guide documents every renamed and removed property per release:
+https://spark.apache.org/docs/latest/migration-guide.html
+
+### Checklist
+
+- [ ] Rename deprecated config keys (e.g., `spark.shuffle.file.buffer.kb` → `spark.shuffle.file.buffer`)
+- [ ] Update removed configs to their replacements
+- [ ] Review `spark-defaults.conf`, application code, and submit scripts
+- [ ] Check for hardcoded config values in test fixtures
+- [ ] Verify `SparkSession.builder().config(...)` calls use current property names
+
+---
+
+## Phase 5: SQL & DataFrame Migration
+
+Spark SQL behavior changes between versions can silently alter query results.
+
+### Key Breaking Changes (2.x → 3.x)
+
+- `CAST` to integer no longer truncates silently — set `spark.sql.ansi.enabled` if needed
+- `FROM` clause is required in `SELECT` (no more `SELECT 1`)
+- Column resolution order changed in subqueries
+- `spark.sql.legacy.timeParserPolicy` controls date/time parsing behavior
+
+### Key Breaking Changes (3.x → 4.x)
+
+- ANSI mode is default (`spark.sql.ansi.enabled=true`)
+- Stricter type coercion in comparisons
+- `spark.sql.legacy.*` flags removed
+
+### Checklist
+
+- [ ] Audit SQL strings and DataFrame expressions for changed behavior
+- [ ] Add explicit `CAST` where implicit coercion relied on legacy behavior
+- [ ] Update date/time format patterns to match new parser
+- [ ] Test SQL queries with representative data and compare output to pre-upgrade baseline
+- [ ] Set `spark.sql.legacy.*` flags temporarily if needed for phased migration
+
+---
+
+## Phase 6: Test Validation
+
+### Checklist
+
+- [ ] All code compiles without errors
+- [ ] All existing unit tests pass
+- [ ] All existing integration tests pass
+- [ ] Run Spark jobs locally with sample data and compare output to pre-upgrade baseline
+- [ ] No deprecation warnings remain (or are documented with a migration timeline)
+- [ ] Update CI/CD pipeline to use new Spark version
+- [ ] Document any `spark.sql.legacy.*` flags that are set temporarily
+
+## Done When
+
+✓ Project compiles against target Spark version
+✓ All tests pass
+✓ No removed APIs remain in code
+✓ Configuration properties are current
+✓ SQL queries produce correct results
+✓ Upgrade impact documented in `spark_upgrade_impact.md`

package/skills/ssh/.plugin/plugin.json

@@ -0,0 +1,18 @@
+{
+  "name": "ssh",
+  "version": "1.0.0",
+  "description": "Establish and manage SSH connections to remote machines, including key generation, configuration, and file transfers. Use when connecting to remote servers, executing remote commands, or transferri...",
+  "author": {
+    "name": "OpenHands",
+    "email": "contact@all-hands.dev"
+  },
+  "homepage": "https://github.com/OpenHands/extensions",
+  "repository": "https://github.com/OpenHands/extensions",
+  "license": "MIT",
+  "keywords": [
+    "ssh",
+    "remote",
+    "scp",
+    "server"
+  ]
+}

package/skills/ssh/README.md

@@ -0,0 +1,140 @@
+# Ssh
+
+Establish and manage SSH connections to remote machines, including key generation, configuration, and file transfers. Use when connecting to remote servers, executing remote commands, or transferring files via SCP.
+
+## Triggers
+
+This skill is activated by the following keywords:
+
+- `ssh`
+- `remote server`
+- `remote machine`
+- `remote host`
+- `remote connection`
+- `secure shell`
+- `ssh keys`
+
+## Details
+
+# SSH Skill
+
+This skill provides capabilities for establishing and managing SSH connections to remote machines.
+
+## Capabilities
+
+- Establish SSH connections using password or key-based authentication
+- Generate and manage SSH key pairs
+- Configure SSH for easier connections
+- Execute commands on remote machines
+- Transfer files between local and remote machines
+- Manage SSH configurations and known hosts
+
+## Authentication Methods
+
+### Password Authentication
+
+```bash
+ssh username@hostname
+```
+
+When prompted, you should ask the user for their password or a private key.
+
+### Key-Based Authentication
+
+Generate a new SSH key pair:
+```bash
+ssh-keygen -t ed25519 -f ~/.ssh/key_name -C "comment" -N ""
+```
+
+Copy the public key to the remote server:
+```bash
+ssh-copy-id -i ~/.ssh/key_name.pub username@hostname
+```
+
+Connect using the private key:
+```bash
+ssh -i ~/.ssh/key_name username@hostname
+```
+
+## SSH Configuration
+
+Create or edit the SSH config file for easier connections:
+```bash
+mkdir -p ~/.ssh
+cat > ~/.ssh/config << 'EOF'
+Host alias
+    HostName hostname_or_ip
+    User username
+    IdentityFile ~/.ssh/key_name
+    Port 22
+    ServerAliveInterval 60
+EOF
+chmod 600 ~/.ssh/config
+```
+
+Then connect using the alias:
+```bash
+ssh alias
+```
+
+## Common SSH Options
+
+- `-p PORT`: Connect to a specific port
+- `-X`: Enable X11 forwarding
+- `-L local_port:remote_host:remote_port`: Set up local port forwarding
+- `-R remote_port:local_host:local_port`: Set up remote port forwarding
+- `-N`: Do not execute a remote command (useful for port forwarding)
+- `-f`: Run in background
+- `-v`: Verbose mode (add more v's for increased verbosity)
+
+## File Transfer with SCP
+
+Copy a file to the remote server:
+```bash
+scp /path/to/local/file username@hostname:/path/to/remote/directory/
+```
+
+Copy a file from the remote server:
+```bash
+scp username@hostname:/path/to/remote/file /path/to/local/directory/
+```
+
+Copy a directory recursively:
+```bash
+scp -r /path/to/local/directory username@hostname:/path/to/remote/directory/
+```
+
+## SSH Agent
+
+Start the SSH agent:
+```bash
+eval "$(ssh-agent -s)"
+```
+
+Add a key to the agent:
+```bash
+ssh-add ~/.ssh/key_name
+```
+
+## Troubleshooting
+
+- Check SSH service status on remote: `systemctl status sshd`
+- Verify SSH port is open: `nc -zv hostname 22`
+- Debug connection issues: `ssh -vvv username@hostname`
+- Check permissions: SSH private keys should have 600 permissions (`chmod 600 ~/.ssh/key_name`)
+- Verify known_hosts: If host key changed, remove the old entry with `ssh-keygen -R hostname`
+
+## Secure SSH Key Management
+
+### Local Storage with Proper Permissions
+
+The most basic approach is to ensure proper file permissions:
+
+```bash
+# Set correct permissions for private keys
+chmod 600 ~/.ssh/id_ed25519
+# Set correct permissions for public keys
+chmod 644 ~/.ssh/id_ed25519.pub
+# Set correct permissions for SSH directory
+chmod 700 ~/.ssh
+```