finops-caches

Analyze GitHub Actions cache usage - size breakdown, cache key patterns, branch distribution, and stale cache detection.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "finops-caches" with this command: npx skills add laurigates/claude-plugins/laurigates-claude-plugins-finops-caches

/finops:caches

Analyze GitHub Actions cache usage - size breakdown, cache key patterns, branch distribution, and stale cache detection.

Context

  • Current repo URL: !git remote get-url origin

Parameters

Parameter Description Default

repo

Repository in owner/name format Current repository

org:orgname

Analyze org-wide cache usage

Execution

bash "${SKILL_DIR}/scripts/cache-analysis.sh" $ARGS

Output Format

=== Cache Analysis: org/repo ===

Summary: 45 caches, 2340MB used 23% of 10GB limit

=== By Key Prefix === node-modules: 12 caches, 1200MB playwright: 8 caches, 800MB turbo: 15 caches, 300MB

=== By Branch === main: 10 caches, 500MB develop: 8 caches, 400MB PR 123: 3 caches, 150MB PR 118: 3 caches, 140MB

=== Largest Caches === node-modules-linux-abc123: 180MB playwright-linux-def456: 150MB

=== Stale Caches (>7 days old) === 8 stale caches, 450MB reclaimable Oldest: 2025-01-15T10:30:00Z

=== PR Branch Caches === 12 PR caches, 580MB (check if PRs are merged/closed)

Post-actions

Based on findings, suggest:

  • High % of limit -> Clean up stale caches, review key strategies

  • Many PR caches -> Add cache cleanup workflow for closed PRs

  • Large single caches -> Consider splitting or compressing

  • Stale caches -> Provide cleanup command:

Delete stale caches

gh api "/repos/$REPO/actions/caches?per_page=100"
--jq '.actions_caches[] | select(.last_accessed_at < "CUTOFF") | .id' |
while read id; do gh api -X DELETE "/repos/$REPO/actions/caches/$id"; done

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

python-code-quality

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

python-development

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

python-testing

No summary provided by upstream source.

Repository SourceNeeds Review