skills.rest
yoshisada
yoshisadaCOMMUNITY
Explore all skills by this author →
GitHub

wheel-run

Resolve and validate local or plugin workflows, then activate wheel hooks.

Updated Mar 26, 2026
Search Tags:#automation#workflow#plugin#activation#hook#wheel-run
One-click install
npx skills add https://github.com/yoshisada/ai-repo-template --skill wheel-run
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wheel-run
Source: https://github.com/yoshisada/ai-repo-template/tree/main/plugin-wheel/skills/wheel-run
Command: npx skills add https://github.com/yoshisada/ai-repo-template --skill wheel-run

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Start a named workflow by resolving either a local workflow file or a plugin-provided workflow, validate the workflow JSON, and prepare per-agent state so wheel hooks can intercept and drive events.

Core Features & Use Cases

  • Resolve and validate workflow references (local and plugin-based).
  • Create per-agent state and activate wheel hook interception.
  • Confirm activation and provide progress checks via wheel-status and wheel-stop.

Quick Start

Provide the workflow name or plugin:workflow to start and activate the wheel-run workflow.

Frequently Asked Questions about wheel-run

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

FAQPage Schema
How do I automate starting a named workflow via hook activation?▼

You can start a workflow by providing the workflow name or plugin:workflow identifier, which resolves the reference and creates per-agent state to enable hook interception for driving automation events.

What is the mechanism behind wheel hooks for interactive event automation?▼

Wheel hooks intercept and drive Claude Code events by using per-agent state created during workflow activation, enabling validation, state preparation, and automated execution of interactive automation sequences.

Do I need a validation script before activating a workflow hook?▼

Yes, activating a workflow requires a validate-workflow script to validate the workflow JSON, along with per-agent state creation and hook-based activation to properly intercept and drive events.

How do I resolve a plugin-provided workflow versus a local workflow file?▼

Resolving a plugin-provided workflow uses the plugin:workflow naming convention, while local workflows are resolved by name, with both types requiring JSON validation before per-agent state creation and hook activation.

Can I check the progress of an activated workflow or stop it?▼

Once a workflow is activated, you can confirm activation and check progress via wheel-status, or halt execution using wheel-stop to manage the interactive automation lifecycle.

Why does my workflow activation fail during JSON validation?▼

Workflow activation fails when the validate-workflow script encounters invalid JSON structure in the local or plugin-provided workflow file, preventing per-agent state creation and hook-based interception.

Related Skills

Explore More Software Engineering Skills→
tae2089tae2089
2

agent-team-run-close

Close agent-team workflow runs after all tasks reach terminal states.

Community
Advanced
yoshisadayoshisada

wheel-status

Display live status of running workflows with step, progress, and IDs.

Community
Basic
aah-stackaah-stack

hook-development

Create Claude Code plugin hooks for event-driven automation and validation workflows.

Community
Advanced
Jarvis-ProjectsJarvis-Projects
1

hooks-manager

Develop, adapt, and validate prompt-based or command-based hooks for Claude Code.

Official
Advanced