Xpersona
P

Post Update Awareness

CLAWHUB · Unverified

After an OpenClaw version change, read the CHANGELOG entry pinned to the installed version and surface user-relevant changes — new tools, breaking changes, o...

62
Rank
84
Safety
973
Downloads

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 973 downloads reported by the source. Last updated 10/11/2026.

Avoid when

  • Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Install and run

Setup complexity: low.

clawhub skill install s170591b6zq2t4fvge4yc0ajes863ccy:post-update-awareness
  1. Install using `clawhub skill install s170591b6zq2t4fvge4yc0ajes863ccy:post-update-awareness` in an isolated environment before connecting it to live workloads.
  2. No published capability contract is available yet, so validate auth and request/response behavior manually.
  3. Review the upstream CLAWHUB listing at https://clawhub.ai/hussein1362/post-update-awareness before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-hussein1362-post-update-awareness/snapshot"

Run-check

$0.02 USD

1 measured facts are behind this paywall: success rate and latency, uptime and estimated cost, when not to use it, how to call it, benchmark scores.

Agents pay $0.02 in USDC. A card payment is $0.50, the smallest a card allows.

Documentation

CLAWHUB

101,973 characters of source documentation, loaded on request.

Extracted files

4 files captured from the source.

SKILL.md

---
name: post-update-awareness
description: After an OpenClaw version change, read the CHANGELOG entry pinned to the installed version and surface user-relevant changes — new tools, breaking changes, optional native dependencies that may need verification (sharp, ffmpeg, node-pty). Runs once per detected version bump. Use when OpenClaw has just been updated, when openclaw -V differs from the value on file, or when the user asks "what changed in this update?"
metadata: {"openclaw":{"requires":{"bins":["openclaw","curl","node"]}}}
---

# Post-Update Awareness

When OpenClaw is updated, the agent should not be the last to know. This skill reads the project CHANGELOG **for the exact installed version**, distills what changed for the user, and surfaces it once.

## When to use

Run this skill when **any** of the following is true:

1. The user asks "what changed in this update?" or "what's new in OpenClaw?"
2. A first-class update flow finishes (`openclaw update`, `openclaw plugins update`, or a package-manager update).
3. `openclaw -V` returns a value different from the version recorded in the skill's state file.

Do **not** run on every heartbeat. Run **once per detected version change**, then persist the new version so subsequent heartbeats stay quiet.

## Scope and non-goals

This skill **only**:

- Reads existing CHANGELOG content pinned to the installed version
- Reports it to the user
- Optionally probes for known-flaky optional native deps mentioned in the entry

This skill **does not**:

- Apply updates (`openclaw update` already handles that)
- Modify configuration
- Install missing dependencies without explicit user confirmation
- Roll back versions

## Workflow

### 1) Read the current installed version

```json
{ "tool": "exec", "command": "openclaw -V" }
```

Parse the version token (e.g. `OpenClaw 2026.5.3-1 (2eae30e)` → `2026.5.3-1`).

### 2) Compare against the last-known version

The skill maintains a small JSON state file per profile.

**Path resolution** (first match wins):

1. `$OPENCLAW_PROFILE_DIR/state/post-update-awareness.json` — when the runtime exports `OPENCLAW_PROFILE_DIR`
2. `$HOME/.openclaw-<profile>/state/post-update-awareness.json` — when a profile name is known (e.g. from `openclaw --profile <name>` or the `OPENCLAW_PROFILE` env var)
3. `$HOME/.openclaw/state/post-update-awareness.json` — single-profile / default fallback

This matters because the same machine can run multiple profiles (`main`, `noura-moi`, `amber`, …) and each one can independently update on its own cadence. A single shared state file caused the skill to go silent on profile B after surfacing on profile A — the bug the v0.3 path resolver fixes.

Contents:

```json
{
  "lastKnownVersion": "2026.5.2",
  "lastSurfacedAt": "2026-05-04T13:15:00Z",
  "profile": "noura-moi"
}
```

- If the file does not exist → write the current version as the baseline and **exit silently**. (No CHANGELOG dump on first run; only on actual transitions.)
- If `currentVersio

README.md

# post-update-awareness

A ClawHub skill that makes your OpenClaw agent **read its own release notes** after an update.

## What it does

When OpenClaw is updated, the agent has no built-in mechanism to consume the release notes — so optional-dependency surprises (e.g. a new release expects `sharp` to be installed) are discovered the hard way: when an unrelated workflow fails, in front of someone you care about.

This skill closes that loop:

1. Detects a version change between current `openclaw -V` and a small per-profile JSON state file the skill maintains.
2. Fetches the CHANGELOG entry **pinned to the installed version's tag** (`v<version>`), not `main`. So the agent reads the changelog that matches what's actually running.
3. Distills the entry into three buckets the user actually cares about — new tools, breaking changes, optional native deps to verify.
4. Probes known-flaky native modules (`sharp`, `ffmpeg-static`, `node-pty`) to flag missing ones.
5. **Detects plugin version drift** — catches the case where the gateway is on `vNew` but an externalized npm-installed plugin (`@openclaw/whatsapp`, `@openclaw/discord`, etc.) is still on `vOld`.
6. **Verifies channel health** post-restart (`channels status`) and surfaces any `disconnected` / `unhealthy` / `degraded` channel.
7. **Surfaces config rewrites** when `plugins update` overwrites `openclaw.json`, including the path to the auto-saved `.bak`.
8. **Yields to the update-guard** when one is already watching the same transition, so the user isn't notified twice for the same bump.
9. Sends one brief surfaced message via the active channel, then — **only on confirmed delivery** — persists the new version so subsequent heartbeats stay quiet.

## What's new in 0.4.0

- **Strict read-only posture.** All mutation paths (offering to update drifted plugins, cleaning stale config entries) have been removed. This skill now only reads and notifies. For the mutation flow, see the companion skill **[post-update-maintenance](https://clawhub.ai/skills/post-update-maintenance)**, which is explicitly scoped for changes.
- This split was made in response to security scanner feedback flagging the previous combined behavior as scope-contradictory. Trust posture is now clear: this skill is safe to install and run on any heartbeat.

## What's new in 0.3.x

- **Profile-aware state file.** Multi-profile setups (`main` + `noura-moi` + …) no longer share a single state file, which was silencing the skill on profile B after surfacing on profile A.
- **Surface-then-persist ordering.** State is now written only after the channel acknowledges the message, with a retry cap. Channel blips no longer eat the notification.
- **Update-guard awareness.** When an external update-guard already announced the version change, the skill skips the redundant header and goes straight into the CHANGELOG distillation.
- **`scripts/resolve.sh`.** Stable resolver for callers outside the skill (safe-update wrappers, cron jobs) so they stop

_meta.json

{
  "ownerId": "kn7bz8fq6vk4bqtfd8q20gjtgn83cc3w",
  "slug": "post-update-awareness",
  "version": "0.4.0",
  "publishedAt": 1779824276033
}

skill-card.md

## Description:

After an OpenClaw version change, this skill reads the CHANGELOG entry pinned to the installed version and surfaces user-relevant changes, breaking changes, and optional native dependencies that may need verification.

This skill is ready for commercial/non-commercial use.

## Publisher:

[hussein1362](https://clawhub.ai/user/hussein1362)

### License/Terms of Use:

MIT-0

## Use Case:

OpenClaw users and operators use this skill after an update to detect version changes, summarize pinned release notes, and flag plugin drift, channel health, optional dependency, or config warnings without performing maintenance actions.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: The skill reads local OpenClaw version, plugin, channel, update-guard, and per-profile state information.

Mitigation: Install it only where those local operational signals are appropriate to inspect, and keep surfaced output limited to update-relevant diagnostics.

Risk: The skill may make unauthenticated GitHub requests for pinned release notes when no local changelog is available.

Mitigation: Prefer the local changelog when present and request only the exact installed version tag; offline environments should expect the no-notes fallback.

Risk: The skill may identify plugin drift, stale config entries, missing optional dependencies, or unhealthy channels but is not scoped to fix them.

Mitigation: Leave updates, config edits, dependency installs, and restarts to the user or the separate post-update-maintenance skill.

Risk: Writing notification state too early could suppress future update notices.

Mitigation: Persist the per-profile state file only after the update notice has been successfully surfaced and acknowledged.

## Reference(s):

- [Post Update Awareness on ClawHub](https://clawhub.ai/hussein1362/skills/post-update-awareness)
- [OpenClaw versioned CHANGELOG](https://github.com/openclaw/openclaw/blob/v<newVersion>/CHANGELOG.md)
- [Post Update Maintenance companion skill](https://clawhub.ai/skills/post-update-maintenance)

## Skill Output:

**Output Type(s):** [Text, Markdown, Shell commands, Configuration guidance]

**Output Format:** [Concise Markdown notice with short bullet buckets and inline shell commands]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [Caps the surfaced notice at about 18 lines and writes per-profile state only after successful surfacing.]

## Skill Version(s):

0.4.0 (source: server release evidence)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

Sponsored

Ads related to Post Update Awareness and adjacent AI workflows.