version

Compare source, installed, and release versions of the compound-workflows plugin.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/adamfeldman/compound-workflows --skill version-adamfeldman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: version
Source: https://github.com/adamfeldman/compound-workflows/tree/main/plugins/compound-workflows/skills/version
Command: npx skills add https://github.com/adamfeldman/compound-workflows --skill version-adamfeldman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps users understand the version status of the compound-workflows plugin by comparing the source code version, the installed version, and the latest release version.

Core Features & Use Cases

  • Version Comparison: Displays the current status of the plugin's version.
  • Actionable Insights: Highlights if the plugin is outdated (STALE) or if new releases are available (UNRELEASED).
  • Use Case: A user wants to ensure they are running the latest version of the compound-workflows plugin and needs to know if an update is available.

Quick Start

Run the version check script to see the current plugin version status.

Frequently Asked Questions about version

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check the installed version status of a plugin?

This Skill checks the installed version status of a plugin by comparing the source, installed, and release versions via a bash script to report if updates are needed.

What is the best way to compare source and release versions for plugin maintenance?

The best way to compare source and release versions for plugin maintenance is executing a version comparison script that evaluates version states and highlights actionable update insights.

How do I know if my compound-workflows plugin is outdated?

You can determine if your compound-workflows plugin is outdated by running a version check script that flags the status as STALE if the installed version lags behind the source or release version.

Does the version check script require any external dependencies to run?

No, the version check script does not require external dependencies to run, relying solely on executing a standard bash script to compare the installed, source, and release versions.

Why does my plugin version status show as UNRELEASED?

Your plugin version status shows as UNRELEASED when the version comparison script detects that new release versions are available but have not yet been applied to your installed environment.