Install reusable agent workflows with AIWG
Use AIWG to install and verify reusable project context, specialist workflows, skills, rules, and MCP utilities across Claude Code, Codex, Copilot, Cursor, and other supported agent providers.
npx skills add agentskillexchange/skills --skill install-reusable-agent-workflows-with-aiwg
Use AIWG when an operator wants an agent to set up repeatable project context and specialist workflows in a repository instead of manually copying prompt files, rules, skills, and provider-specific configuration.
What this skill actually does
The repeatable workflow is to ask the current AI provider to follow AIWG’s setup manifest, have it explain the plan, preserve existing work, install or repair the AIWG layout, run aiwg use all for the chosen provider, refresh indices, regenerate project context, and verify whether the provider needs a reload. For manual use, install the CLI with npm and run aiwg use all –provider from the project directory.
Invoke this instead of using an AI tool normally when the project needs durable cross-session context, repeatable specialist workflows, provider-readable rules, or a controlled install/repair path that can be checked by the agent and operator. The scope boundary is the project onboarding and workflow-installation procedure around AIWG artifacts and CLI verification; it is not a generic listing for an agent framework, SDK, prompt library, or model provider.
Inputs and prerequisites: Node.js 20 or newer, the aiwg npm package or AIWG setup manifest, a project workspace, and a supported provider such as Claude Code, Codex, Copilot, Cursor, OMP, or Pi.
Setup notes: Agent-led setup can follow https://aiwg.io/setup.aiwg.yaml. Manual setup uses npm i -g aiwg, then aiwg use all –provider in the target project. Use aiwg status or aiwg doctor for maintenance and troubleshooting when needed.
Source and verification boundary: use https://github.com/jmagly/aiwg and https://aiwg.io as the canonical references before running the workflow; keep provider choices, file changes, CLI commands, and verification output reviewable against those upstream sources.
Framework fit: publish this as a Multi-Framework workflow because upstream explicitly targets multiple agent providers and the approved skill describes a concrete install-and-verify operator workflow rather than treating AIWG as a generic platform.