knowledge-freshness

Validate and refresh stale offline migration knowledge refs against current framework versions.

1|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/vickysrawat/AI-Assisted-development --skill knowledge-freshness-vickysrawat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowledge-freshness
Source: https://github.com/vickysrawat/AI-Assisted-development/tree/main/skills/knowledge-freshness
Command: npx skills add https://github.com/vickysrawat/AI-Assisted-development --skill knowledge-freshness-vickysrawat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Offline knowledge references bundled with the migration skill family decay silently as frameworks release new versions, leaving migration guidance based on outdated facts. This Skill detects which refs are stale and refreshes them with web-grounded, human-approved updates. ## Core Features & Use Cases - Staleness Detection: The check command classifies every manifest ref as FRESH, STALE-BY-AGE, STALE-BY-VERSION, or UNKNOWN using deterministic offline comparison with no network I/O. - Gated Refresh: The refresh command web-grounds current facts, shows a unified diff, runs a higher-tier LLM judge against a strict rubric, and writes only after explicit APPROVE ADO-9004 approval through the Write Gate. - Authority Tagging: Refreshed refs are re-tagged VERIFIED or INFERRED based on source host authority, and the manifest last_verified date is bumped deterministically. - Use Case: A plugin maintainer runs check before a release, finds the .NET stack ref is STALE-BY-VERSION, then runs refresh refs/stacks/dotnet.md to update it to the current .NET version under approval. ## Quick Start Run the knowledge-freshness check command to classify all migration knowledge refs and report which ones are stale.

Frequently Asked Questions about knowledge-freshness

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

FAQPage Schema
How do I check if migration knowledge refs are stale?

Run the `check` command, which executes the knowledge-freshness.cjs script against the freshness manifest. It classifies each ref as FRESH, STALE-BY-AGE, STALE-BY-VERSION, or UNKNOWN using offline date math and an optional `--latest` JSON of current versions.

How do I refresh an outdated framework version reference?

Run `refresh <ref-path>` on a stale ref. The skill web-grounds current facts, shows a unified diff, runs a higher-tier LLM judge, and writes only after you approve with `APPROVE ADO-9004` at the Write Gate.

Does the freshness detector require network access?

No, the detector script performs no network I/O and only compares manifest data against dates and a `--latest` JSON file. Web searches for current versions are performed separately by the LLM before invoking the script.

What happens when a ref is missing from the latest versions file?

Refs absent from the `--latest` JSON are classified as UNKNOWN, never as FRESH. This prevents silently treating unverified refs as up to date when version data is unavailable.

Can knowledge-freshness update refs without approval?

No, all writes go through the Write Gate and require explicit `APPROVE ADO-9004` confirmation. The `check` command is strictly read-only, and `refresh` stops without writing if the judge fails or approval is not given.