Use Case
When working with container registries (Harbor, GHCR, Docker Hub), skopeo is used to inspect images and list tags. The JSON output can be very large, especially list-tags on repos with many tags.
Common Commands
skopeo list-tags docker://harbor.wxs.ro/PROJECT/IMAGE - lists all tags (JSON with potentially hundreds of entries)skopeo inspect docker://registry/image:tag - returns full image manifest JSON (labels, layers, config, etc.)
Savings Opportunity
The output is always JSON and often contains far more data than needed:
list-tags: Only the tag names matter; the wrapping JSON structure is noiseinspect: Usually only a few fields are relevant (digest, labels, created date)
Filtering/summarizing these outputs would save significant tokens, especially in CI migration and registry audit workflows.
Suggested Behavior
rtk skopeo list-tags ... - return just the tag list, optionally truncated (e.g., last N tags)rtk skopeo inspect ... - return a compact summary (digest, created, architecture, key labels)
Use Case
When working with container registries (Harbor, GHCR, Docker Hub),
skopeois used to inspect images and list tags. The JSON output can be very large, especiallylist-tagson repos with many tags.Common Commands
skopeo list-tags docker://harbor.wxs.ro/PROJECT/IMAGE- lists all tags (JSON with potentially hundreds of entries)skopeo inspect docker://registry/image:tag- returns full image manifest JSON (labels, layers, config, etc.)Savings Opportunity
The output is always JSON and often contains far more data than needed:
list-tags: Only the tag names matter; the wrapping JSON structure is noiseinspect: Usually only a few fields are relevant (digest, labels, created date)Filtering/summarizing these outputs would save significant tokens, especially in CI migration and registry audit workflows.
Suggested Behavior
rtk skopeo list-tags ...- return just the tag list, optionally truncated (e.g., last N tags)rtk skopeo inspect ...- return a compact summary (digest, created, architecture, key labels)