Is check-ci safe to install?

SaferSkills independently audited check-ci (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/check-ci/SKILL.md · 1 file

skills/check-ci/SKILL.md1.6 KB · Markdown

name: check-ci

description: Use this workflow skill for PR CI triage: inspect failing or pending checks, mergeability, and related review feedback, then reproduce likely failures locally and summarize next steps.

Check CI

Use this for PR health checks and failure triage.

This is narrower than pr-analysis: prefer check-ci when the main question is why checks are failing or blocked.
This is read-only unless the user also asks to fix the problem.

Workflow

Resolve the PR number from an argument or the current branch with gh pr view --json number.
Inspect checks with gh pr checks <pr> and save verbose output to scratch/check-ci-<pr>.log when needed.
If checks failed, fetch failed-job logs with gh run view <run-id> --log-failed.
Check mergeability and branch drift with gh pr view --json mergeable,mergeStateStatus plus local git fetch origin.
Gather review comments and unresolved feedback that may explain the failing state.
Reproduce the most likely failure locally using the narrowest relevant command.
Summarize current state, root cause, local repro status, and next fix steps.

Repo Validation Mapping

TypeScript lint or build: bun run lint, bun run build
Tests: bun test or bun test <file>
Fast repo checks: bash scripts/all_fast_validate_checks.sh
Android: (cd android && ./gradlew <task>)
iOS: bash scripts/ios/swift-build.sh or bash scripts/ios/swift-test.sh

Output Structure

Current CI state
Failing checks and likely root cause
Mergeability or conflict status
Review feedback that is still actionable
Recommended next action

check-ci— agent skill

Is check-ci safe to install?

Check CI

Workflow

Repo Validation Mapping

Output Structure

Audit the pieces. Scan the whole. Decide.