ot-apply-upgrade-notes

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

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/triage-software/skills --skill ot-apply-upgrade-notes-triage-software
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ot-apply-upgrade-notes
Source: https://github.com/triage-software/skills/tree/main/skills/ot-apply-upgrade-notes
Command: npx skills add https://github.com/triage-software/skills --skill ot-apply-upgrade-notes-triage-software

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? After upgrading an agent-skills collection, the artifacts previously installed into your repository (tracker descriptors at .ai/trackers/<tracker>.md and browser-provider descriptors at .ai/browsers/<provider>.md) stay stale, which can degrade or skip operations the new skills expect. This Skill diffs installed artifacts against the freshly shipped versions, applies safe updates, and reports exactly what changed. ## Core Features & Use Cases - Descriptor diffing: Compares installed tracker and browser descriptors operation-by-operation against shipped versions, classifying each difference as missing, changed, locally edited, or local-only. - Customization preservation: Never overwrites a locally edited section silently; shows both versions and asks the operator to keep, replace, or merge, while always keeping local-only operations. - Upgrade-notes migration: Walks the collection's UPGRADE_NOTES.md, adds missing config keys with documented defaults, and verifies expected artifacts exist. - Custom-provider gap reports: For trackers or browser providers not shipped in the collection, reports newly required operations with their contract text instead of inventing an implementation. - Use Case: After running npx skills update -p, invoke this Skill to re-sync your repo's .ai/ pipeline artifacts, preview everything with --dry-run, and get a report of conflicts needing a decision. ## Quick Start Run the ot-apply-upgrade-notes skill with --dry-run to preview which tracker and browser descriptor updates the latest skills upgrade would apply to this repository.

Frequently Asked Questions about ot-apply-upgrade-notes

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

FAQPage Schema
How do I update installed skill artifacts after upgrading a skills collection?▼

Run the ot-apply-upgrade-notes skill after `npx skills update`. It diffs your installed tracker and browser descriptors against the shipped versions, applies additive changes, and asks before replacing anything you customized locally.

How can 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 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 you per section to keep local, take shipped, or merge by hand. Local-only operations are always kept.

What happens if I use a custom tracker or browser provider?▼

Custom providers get a gap report against the shipped TEMPLATE.md, listing every newly required operation with its contract text. The skill never invents an implementation for someone else's tracker; it can draft a section for your review on request.

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 and points you at /ot-setup-agent-pipeline instead of auto-running setup. The setup skill is the authority that generates the config and initial artifacts.