Plugin · Claude Code · DevOps

Llimllib Aver

llimllib-aver is a Claude Code plugin for the Ship phase that scans GitHub Actions workflow files and reports outdated action versions.

by llimllib · github.com/llimllib/aver

Audit `.github/workflows` YAML and surface outdated third-party action version pins before CI breaks on a release.

1
GitHub stars
0
Installs
0
Community votes
One vote per signed-in builder - it helps surface the tools the community actually relies on.
Install

Add it to Claude Code

Install the plugin in Claude Code. One command, paste-ready.

Install the plugin
/plugin install llimllib-aver@llimllib/aver
Add to ClaudeUse the Agent APISkillselion is itself an MCP server - your agent can fetch this config directly.
Agent API

Built to be called by your agent

Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.

Retrieve this entry with skillselion.get_details("plugin:llimllib/aver") and the paste-ready config with skillselion.get_install_config("plugin:llimllib/aver").

About

What it does

llimllib-aver is a Claude Code plugin that acts as a GitHub Actions version checker for solo builders 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.

Highlights

  • 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

Why builders use it

Outdated GitHub Actions pins hide in YAML until a failed workflow blocks your release.

You get an actionable list of workflow actions to bump before the next CI run or deploy.

At a glance

  • Type - Plugin in DevOps.
  • Adoption - 0 installs, 1 stars, 0 votes.

FAQ

Who is llimllib-aver for?

Solo and small-team builders 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.

Discussion

Comments

Share how you use llimllib-aver, gotchas, or tips for other indie builders.

No comments yet - be the first to share how you use it.

This week for builders

Five minutes, every Monday — the tools, releases and tactics for shipping solo.

unsubscribe anytime.