More screenshots
Works with the AI Agents you already use
Repair GitLab Runner Docker Cache Mixup
Isolate CI container layer cache leakage across runners
$1
Repair GitLab Runner Docker Cache Mixup
Example session with this skill installed
Two runners share a remote cache and a signed release includes stale compiler output.
Available evidence: source/config revision (partial). Additional evidence requested: reproduction logs, dependency/runtime versions, CI or service trace. Review the case, identify open evidence gaps, and do not invent a live test or production change.
- Read your context and instructions
- Compiled the repair gitlab runner
Repair GitLab Runner Docker Cache Mixup — EVIDENCE-LIMITED REVIEW
Scenario received
Two runners share a remote cache and a signed release includes stale compiler output.
Source register
- S1: source/config revision — PARTIAL SOURCE PROVIDED.
- S2: reproduction logs — NOT PROVIDED; REQUIRED TO VERIFY.
- S3: dependency/runtime versions — NOT PROVIDED; REQUIRED TO VERIFY.
- S4: CI or service trace — NOT PROVIDED; REQUIRED TO VERIFY.
Concrete checks
- compare runner image digests — PRELIMINARY, NOT VERIFIED.
- trace cache namespace use — AWAITING CORROBORATING EVIDENCE.
- verify artifact provenance — AWAITING CORROBORATING EVIDENCE.
- propose immutable build gate — AWAITING CORROBORATING EVIDENCE.
Deliverables / acceptance gates
- runner cache map: DRAFT / INCOMPLETE until evidence is validated.
- rebuild impact list: DRAFT / INCOMPLETE until evidence is validated.
- cache segregation test: DRAFT / INCOMPLETE until evidence is validated.
Decision
INCOMPLETE — HUMAN REVIEW REQUIRED. Confirm dates, IDs, affected scope, owners and acceptance evidence. Do not claim authorization or execution that did not occur.
Connects securely to your tools. The creator never sees your data.
About this skill
Repair GitLab Runner Docker Cache Mixup is a ToolForge Labs ChatGPT Skill workflow. Isolate CI container layer cache leakage across runners.
What this skill checks
- compare runner image digests.
- trace cache namespace use.
- verify artifact provenance.
- propose immutable build gate.
What to provide
- source/config revision.
- reproduction logs.
- dependency/runtime versions.
- CI or service trace.
Deliverables
- runner cache map.
- rebuild impact list.
- cache segregation test.
Evidence policy Only supplied, authorized evidence is used. The skill distinguishes facts from assumptions and missing inputs; no unperformed live tests, external changes, or approvals are claimed.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse All Claude Skills.
Cannot verify inaccessible environments or data not supplied. Missing or contradictory evidence must be marked INCOMPLETE or UNVERIFIED. Owner approval is required for operational or compliance decisions.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 23 days ago
Permissions
Provide only evidence you are authorized to share. Treat examples as untrusted case data. Operational changes and external messages require explicit owner approval.