[polylane]

The weekly Skill Index check failed because the published agent skills index was out of date. Its skills were pinned to older source commits of five plugin repositories, so the drift check regenerated a different file and exited with an error. The index now pins every skill to the repository commit the marketplace resolves today, and the drift and URL checks pass. Every skill URL is pinned to a commit, so a skill moving upstream never breaks the published index; only the pinned commits advanced, and the check reported that staleness. Regenerating the index from the marketplace removes it. A scheduled run will detect this again if it recurs.

flowchart LR
  MP["marketplace HEAD"] --> GEN["generate"]
  PLUG["plugin repo HEADs"] --> GEN
  GEN --> IDX["index.json (updated pins)"]
  IDX --> CHK["skills:check -> 55 URLs 200"]
  IDX --> DRIFT["skills:drift -> pass"]

Loading

Fix walkthrough

Watch the fix explained (1:30). Recorded for commit 62e402eb2bb010cfea8a71e0c69255d21caaa176.

Out of scope

• Auto-regenerating the index on plugin changes: the weekly schedule is the intended drift detector.

Production impact

Skill index regeneration keeps the published index valid

The change only updates the pinned commit SHAs in the static skill index served at agents.datum.net. I confirmed every pinned URL returns 200 and its digest matches (55 skills) with npm run skills:check, so the served artifact stays valid and no runtime path changes. No deployed resource edges are recorded for the repository node, so no production resource behavior changes on merge.

Checked and not affected (1)

• agents.datum.net

Observability

• Skill Index workflow: npm run skills:drift now exits 0 and npm run skills:check reports the URL and digest check for the served index.
• No new log or metric is added; the change is a data file under public/.

Polylane assessed this pull request at 62e402e.

Causal chain

• Signal (alert): CI failing: Skill Index on datum-cloud/agents.datum.net@main
• Surfacing site: GitHub Actions workflow "Skill Index" run 42574460959 at datum-cloud/agents.datum.net:.github/workflows/skill-index.yml#skill-index
• Mechanism: The committed public/.well-known/agent-skills/index.json pins each skill URL to a plugin-repo commit SHA. Five plugin repositories advanced their default branch after the index was last generated, so npm run skills:drift regenerates a different index and exits 1.
• Producer: datum-cloud/agents.datum.net skill index data, at datum-cloud/agents.datum.net:public/.well-known/agent-skills/index.json
• Trigger: The compute, dns-operator, network-services-operator, milo-os/activity and milo-os/telemetry repositories advanced their default branch after the index was generated.
• What happens to the failed unit today: The published index is served at https://agents.datum.net/.well-known/agent-skills/index.json; every URL is pinned to a commit so a skill move never breaks it, and drift reports the staleness.
• Last observed: 2026-11-09T06:40:32Z
• Blast radius: unknown other resource(s), unknown other tenant(s); data at risk: none named
• Producer evidence:
  • Job 129018939747 step 'Run npm run skills:drift' concluded failure while 'Run npm run skills:check' succeeded.
  • Committed index pins older SHAs for compute (e4f8b26), dns-operator (7501a37), network-services-operator (22075ce), milo-os/activity (750d54c) and milo-os/telemetry (151fc37); digests unchanged.
  • npm run skills:drift exits 1 on the committed file and 0 after npm run skills:generate; npm run skills:check then reports 55 skills, every URL 200 and digest match.

1 file changed (+54/-54)

• public/.well-known/agent-skills/index.json: modified, +54/-54

---

Generated by Polylane. You can ask follow-ups by mentioning @polylane in a comment.