om-apply-upgrade-notes

Synchronizes installed tracker and browser descriptors with shipped upgrade notes while preserving local edits.

1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/tkogut/agents-os-core --skill om-apply-upgrade-notes-tkogut
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: om-apply-upgrade-notes
Source: https://github.com/tkogut/agents-os-core/tree/main/global_skills/om-apply-upgrade-notes
Command: npx skills add https://github.com/tkogut/agents-os-core --skill om-apply-upgrade-notes-tkogut

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? After upgrading a skills collection, the artifacts a previous run installed into your repository — tracker descriptors at .ai/trackers/<tracker>.md and browser-provider descriptors at .ai/browsers/<provider>.md — become stale, silently degrading or skipping operations they no longer define. This Skill reads the collection's UPGRADE_NOTES.md, diffs installed artifacts against the shipped versions, and brings them up to date without discarding local customizations. ## Core Features & Use Cases - Descriptor diffing: Compares installed tracker and browser descriptors operation-by-operation, classifying each difference as missing, safely replaceable, locally edited, or local-only. - Conflict-safe upgrades: Never overwrites team customizations silently — shows both versions side by side and asks per section, while --yes auto-applies purely additive changes. - Config and artifact checks: Adds missing config keys with documented defaults, verifies the browser provider resolves, and validates the config still parses with jq. - Use Case: After running npx skills add to upgrade your agent pipeline collection, run this Skill with --dry-run to preview exactly which operations (e.g. attach-image-evidence) your installed GitHub tracker descriptor is missing, then apply the additive changes and review the uncommitted diff. ## Quick Start Ask the agent to apply the upgrade notes from the skills collection and re-sync my installed tracker and browser descriptors, using --dry-run first to preview the changes.

Frequently Asked Questions about om-apply-upgrade-notes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update installed tracker descriptors after upgrading a skills collection?▼

Run the upgrade-notes skill, which diffs your installed descriptor at .ai/trackers/<tracker>.md against the shipped version operation by operation. Missing operations are appended additively, unchanged stock sections are replaced safely, and locally edited sections require your explicit confirmation.

How do I preview upgrade changes without modifying my repository?▼

Pass the --dry-run flag to report every change the skill would make without applying anything. The report marks proposed changes distinctly and distinguishes checks on current artifacts from checks on the proposal.

Will the upgrade overwrite my custom tracker descriptor edits?▼

No. Sections that differ from stock are treated as team customizations: the skill shows both versions side by side and asks whether to keep local, take shipped, or merge by hand. Local-only operations are always kept, and --yes only auto-applies purely additive changes.

What happens if my repository uses a custom browser or tracker provider?▼

Custom providers are not auto-implemented. The skill diffs the shipped TEMPLATE.md against your custom descriptor and files a gap report listing every newly required operation with its contract text, drafting a section for your review only when you ask.

Why does the skill stop when .ai/agentic.config.json is missing?▼

Without the config there is nothing installed to upgrade, so the skill stops instead of auto-running setup and points you to om-setup-agent-pipeline. This prevents creating pipeline artifacts in a repository that never opted into the agentic workflow.

Does the upgrade skill commit changes or run tracker operations?▼

No. It performs no tracker operations or label mutations — descriptors are diffed and edited as files only. All changes are left uncommitted for your review, and the final report suggests the commit without making it.