Index of every page on this site: llms.txt
All skills
Run it yourself

Audits a repository's GitHub Actions workflows for CI optimization opportunities — missing caches, redundant setup, sleep-based readiness, long test jobs without sharding, full-history checkout, dead env vars, build-cache misconfig, and ~60 more patterns across caching, redundancy, parallelization, conditional execution, trigger scope, and hidden failures. Use when: (1) analyzing a repo's CI for optimization opportunities, (2) producing a prioritized report with measured wall-clock and runner-minute savings, (3) re-auditing after upstream CI changes. Do not trigger for: general CI setup help, writing new workflows from scratch, non-GitHub-Actions CI systems, or security/posture audits — use `ci-secure` for those.

Use this Skill: https://skilld.dev/gh/starslingdev/skills/ci-speedup

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencespatternsopt3-turbo-cache-misconfiguration.md

≈404 tokens on demand. Your agent reads this file only when SKILL.md points to it.

OPT3 — Read-Only Turbo Cache (never populated)

TL;DR: A job sets TURBO_CACHE: remote:ro — it READS the remote cache but never writes it. If nothing else writes the cache, it stays cold and every task re-executes.

Anti-pattern: remote:ro means "remote only, read-only" — local cache is skipped AND this job never populates the remote cache. That's correct ONLY when a separate writer (e.g. the main-branch build with remote:rw) keeps it warm; a read-only cache with no writer is always a miss.

NOTE — remote:rw is NOT flagged. On ephemeral CI runners (GitHub-hosted and most self-hosted) the local file-system cache does not persist between runs, so remote:rw (remote-only, read-write — the cross-run cache that actually helps) is the correct config, not a misconfiguration. OPT3 only flags the read-only (ro) case. The cross-workflow read-only-reader / read-write-writer race is OPT37's territory, not this single-file check.

Detection heuristic:

grep -rn 'TURBO_CACHE' .github/workflows/   # flag only value 'remote:ro'

Fix: If this job should populate the cache, set remote:rw. If it intentionally reads a cache a sibling job/workflow writes, confirm that writer exists (see OPT37) — otherwise the cache is never warm.


Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 alert2d3 checks · Risk SAFE
  • Gen Agent Trust Hub2d

    The skill is a robust CI optimization tool that audits GitHub Actions workflows. It identifies performance bottlenecks using deterministic logic and provides analysis of job logs. While it processes untrusted log data, it includes strong defensive instructions to mitigate indirect prompt injection. A minor best-practice issue regarding unsafe YAML loading was identified in a utility script.

  • Socket2d

    No alerts

  • Snyk2d

    Risk: CRITICAL · 2 issues

Signed by skilld at 9a84115. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 16 hours ago.

Activeupdated yesterday

README badge

README badge for starslingdev/skills/ci-speedup