| name | supply-chain-refresh |
| model | sonnet |
| description | Produces a Supply Chain Refresh Report and updated manifest.json by pulling the latest from all watched repos, scanning for new or changed skills, normalizing, and packaging them into CAS. Use when: "refresh the supply chain", "update community skills", "weekly skill library maintenance", "a community repo announced a new release". |
| license | Complete terms in LICENSE.txt |
| category | system-health |
| triggers | ["refresh the supply chain","update community skills","weekly skill library maintenance","a community repo announced a new release"] |
| tier | 1 |
| agents | ["primary"] |
| tool_dependencies | ["file_system"] |
| inputs | [{"name":"watched_repos","type":"string[]","description":"List of community repo URLs to pull and scan for new or changed skills","required":false}] |
| outputs | [{"name":"refresh_report","type":"ref","format":"cas-ref","description":"Supply Chain Refresh Report and updated manifest.json with newly normalized and CAS-packaged skills"}] |
Supply Chain Refresh
Automated skill supply chain maintenance.
I. Philosophy
A supply chain is only as good as its refresh rate. Community skills evolve — repos add new skills, fix bugs, and improve documentation. This skill runs the full scan-normalize-package pipeline on a scheduled or manual basis, producing a diff report that shows what changed since the last run.
II. When to Use
- On a weekly schedule to keep the skill library current
- After adding new repos to the watched list
- When a community repo announces a new release
- Before publishing to OCI (Action 7) to ensure latest versions
III. Workflow
Step 1: Load Watched Repo List
Read the repo list from the supply chain manifest:
/AgenticStackOrchestration/specs/starred-repos-supply-chain/manifest.json
Extract source_repos array. Also check for any newly starred repos:
gh api user/starred --jq '.[].full_name'
Step 2: Pull Latest
For each repo:
- If already cloned:
git pull --ff-only
- If new:
git clone --depth=1
- Record: commit SHA before and after pull
Step 3: Scan for Changes
Run scan-community-repos on all repo paths.
Compare new catalog against previous manifest.json:
- New skills: present in scan, absent in manifest
- Updated skills: present in both, content hash differs
- Removed skills: present in manifest, absent in scan
Step 4: Normalize New/Updated Skills
For each new or updated skill:
- Run
normalize-community-skill
- Copy to staging directory
Step 5: Package
Run dojo skill package-all on staging directory.
Only new/updated skills will get new CAS entries (content-addressed = idempotent for unchanged content).
Step 6: Generate Diff Report
# Supply Chain Refresh Report
Date: {timestamp}
Previous run: {last_manifest_date}
## Changes
- New skills: {count} ({names})
- Updated skills: {count} ({names})
Removed skills: {count} ({names})
Unchanged: {count}
| Name | Source | Tier | CAS Hash |
|------|--------|------|----------|
