More screenshots
Works with the AI Agents you already use
Repair Terraform Provider Lock Platform Mismatch
Diagnose provider lock mismatch between CI and developer OS
$1
Repair Terraform Provider Lock Platform Mismatch
Example session with this skill installed
CI on Linux fails install because lock file contains only Darwin platform checksums.
Available evidence: configuration and lock snapshots (partial). Additional evidence requested: platform/runtime versions, CI job logs, upgrade audit trail. 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 terraform provider
Repair Terraform Provider Lock Platform Mismatch — EVIDENCE-LIMITED REVIEW
Scenario received
CI on Linux fails install because lock file contains only Darwin platform checksums.
Source register
- S1: configuration and lock snapshots — PARTIAL SOURCE PROVIDED.
- S2: platform/runtime versions — NOT PROVIDED; REQUIRED TO VERIFY.
- S3: CI job logs — NOT PROVIDED; REQUIRED TO VERIFY.
- S4: upgrade audit trail — NOT PROVIDED; REQUIRED TO VERIFY.
Concrete checks
- compare provider selections — PRELIMINARY, NOT VERIFIED.
- inspect lock hash variants — AWAITING CORROBORATING EVIDENCE.
- identify unchecked upgrade drift — AWAITING CORROBORATING EVIDENCE.
- propose controlled multi-platform lock regen — AWAITING CORROBORATING EVIDENCE.
Deliverables / acceptance gates
- provider lock matrix: DRAFT / INCOMPLETE until evidence is validated.
- CI failure rationale: DRAFT / INCOMPLETE until evidence is validated.
- reproducible repair plan: 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 Terraform Provider Lock Platform Mismatch is a ToolForge Labs ChatGPT Skill workflow. Diagnose provider lock mismatch between CI and developer OS.
What this skill checks
- compare provider selections.
- inspect lock hash variants.
- identify unchecked upgrade drift.
- propose controlled multi-platform lock regen.
What to provide
- configuration and lock snapshots.
- platform/runtime versions.
- CI job logs.
- upgrade audit trail.
Deliverables
- provider lock matrix.
- CI failure rationale.
- reproducible repair plan.
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.