sync-agent-infra

Detect and fix drift across agent-first infrastructure files.

8.1k|1.2k|Updated Feb 24, 2026

Search Tags:#workflow #consistency #validation #infrastructure #drift-detection #agent-skills

Ready to run

npx skills add https://github.com/NVIDIA/OpenShell --skill sync-agent-infra-nvidia

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sync-agent-infra
Source: https://github.com/NVIDIA/OpenShell/tree/main/.agents/skills/sync-agent-infra
Command: npx skills add https://github.com/NVIDIA/OpenShell --skill sync-agent-infra-nvidia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect and fix drift across agent-first infrastructure files that reference each other and must stay consistent.

Core Features & Use Cases

Inventory and verify critical files (AGENTS.md, CONTRIBUTING.md, README.md) for cross-reference integrity.
Detect drift in workflow chains, skill tables, and issue/PR conventions, and guide remediation across related SKILL.md entries.
Trigger checks after adding, removing, or renaming skills, crates, or workflows to maintain coherence.

Quick Start

From the repository root, run the drift-check to verify cross-file consistency.

Frequently Asked Questions about sync-agent-infra

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

FAQPage Schema

How do I detect drift across agent infrastructure files like AGENTS.md and README.md?▼

Infrastructure drift detection scans agent-first files like AGENTS.md, CONTRIBUTING.md, and README.md to find broken cross-references and misaligned workflow chains. It triggers after adding, removing, or renaming skills, crates, or workflows to ensure all companion SKILL.md entries and architecture mappings remain consistent.

When do I need to run a consistency check on my agent skills and workflow chains?▼

You need to run a consistency check immediately after adding, removing, or renaming skills, crates, or workflows. This ensures that workflow chains, skill tables, issue and PR conventions, and companion SKILL.md entries remain coherent and properly cross-referenced across the repository.

What is the best way to keep AGENTS.md and CONTRIBUTING.md cross-references accurate?▼

The best way to keep AGENTS.md and CONTRIBUTING.md cross-references accurate is to enforce a drift-check routine that validates cross-file references, companion SKILL.md entries, and the accuracy of the skills table and architecture mappings whenever repository changes occur.

How does drift detection handle companion SKILL.md entries when workflows change?▼

Drift detection handles companion SKILL.md entries by verifying their alignment with updated workflow chains and skill tables. It guides remediation across related entries to ensure that all cross-file references and architecture mappings reflect the current repository state.

Can I fix broken architecture mappings and skill tables without manual searching?▼

Yes, you can fix broken architecture mappings and skill tables by running a drift-check that automatically inventories critical files, detects inconsistencies, and guides remediation across related infrastructure files to restore cross-reference integrity without manual searching.

Why does my README.md drift after renaming agent skills or crates?▼

Your README.md drifts after renaming agent skills or crates because cross-file references, the skills table, and architecture mappings become outdated. Running a drift-check detects these inconsistencies and guides the necessary remediation across all related files.