What problem does it solve? Large, generated, or encrypted files do not belong in plain Git history, yet teams still need a single place to discover where those artifacts live, how to fetch them, and how to verify them. This Skill defines a central registry in artifacts/README.md so nothing is tracked ad hoc and no plaintext secrets leak into the repository. ## Core Features & Use Cases - Central Registry: Every artifact or artifact group gets a row in artifacts/README.md with backend, path, encryption status, fetch command, and verify command. - Git LFS Workflow: Standardized commands for tracking narrow per-artifact patterns, pulling specific paths, and checking registry drift with git lfs ls-files. - Encrypted Artifacts: Conventions for age-encrypted files, with private keys kept under .creds/lfs/ and decrypted outputs under ignored .local/artifacts/ paths. - Use Case: When adding a 2 GB sample dataset to a repo, you track it with Git LFS under artifacts/lfs/sample-dataset-v1/, add a registry row with fetch and checksum commands, and commit the pointer files and .gitattributes update together. ## Quick Start Ask the agent to register a new large file as a Git LFS artifact and update the artifacts registry with its fetch and verify commands.
