Llimllib Aver
- 1 repo stars
- Updated January 29, 2026
- llimllib/aver
llimllib-aver is a Claude Code plugin that scans GitHub Actions workflow files and reports outdated action versions.
About
llimllib-aver is a Claude Code plugin that acts as a GitHub Actions version checker for developers who own their own CI YAML. Instead of manually opening every workflow file and comparing pins to marketplace releases, you register the plugin and let the agent scan workflow definitions and call out outdated actions. That matters when a stale `actions/checkout` or composite action pin fails only on main, or when you inherit a template repo and do not know which pins are years old. The tool stays narrow: it targets Actions references in workflow files, not your application package lockfiles or container bases. Use it as a quick gate during ship prep, after merging infra changes, or when onboarding a forked project. Pair the report with your normal bump-and-test loop; it does not auto-apply updates. Confidence is high for the stated scope; depth of version resolution depends on how the upstream skill implements checks against the Actions ecosystem.
- Scans repository workflow files for pinned GitHub Actions versions
- Reports which actions are behind current recommended or published versions
- Focused on CI/CD YAML, not npm, Docker base images, or app runtime deps
- Lightweight checker suited to periodic maintenance in agent-driven repos
- Single-plugin bundle from the llimllib/aver repository
Llimllib Aver by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin install llimllib-aver@llimllib/averAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| repo stars | ★ 1 |
|---|---|
| Last updated | January 29, 2026 |
| Repository | llimllib/aver ↗ |
What it does
Audit `.github/workflows` YAML and surface outdated third-party action version pins before CI breaks on a release.
Who is it for?
maintainers who ship via GitHub Actions and want a fast Actions-only version audit from Claude Code.
Skip if: Skip if you need full-stack dependency scanning (npm, Terraform, Docker) or non-GitHub CI systems.
What you get
You get an actionable list of workflow actions to bump before the next CI run or deploy.
- Report of outdated or behind-market GitHub Actions references in scanned workflows
- Prioritized list of workflow files and action names to update manually
By the numbers
- Plugin bundle count: 1
- Scope: GitHub Actions workflow files only
- Source repository: llimllib/aver
Recommended Plugins
Ahmedasmar Devops Claude SkillsA Claude Code Skills Marketplace for DevOps workflows189
Akin Ozer Cc Devops SkillsA practical skill pack for DevOps work in Claude Code and Codex.281
Antonbabenko Terraform SkillThe Claude Agent Skill for Terraform and OpenTofu - testing, modules, CI/CD, and production patterns2.2k
Aws Samples Aws Emr Utilities1 plugin45
Awudevelop Claude PluginsProduction-ready Claude Code plugins for workflow automation and productivity
Axiomhq CliThe power of Axiom on the command line.59How it compares
GitHub Actions workflow version checker, not a monorepo dependency bot or MCP integration server.
FAQ
Who is Llimllib Aver for?
and small-team developers using GitHub Actions who want Claude Code to flag stale action pins in workflow YAML without leaving the editor.
When should I use Llimllib Aver?
Before a release, after copying workflow templates, or when CI starts failing on action deprecation or major version changes.
How do I add Llimllib Aver to my agent?
Install the plugin from the llimllib/aver marketplace entry into Claude Code, open a repo with `.github/workflows`, and ask the agent to run the version check skill on those files.