gha 96/100 — SaferSkills

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

30.8 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 1 flagged

Securityscore 88 · 1 finding

MEDIUMInstruction telling the agent not to ask for approvalSS-SKILL-INJECT-DONT-ASK-01 · Prompt injection · README.md

MEDIUM — it fires on intent; the real damage depends on the host agent's own approval-gating.

Why it matters

The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.

The exact value spotted

excerptREADME.md· markdown

860So sometimes you want to check the code and ask it to simplify things. You could fix things

… (108 chars elided on L860)

861

862Some people say if you write code only through AI, you'll never understand it. But that's on

… (108 chars elided on L862)

863

864Note that this applies to prose as well. Claude Code often tries to summarize previous parag

… (108 chars elided on L864)

Occurrences

1 occurrence · at L862

How to fix

Remove the approval-skipping instruction, or scope it narrowly to a specific safe, reversible action.

Delete blanket "don't ask / no need to confirm" directives from the skill.
If the skill is a genuine autonomous job, restrict the opt-out to a named non-destructive action rather than all actions.

Framework references

OWASPLLM01 ATLASAML.T0051

Trace & refs

ruleSS-SKILL-INJECT-DONT-ASK-01sha256ce5204b52388d24f…rubric 365aacaView on GitHub

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/gha/SKILL.md · 1 file

skills/gha/SKILL.md2.5 KB · Markdown

name: gha

description: Analyze GitHub Actions failures and identify root causes

argument-hint: <url>

Investigate this GitHub Actions URL: $ARGUMENTS

Use the gh CLI to analyze this workflow run. Your investigation should:

Get basic info & identify actual failure:

What workflow/job failed, when, and on which commit?
CRITICAL: Read the full logs carefully to find what SPECIFICALLY caused the exit code 1
Distinguish between warnings/non-fatal errors vs actual failures
Look for patterns like "failing:", "fatal:", or script logic that determines when to exit 1
If you see both "non-fatal" and "fatal" errors, focus on what actually caused the failure

Check flakiness: Check the past 10-20 runs of THE EXACT SAME failing job:

IMPORTANT: If a workflow has multiple jobs, you must check history for the SPECIFIC JOB that failed, not just the workflow
Use gh run list --workflow=<workflow-name> to get run IDs, then gh run view <run-id> --json jobs to check the specific job's status
Is this a one-time failure or recurring pattern for THIS SPECIFIC JOB?
What's the success rate for THIS JOB recently?
When did THIS JOB last pass?

Identify breaking commit (if there's a pattern of failures for the specific job):

Find the first run where THIS SPECIFIC JOB failed and the last run where it passed
Identify the commit that introduced the failure
Verify by checking: does THIS JOB fail in ALL runs after that commit? Does it pass in ALL runs before?
If verified, report the breaking commit with high confidence

Root cause: Based on logs, history, and any breaking commit, what's the likely cause?

Focus on what ACTUALLY caused the failure (not just any errors you see)
Verify your hypothesis against the logs and failure logic

Check for existing fix PRs: Search for open PRs that might already address this issue:

Use gh pr list --state open --search "<keywords>" with relevant error messages or file names
Check if any open PR modifies the failing file/workflow
If a fix PR exists, note it in your report and skip the recommendation section

Write a final report with:

Summary of failure (what specifically triggered the exit code 1)
Flakiness assessment (one-time vs recurring, success rate)
Breaking commit (if identified and verified)
Root cause analysis (based on the ACTUAL failure trigger)
Existing fix PR (if found - include PR number and link)
Recommendation (skip if fix PR already exists)

gha— agent skill

Is gha safe to install?

Audit the pieces. Scan the whole. Decide.