Skip to content
Back to search

skigard-action

GitHub Action that installs a pinned, checksum-verified skigard release and runs skigard verify --strict on your agent-skill lockfile.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/ambierhq--skigard-action/badge.svg)](/listings/ambierhq--skigard-action)

HTML

<a href="/listings/ambierhq--skigard-action"><img src="/api/listings/ambierhq--skigard-action/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 80 lines
  1. # skigard-action
  2. GitHub Action that installs a **pinned, checksum-verified** [skigard](https://github.com/ambierhq/skigard) release and runs
  3. `skigard verify` on your repository: it fails the job when the approved skills, the lockfile, the installs or the generated
  4. marketplace no longer agree (an unapproved or modified skill).
  5. ```yaml
  6. name: skills
  7. on: [push, pull_request]
  8. permissions: {}
  9. jobs:
  10. verify:
  11. runs-on: ubuntu-latest
  12. permissions: {contents: read}
  13. steps:
  14. - uses: actions/checkout@<full-commit-sha> # pin actions by SHA
  15. with: {persist-credentials: false}
  16. - uses: ambierhq/skigard-action@<full-commit-sha> # v1
  17. with:
  18. version: 0.1.1
  19. # sha256: <archive checksum from the release's checksums.txt> # optional, pins the exact bytes
  20. ```
  21. Pin this action by commit SHA, like every action in a security-sensitive workflow. The `v1` tag moves; a SHA does not.
  22. ## Inputs
  23. | Input | Default | |
  24. |---|---|---|
  25. | `version` | required | skigard version without the `v`, e.g. `0.1.1`. There is no `latest`, on purpose. |
  26. | `sha256` | none | SHA-256 of the archive for the runner (`skigard_<version>_<os>_<arch>.tar.gz`, `.zip` on Windows). The download must match it. |
  27. | `args` | `--strict` | Arguments for `skigard verify`. |
  28. | `home` | `.skigard` | `SKIGARD_HOME` (project scope), relative to `working-directory`. |
  29. | `working-directory` | `.` | |
  30. | `verify` | `true` | `false` only installs skigard. |
  31. | `verify-signature` | `false` | `true` verifies the cosign signature of `checksums.txt` before it is trusted. Needs `cosign` on `PATH`; fails if it is missing. See below. |
  32. | `base-url` | the GitHub release | Asset location for mirrors and this action's tests. `https://`, `file://` or localhost only. |
  33. Output: `version`, the installed `skigard version` line.
  34. ## Verifying the signature
  35. Install cosign first, pinned by SHA, then turn the input on:
  36. ```yaml
  37. - uses: sigstore/cosign-installer@756fe2d284c7292c4e9b62c8a28f1e5629c59532 # v4.1.3
  38. - uses: ambierhq/skigard-action@<full-commit-sha> # v1
  39. with:
  40. version: 0.1.1
  41. verify-signature: true
  42. sha256: <archive checksum> # optional, can be combined
  43. ```
  44. The action does not install cosign itself, so there is no unpinned download. If `verify-signature` is true and cosign is
  45. missing, the step fails rather than silently skipping the check.
  46. ## What it does and does not do
  47. - Downloads `skigard_<version>_<os>_<arch>` and `checksums.txt` from the GitHub release, refuses on any SHA-256 mismatch
  48. (against `checksums.txt`, and against your `sha256` input when set), extracts only the binary and adds it to `PATH`.
  49. - Runs on Linux, macOS and Windows runners (x64 and arm64).
  50. - Never runs `skigard approve`: approval needs a human at a terminal and is not possible in CI.
  51. - With `verify-signature: true` it runs `cosign verify-blob --bundle checksums.txt.sigstore.json` on `checksums.txt`,
  52. requiring the certificate identity to be skigard's `release.yml` workflow at `refs/tags/v<version>` and the issuer
  53. `https://token.actions.githubusercontent.com`. Off by default; pin `sha256` for the strongest guarantee.
  54. - No telemetry; the only network access is the download above.
  55. ## Development
  56. `.github/workflows/ci.yml` has two kinds of tests, each on Linux, macOS and Windows:
  57. - `test` builds skigard from `main`, packages it like a release, serves it from localhost and runs the action against it
  58. (success, pinned checksum, wrong checksum, tampered archive, bad version, non-local URL, store drift).
  59. - `real-release` runs the action against the real published `v0.1.1` release (no `base-url`): empty project passes,
  60. the real `sha256` is accepted, a wrong one is refused, the real cosign signature verifies, a tampered `checksums.txt`
  61. and a missing cosign are refused, and an unapproved skill fails `verify --strict`.
  62. The `v1` tag is created by the maintainers after review, never automatically.
  63. MIT licensed.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.