skill-update-check

To audit imported skills for drift and security, compare the locked SHAs in your skills.lock file against the latest upstream commits on the tracked branch to identify changes and assign risk flags for prioritized triage.

Skills.lock drift detection works by iteratively comparing each tracked skill's pinned SHA hash against the latest upstream commit on its configured branch, detecting unauthorized or outdated changes since the version was locked.

Checking upstream skill updates respects the enabled set configured in your aeon.yml file, ensuring the audit only processes active skills and factors their enabled status into the final risk triage prioritization.

Yes, you can generate an automated report that outputs a comprehensive markdown file at articles/skill-update-check-${today}.md alongside a compact status footer designed specifically for monitoring and automation pipelines.

The best way to triage security risks for outdated skill versions is to classify changes by drift size and security verdict, prioritizing updates based on whether the skill is enabled in your aeon.yml configuration.

No, the skill audit process requires no external dependencies to function, relying solely on the GitHub API to fetch upstream branch data and comparing it against your local skills.lock file.