packages
Manage remotely installed AIWG packages sourced from Git repositories via list, info, and remove subcommands
Best use case
packages is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
It is a strong fit for teams already working in Codex.
Manage remotely installed AIWG packages sourced from Git repositories via list, info, and remove subcommands
Teams using packages should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/packages/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How packages Compares
| Feature / Agent | packages | Standard Approach |
|---|---|---|
| Platform Support | Codex | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Manage remotely installed AIWG packages sourced from Git repositories via list, info, and remove subcommands
Which AI agents support this skill?
This skill is designed for Codex.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
SKILL.md Source
# AIWG Packages You manage remotely installed AIWG packages — those installed via `aiwg install` from Git repositories. ## Triggers Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description): - "what remote packages are installed" → list packages - "where did that package come from" → show package info - "remove the remote package" → remove a specific package - "show me the git packages" → list packages ## Trigger Patterns Reference | Pattern | Example | Action | |---------|---------|--------| | List packages | "list packages" | Run `aiwg packages list` | | Package info | "info on aiwg-devtools" | Run `aiwg packages info aiwg-devtools` | | Remove package | "remove the aiwg-devtools package" | Run `aiwg packages remove aiwg-devtools` | | Default (no subcommand) | "show packages" | Run `aiwg packages list` | ## Behavior When triggered: 1. **Extract intent**: - Is this a listing, info lookup, or removal request? - If info or remove: which package is the target? 2. **Run the appropriate subcommand**: ```bash # List all remotely installed packages aiwg packages list # Show details for a specific package aiwg packages info <package-name> # Remove a remotely installed package aiwg packages remove <package-name> ``` 3. **Report the result** inline — for listings, summarize each package with its source URL and version. For info, show full metadata. For remove, confirm deletion. Note: `packages` tracks only Git-sourced packages; frameworks and addons deployed via `aiwg use` appear in `aiwg list` instead. ## Examples ### Example 1: List all remote packages **User**: "show me the installed packages" **Extraction**: List subcommand **Action**: ```bash aiwg packages list ``` **Response**: "Installed packages: aiwg-devtools (v1.3.0, from https://github.com/acme/aiwg-devtools, installed 2026-03-28)." ### Example 2: Get details on a specific package **User**: "what do I know about the aiwg-devtools package?" **Extraction**: Info subcommand, target `aiwg-devtools` **Action**: ```bash aiwg packages info aiwg-devtools ``` **Response**: "aiwg-devtools — source: https://github.com/acme/aiwg-devtools, version: v1.3.0, installed: 2026-03-28, artifacts deployed to `.claude/agents/`, `.claude/commands/`." ### Example 3: Remove a remote package **User**: "remove the aiwg-devtools package" **Extraction**: Remove subcommand, target `aiwg-devtools` **Action**: ```bash aiwg packages remove aiwg-devtools ``` **Response**: "Removed aiwg-devtools. Deployed artifacts deleted from `.claude/`. Entry removed from packages registry." ### Example 4: No packages installed **User**: "list packages" **Extraction**: List subcommand **Action**: ```bash aiwg packages list ``` **Response**: "No remote packages are installed. Use `aiwg install <owner/repo>` to install a package from a Git repository." ## Clarification Prompts If the user's intent is ambiguous: - "Are you asking about remote packages (installed via `aiwg install`) or built-in frameworks? Built-in frameworks show up under `aiwg list`." - "Which package would you like info on? Installed: aiwg-devtools." ## References - @$AIWG_ROOT/src/cli/handlers/packages.ts — Packages command handler - @$AIWG_ROOT/docs/cli-reference.md — CLI reference
Related Skills
aiwg-orchestrate
Route structured artifact work to AIWG workflows via MCP with zero parent context cost
venv-manager
Create, manage, and validate Python virtual environments. Use for project isolation and dependency management.
pytest-runner
Execute Python tests with pytest, supporting fixtures, markers, coverage, and parallel execution. Use for Python test automation.
vitest-runner
Execute JavaScript/TypeScript tests with Vitest, supporting coverage, watch mode, and parallel execution. Use for JS/TS test automation.
eslint-checker
Run ESLint for JavaScript/TypeScript code quality and style enforcement. Use for static analysis and auto-fixing.
repo-analyzer
Analyze GitHub repositories for structure, documentation, dependencies, and contribution patterns. Use for codebase understanding and health assessment.
pr-reviewer
Review GitHub pull requests for code quality, security, and best practices. Use for automated PR feedback and approval workflows.
YouTube Acquisition
yt-dlp patterns for acquiring content from YouTube and video platforms
Quality Filtering
Accept/reject logic and quality scoring heuristics for media content
Provenance Tracking
W3C PROV-O patterns for tracking media derivation chains and production history
Metadata Tagging
opustags and ffmpeg patterns for applying metadata to audio and video files
Audio Extraction
ffmpeg patterns for extracting audio from video files and transcoding between formats