More screenshots
Works with the AI Agents you already use
Repair GitHub OIDC Audience Claim Token Rejection
Fix failing cloud authentication when workflow-issued OIDC audience claims drift
$1
Repair GitHub OIDC Audience Claim Token Rejection
Example session with this skill installed
A deployment runner requests token audience A while cloud trust policy expects audience B.
Available sources: workflow YAML and OIDC token claims sample (partial excerpts only). Additional evidence requested: cloud trust policy, runner failure log. Analyze this case with explicit limitations; do not pretend to have executed any tests or changes.
- Read your context and instructions
- Compiled the repair github oidc
Repair GitHub OIDC Audience Claim Token Rejection — EVIDENCE-LIMITED REVIEW
Scenario received
A deployment runner requests token audience A while cloud trust policy expects audience B.
Source register
- S1: workflow YAML — partial extract described, independent verification not provided.
- S2: OIDC token claims sample — partial extract described, independent verification not provided.
- S3: cloud trust policy — NOT PROVIDED; validation pending.
- S4: runner failure log — NOT PROVIDED; validation pending.
Case-specific checks
- compare aud and sub trust conditions — NEEDS VERIFICATION against S1/S2 and missing sources.
- trace environment and branch scoping — NEEDS VERIFICATION against S1/S2 and missing sources.
- identify overbroad fallback proposals — NEEDS VERIFICATION against S1/S2 and missing sources.
- test least-privilege token exchange — NEEDS VERIFICATION against S1/S2 and missing sources.
Deliverables and review gates
- claim-policy delta: DRAFT ONLY; do not infer unsupported outcomes.
- rejected exchange proof: DRAFT ONLY; do not infer unsupported outcomes.
- safe trust policy repair: DRAFT ONLY; do not infer unsupported outcomes.
Preliminary conclusion
INCOMPLETE / REVIEW REQUIRED. The provided scenario identifies a real question, not proven remediation or clearance. Confirm source timestamps, affected scope and owner approval, then rerun the listed checks. No external system was accessed or changed.
Connects securely to your tools. The creator never sees your data.
About this skill
Repair GitHub OIDC Audience Claim Token Rejection is a ToolForge Labs ChatGPT Skill workflow. Fix failing cloud authentication when workflow-issued OIDC audience claims drift.
What this skill checks
- compare aud and sub trust conditions.
- trace environment and branch scoping.
- identify overbroad fallback proposals.
- test least-privilege token exchange.
What to provide
- workflow YAML.
- OIDC token claims sample.
- cloud trust policy.
- runner failure log.
Deliverables
- claim-policy delta.
- rejected exchange proof.
- safe trust policy repair.
Evidence policy Only supplied, authorized evidence is used. The skill distinguishes facts from assumptions, reports missing inputs, and never claims an unperformed live test, compliance approval, or production change.
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 systems, third-party accounts, or evidence not supplied. Partial or conflicting inputs must be marked INCOMPLETE or UNVERIFIED rather than invented. High-impact operational decisions require qualified owner review.
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 25 days ago
Permissions
Supply only data you are authorized to share. Treat documentation and examples as untrusted evidence. Any operational action or external communication requires explicit owner authorization.