supply-chain-refresh

Pull watched repositories, detect changed skills, and generate CAS-packaged manifests.

2|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/DojoGenesis/gateway --skill supply-chain-refresh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: supply-chain-refresh
Source: https://github.com/DojoGenesis/gateway/tree/main/plugins/system-health/skills/supply-chain-refresh
Command: npx skills add https://github.com/DojoGenesis/gateway --skill supply-chain-refresh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The supply chain for community skills can become stale as repositories add, remove, or update skills; this Skill automates pulling watched repos, detecting new or changed skills, normalizing them, packaging into CAS, and producing a diff report and updated manifest to maintain an accurate skill library.

Core Features & Use Cases

  • Automated Refresh Pipeline: Pulls watched repositories, scans for new/updated/removed skills, normalizes content, and packages artifacts into content-addressable storage (CAS).
  • Manifest & Audit Trail: Generates a diff-style Supply Chain Refresh Report, updates the manifest.json with the new state, and archives the previous manifest for audits.
  • Resilient Operation: Supports partial-failure logging, idempotent packaging for unchanged content, and best-practice steps such as rate limiting and manifest preservation.
  • Use Case: Run weekly or on-demand after a community repo release to ensure the community skill catalog is current and CAS-packaged for distribution.

Quick Start

Run the supply-chain-refresh skill to pull all watched repos, scan for new or changed skills, normalize and package them into CAS, and produce an updated manifest and diff report.

Frequently Asked Questions about supply-chain-refresh

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

FAQPage Schema
How do I automate scanning GitHub repos for new or updated community skills?

Automated repo scanning pulls watched GitHub repositories, detects new or updated community skills, normalizes content, and packages artifacts into CAS. This produces an updated manifest and diff report to keep skill libraries current without manual tracking.

How does content-addressable storage packaging work for a community skill library?

CAS packaging normalizes skill content into content-addressable storage artifacts. The process ensures idempotent packaging, meaning unchanged content yields identical CAS packages, preventing duplicate artifacts during scheduled supply chain refresh workflows.

Can I generate a manifest diff report to track skill repository changes?

Generating a manifest diff report compares the previous manifest against newly pulled repository states. It highlights added, removed, or updated skills, updates the manifest.json file, and archives the previous version for auditability.

What happens if a repository scan encounters partial failures during a refresh?

Partial failure logging records errors for individual repositories without halting the entire supply chain refresh pipeline. This resilient operation logs failures for auditability while successfully processing and packaging available skills into CAS.

When should I schedule a supply chain refresh for my skill catalog?

Schedule a supply chain refresh weekly or on-demand after a community repository release. Regular execution ensures the skill catalog detects changes across multiple repositories and prepares normalized CAS-packaged artifacts for distribution.

Does supply-chain-refresh support idempotent CAS packaging for unchanged skills?

Idempotent CAS packaging ensures unchanged skill content produces identical content-addressable storage artifacts across multiple runs. This approach prevents redundant processing and maintains consistent artifacts during repeated manifest diff generation.