install-updates

Refresh the windyroad marketplace cache and re-install updated plugins across projects.

4|1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/windyroad/agent-plugins --skill install-updates
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: install-updates
Source: https://github.com/windyroad/agent-plugins/tree/main/.claude/skills/install-updates
Command: npx skills add https://github.com/windyroad/agent-plugins --skill install-updates

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Refreshes the windyroad marketplace cache and re-installs updated plugins into the current project and into each sibling project that has windyroad plugins enabled, ensuring governance after release cycles.

Core Features & Use Cases

  • Refresh the marketplace cache to fetch the latest versions of all windyroad plugins used by the workspace.
  • Detect and update windyroad plugins across the current project and every sibling project with enabled plugins.
  • Apply ADR-driven rename-mapping migrations and provide audit-ready migration status.

Quick Start

Run the install-updates skill at the end of a release cycle to refresh the windyroad marketplace cache and update all windyroad plugins in the current project and in each sibling project.

Frequently Asked Questions about install-updates

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

FAQPage Schema
How do I refresh marketplace cache and update plugins across sibling projects?

To refresh marketplace cache and update plugins across sibling projects, run the install-updates skill to automate cache refresh, plugin discovery, and consent-gated installations across the current project and all sibling projects with windyroad plugins enabled.

When should I refresh windyroad plugins across my workspace?

You should refresh windyroad plugins at the end of a release cycle. This ensures governance after release workflows by propagating updated marketplace versions and ADR-driven rename-mapping migrations to every active sibling project.

How do plugin rename-mapping migrations work during updates?

Plugin rename-mapping migrations apply ADR-driven naming changes automatically during the update process. The skill detects renamed plugins, applies the required migrations across all sibling projects, and provides audit-ready migration status reports.

Can I update plugins in sibling projects without manual consent for each one?

Updates across sibling projects use a consent-gated install state. This means the skill discovers per-project plugin updates and applies installations based on established consent gates, allowing automated propagation across multiple active projects.

Does install-updates work with sibling projects that have no windyroad plugins enabled?

The skill only targets the current project and sibling projects that have windyroad plugins enabled. Sibling projects without enabled windyroad plugins are skipped during the automated marketplace cache refresh and plugin update propagation.

What is the best way to automate end-of-release plugin governance for multiple projects?

The best way to automate end-of-release plugin governance is running a skill that refreshes the windyrad marketplace cache, detects per-project plugin updates, applies rename-mapping migrations, and executes consent-gated installs across all active sibling projects simultaneously.