How does the skill determine if updates exist?

It runs npx agent-reverse check-updates --json, then uses jq to count the outdated entries and prints a summary if the count is greater than zero.

Can I disable startup notifications?

Yes. Remove this skill from the .claude/commands/ to stop session-start alerts.

How do I perform updates manually?

Use manifest_check_updates to identify outdated items, review the details (id, pinnedCommit, latestCommit), then run manifest_sync to reinstall all skills from the latest commits.

agent-reverse-update

Scanned

npx machina-cli add skill shihwesley/agent-reverse/agent-reverse-update --openclaw

Files (1)

SKILL.md

1.3 KB

Agent Reverse Update

Checks for skill updates automatically on session start.

How It Works

On session start, this skill checks your agent-reverse.json manifest against the remote repos to see if any pinned commits have newer versions available.

Manual Check

To manually check and update:

Check for updates: Use manifest_check_updates MCP tool to see which skills have updates
View outdated: The tool returns outdated array with id, pinnedCommit, and latestCommit
Update all: Use manifest_sync MCP tool to reinstall all skills from latest commits

Example Usage

# Check updates
Use manifest_check_updates tool

# Sync to latest
Use manifest_sync tool

Suppressing Notifications

If you don't want session-start notifications, remove this skill from .claude/commands/.

Source

git clone https://github.com/shihwesley/agent-reverse/blob/main/skills/agent-reverse-update/SKILL.mdView on GitHub

Overview

Automatically checks the local agent-reverse.json manifest against remote repos at session start to detect newer versions of pinned commits. If updates are found, it reports the count, helping you stay current without manual checks.

How This Skill Works

On session start, the hook looks for agent-reverse.json. If present, it runs npx agent-reverse check-updates --json, parses the result with jq to count outdated entries, and echoes a summary like [AgentReverse] N update(s) available.

When to Use It

When you start a session and want to know if any pinned AgentReverse revisions have newer versions
During development in a shared workspace to ensure the manifest is current
To automatically surface update alerts without manual checks
When coordinating updates with MCP tools (manifest_check_updates / manifest_sync)
If startup notifications are noisy, you want a quick way to disable them by removing the skill

Quick Start

Step 1: Ensure agent-reverse.json exists in your workspace
Step 2: Start a new session to trigger the SessionStart update check
Step 3: If updates are reported, use manifest_check_updates and manifest_sync to install the latest commits

Best Practices

Keep agent-reverse.json synced with the remote manifests
Test updates in a staging environment before applying to production
Regularly review the reported update counts and plan upgrades
Complement startup checks with manifest_check_updates before syncing
Document changes to shared manifests so teammates understand updates

Example Use Cases

A developer starts a session and sees [AgentReverse] 2 update(s) available and runs manifest_sync to upgrade to the latest commits
In a team project, every session start surfaces the latest pinned revisions to keep everyone on the same version
Manually verify updates via manifest_check_updates and review outdated entries (id, pinnedCommit, latestCommit) before syncing
If notifications become noisy, the team removes the skill from .claude/commands/ to suppress startup alerts
An automated workflow triggers updates after the startup alert by using MCP tools to install the latest commits

Frequently Asked Questions

Add this skill to your agents