update-gateway-hub

To check stale HTML pages, the Skill scans your site, ranks pages by verification age, and pulls live updates from Google Docs, GitHub, Jira, and Slack to detect outdated content. It then reconciles changes by applying approved in-place HTML edits.

Automating knowledge hub staleness checks involves parallel source sweeps across GitHub, Jira, and Slack. The Skill compares live source updates against published HTML pages and organizes findings into new, changed, stale, and failed items for targeted maintenance.

Staleness ranking works by ordering HTML pages based on data-verified dates so the oldest content is checked first. This prioritization ensures the most outdated pages are reconciled with live source updates before newer, stable content is reviewed.

Yes, you can preserve existing site structure during updates. The Skill applies only user-approved edits in place, refreshes verification dates, and maintains the current layout while replacing outdated content with data from live sources.

Yes, the staleness check works with local transcript files, Slack discussions, Google Docs, GitHub repositories, and Jira tickets. It performs parallel source checks against these inputs to identify and report necessary HTML page updates.

To report content changes, the Skill compares differences between live sources and published pages, categorizing discrepancies into new, changed, stale, and failed items. This structured reporting guides which HTML edits require your approval.