Is ci-workflow-doctor safe to install?

SaferSkills independently audited ci-workflow-doctor (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 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 · 0 flagged

Securityscore 100 · 0 findings

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

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/ci-workflow-doctor/SKILL.md · 1 file

skills/ci-workflow-doctor/SKILL.md1.7 KB · Markdown

name: ci-workflow-doctor

description: Lint GitHub Actions workflows for deploy-breaking and security mistakes. Use whenever the user writes or edits a workflow file, mentions GitHub Actions, sets up CI/CD, complains that deploys land out of order, or before the first automated deploy of a project. Also run it during any security review of a repo. Runs fully offline — no API keys, no network, no credentials.

ci-workflow-doctor

Part of shipsafe — offline deploy-safety skills. Every script is stdlib-only Python 3.8+; nothing leaves the machine.

python3 scripts/lint_workflows.py <repo_root> [--json]   # finds .github/workflows itself

Checks:

PR_TARGET_WITH_CHECKOUT (critical) — pull_request_target + checkout of the PR head runs untrusted fork code WITH repo secrets. This is the classic GitHub Actions exfiltration pattern; fix immediately.
MUTABLE_ACTION_REF (high) — third-party actions pinned to tags/branches can be force-pushed by a compromised maintainer. Pin to a 40-char commit SHA. Official actions/* are exempt.
MISSING_CONCURRENCY (high) — deploy jobs without a concurrency group let two pushes deploy in parallel; the OLDER build can finish last and win. The fix block to suggest is in the script output.
SECRET_IN_RUN (high) — ${{ secrets.X }} interpolated into run: scripts leaks via shell tracing; pass via env: instead.
NO_TIMEOUT / UNPINNED_RUNNER (low) — hygiene for deploy reliability.

Implementation note: parsing is line-structured and heuristic (zero dependencies, runs anywhere) — on exotic YAML, verify a finding against the file before asserting it.

Exit codes: 0 clean, 1 findings.

All paths below are relative to this skill's directory (ci-workflow-doctor/).

ci-workflow-doctor— agent skill

Is ci-workflow-doctor safe to install?

ci-workflow-doctor

Audit the pieces. Scan the whole. Decide.