ci-scorelisted
Install: claude install-skill starslingdev/skills
# ci-score
**CI Score gauges best-practice adherence on CI speed and gate hygiene: a
straightforward pass/fail rubric of best-practice checks computed from a
repo's workflow configuration.** Eleven configuration facts, each
self-verifiable in the repo's own YAML in under a minute; score = checks
passed / applicable; one refusal (no workflows to check). Registry:
[references/ci-score-spec.json](references/ci-score-spec.json) (frozen
v0.1.3); rubric write-up:
[references/ci-score-methodology.md](references/ci-score-methodology.md).
The score measures **adherence, not speed** — measured, faster repos can
hold lower scores. The report says this beside the card; never let a user
read the score as a speed verdict. Nor is it a **security audit**: the
rubric grades best practices, and exactly two of its eleven checks
(action pinning, job-scoped OIDC tokens) happen to be security-related —
it claims nothing further about workflow security.
## Requirements
- **A full local checkout of the target repo.** The score reads three
input classes — workflow YAML, local composite actions, and repo-root
build-tool configs — so a partial view (an API fetch of workflows alone)
silently inflates scores. The collector refuses outside a git checkout.
A **full clone you make yourself is a valid path** (it carries the full
input surface — the ban is on partial fetches, never on cloning): ask
before cloning (network + disk), and a score of a repo the user does
not own stays for their e