agentleFS
Sign inStart free
bastosbastos/skills/package-private-ml-artifacts/SKILL.md

package-private-ml-artifacts

Skill7 starsChanged 10 months agoMITView on GitHub

Inventories, hashes, scans, and verifies datasets, adapters, checkpoints, logs, and evaluation evidence before an explicitly approved private upload. Use when ephemeral jobs or handoffs require durable ML artifacts without exposing credentials or unapproved data.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create or verify the private destination before transfer.

    line 32
  2. Distinctive:

    Keep local evidence until remote verification succeeds.

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Package Private ML Artifacts

Preserve reproducibility while keeping credentials, restricted sources, and large assets out of source control.

Confirm authorization and scope

Obtain explicit approval before uploading datasets, weights, adapters, checkpoints, or other large artifacts. Confirm the destination is private and list exactly what will be uploaded. Never infer that permission to train also grants permission to publish artifacts.

Classify each artifact by source, license, sensitivity, retention need, and whether it belongs in Git, private object storage, or a private model/dataset repository.

Build a manifest

Run:

python scripts/build_artifact_manifest.py experiment-output \
  --output experiment-output/artifact-manifest.json \
  --max-file-mb 5000

The script records relative paths, byte sizes, and SHA-256 hashes and fails on suspicious credential filenames/content or oversized files. Review flagged paths; do not weaken the scan merely to complete an upload.

Include reproduction inputs: commands, configuration, revisions, seed, packages, hardware, source/split manifests, logs, raw outputs, normalized results, validators, and reports. Do not include environment files, tokens, caches, or unrelated workspace data.

Upload and verify

  1. Create or verify the private destination before transfer.
  2. Upload the manifest with the artifacts.
  3. Record destination repository, revision/commit, upload command, and timestamp.
  4. Re-list or download enough data to prove remote sizes and hashes match.
  5. Keep local evidence until remote verification succeeds.

Report omissions and why they were omitted. Do not call an upload complete when only a mutable branch name, partial logs, or unverified files remain.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free