Update to Claus Argos Skill OS

{
  "description": "Inventory, catalog, compare, version, back up, synchronize, package, and maintain a personal or organizational agent-skill library. Use when a user asks how many skills exist, where they are stored, what each skill does, whether copies differ, which skills overlap, whether a catalog is current, how to organize skills across Codex and desktop folders, or to prepare safe backups, manifests, checksums, archives, portability maps, and controlled updates.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 251
    },
    {
      "relative_path": "references/library-schema.md",
      "size_in_bytes": 392
    },
    {
      "relative_path": "references/project-documentation-routing.md",
      "size_in_bytes": 2085
    },
    {
      "relative_path": "scripts/inventory-skills.py",
      "size_in_bytes": 2292
    }
  ],
  "name": "manage-skill-library",
  "skill_md_contents": "---\nname: manage-skill-library\ndescription: Inventory, catalog, compare, version, back up, synchronize, package, and maintain a personal or organizational agent-skill library. Use when a user asks how many skills exist, where they are stored, what each skill does, whether copies differ, which skills overlap, whether a catalog is current, how to organize skills across Codex and desktop folders, or to prepare safe backups, manifests, checksums, archives, portability maps, and controlled updates.\n---\n\n# Manage Skill Library\n\nMaintain one declared source of truth and make every other copy traceable.\n\n## Workflow\n\n1. Confirm library roots, installed root, backup/export roots, runtime, and whether the request is read-only or authorizes changes.\n2. Run `scripts/inventory-skills.py ROOT --json OUTPUT.json --markdown OUTPUT.md` for each root.\n3. Compare normalized skill names, descriptions, file lists, hashes, UI metadata, and modified content. Do not assume same folder name means same version.\n4. Classify entries as `identical`, `changed`, `installed-only`, `backup-only`, `conflicting`, `invalid`, or `unknown`.\n5. Detect overlaps by intended trigger and outcome, not merely keywords. Recommend keep, route, merge, split, archive, or retire.\n6. Propose a sync plan naming source, destination, overwrite behavior, recovery copy, and expected changes.\n7. Obtain explicit approval before overwriting, deleting, replacing, symlinking, installing, or activating anything.\n8. After approved changes, rebuild inventories and verify hashes.\n\n## Rules\n\n- Never designate a source of truth silently.\n- Preserve user changes and unrelated files.\n- Prefer recoverable archives and dated versions.\n- Do not auto-update third-party skills without provenance, security review, diff review, and approval.\n- Keep the human catalog derived from the installed inventory so counts cannot drift.\n- For project/documentation skills, maintain the ownership and lifecycle routing matrix in `references/project-documentation-routing.md`; test positive triggers and near-neighbor exclusions before changing descriptions.\n\n## Output\n\nReturn authoritative count by root, status table, duplicates/conflicts, coverage map, proposed actions, and verification result. State whether counts include system/plugin skills or only personal skills.\n"
}