Add Rewind to the public skills catalog

[3mdistal]

Summary

Add Rewind to the public Builder skills catalog while keeping its executable instructions synchronized from Agent Native and its local Clips connection fail-closed.

Why

Rewind is not useful as a copied prompt alone. It reads recent local context through Clips Desktop and a local Model Context Protocol (MCP) connection. Publishing only SKILL.md would let users discover the workflow but leave the agent unable to call its tools; first-time users could also reach a missing-tool error without a safe route to install Clips.

Agent Native therefore remains canonical for the generated skill and local installer. This repository owns public discovery and a human-facing README that explains setup, privacy, and repair.

What changed

• Add the generated skills/rewind/SKILL.md and preserve skills/rewind/README.md as a public documentation overlay.
• Generalize the existing Visual Plan/Visual Recap sync script and workflow to include exported Agent Native skills.
• Add Rewind to the root catalog and Claude/Codex plugin metadata.
• Direct complete installs to @agent-native/skills or @agent-native/core; plain-copy and whole-directory plugin paths explain that they cannot configure the local MCP connection by themselves.
• Require invocation-time consent before opening the official Clips installer and keep Rewind unavailable until Core configures the connection and screen_memory_status succeeds.
• Let CI validate a trusted same-named Agent Native branch when the two companion PRs are open together, otherwise fall back to Agent Native main.
• Accept both legacy and new repository-dispatch events during the producer/consumer transition under one cancel-in-progress concurrency group.

How to test

• Passed: npm run check against the paired Agent Native branch, proving skill frontmatter validity and exact synchronization for Visual Plan, Visual Recap, and Rewind.
• Passed: PR CI check on head d668717, using the trusted companion branch, plus GitGuardian's secret scan.
• Passed: plugin JSON parsing and an HTTP 200 check for https://clips.agent-native.com/download.
• Passed: independent technical review found no material synchronization, installer-contract, or workflow security defect.
• Blocked: end-to-end clean-profile macOS acceptance still requires a runnable branch-built Agent Native CLI, a signed Clips installer, and a profile where Clips is absent. The available machine could not supply that state without touching an existing installation, so the frozen H1–H10 journey remains a pre-merge gate.

For a local sync check:

AGENT_NATIVE_FRAMEWORK_PATH=/path/to/agent-native npm run check

Notes

• No dependencies, schema migrations, credentials, or data migrations are added.
• Rewind remains disabled by default in Clips. Neither this repository nor its plugin installs Clips, grants capture permissions, or enables screen/audio capture.
• skills/rewind/SKILL.md is generated; edit the canonical Agent Native source and run npm run sync:agent-native-skills. The public README is intentionally maintained here.
• The companion producer sends the legacy sync event first and the new event second, so either PR may merge first without losing the synchronization request.

Review focus

• Is the boundary between the generated skill and public README understandable and maintainable?
• Do every public installation path and plugin surface accurately distinguish copying instructions from configuring the local MCP connection?
• Is the same-named-branch CI lookup constrained to trusted BuilderIO/agent-native refs, with a safe main fallback?
• Do the dual event names and shared concurrency group make the cross-repository transition idempotent?

Companion PR

Canonical skill and installer: BuilderIO/agent-native#2345