Agent skill · software engineering · thebushidocollective
gitlab-ci-artifacts-caching
Use when configuring artifacts for inter-job data passing or caching for faster builds. Covers cache strategies and artifact management.
Why this skill is useful
Provides specific YAML configurations for GitLab CI caching and artifact management that the AI wouldn't reliably generate on its own.
What it needs
About 2k tokens when loaded. Last updated 2026-07-19. 187 stars on the source repository.
What this skill does
GitLab CI - Artifacts & Caching Configure artifacts and caching for efficient pipeline execution. Artifacts Basic Artifact Configuration Artifact Reports Conditional Artifacts Artifact Dependencies Caching Basic Cache Configuration Cache Key Strategies Cache Policy Fallback Keys Distributed Cache (S3) Configure in GitLab Runner: Artifacts vs Cache Feature Artifacts Cache --------- ----------- ------- Purpose Pass data between jobs Speed up job execution Storage GitLab server Runner local or S3 Reliability Guaranteed Best effort Expiration Configurable Configurable Cross-pipeline Yes (with dependencies) Yes (with keys) Best Practices 1. Use cache for dependencies (nodemodules, vendor) 2. Use artifacts for build outputs 3. Set appropriate expiration times 4. Use lock file-based cache keys 5. Exclude source maps and unnecessary files 6. Use policy: pull for jobs that only read cache
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills thebushidocollective/artifacts-caching