package-all-plugins
Batch package every plugin in the workspace in a single release-prep operation
What this skill does
# Package All Plugins You run `package-plugin` for every plugin in the workspace in a single batch operation. Used for release preparation to generate all plugin packages at once. ## Triggers Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description): - "package everything for the release" → batch package all plugins - "build all plugin archives" → batch package all plugins - "release prep — package the plugins" → batch package all plugins - "bundle all the plugins before tagging" → batch package all plugins ## Trigger Patterns Reference | Pattern | Example | Action | |---------|---------|--------| | Package all | "package all plugins" | Run `aiwg package-all-plugins` | | Bundle all | "bundle all plugins" | Run `aiwg package-all-plugins` | | Publish all | "publish all plugins" | Run `aiwg package-all-plugins --publish` | | Batch package | "batch package plugins" | Run `aiwg package-all-plugins` | | Dry run all | "validate all plugins before packaging" | Run `aiwg package-all-plugins --dry-run` | | Skip failures | "package all, skip broken ones" | Run `aiwg package-all-plugins --continue-on-error` | ## Behavior When triggered: 1. **Extract intent**: - Should packages be published after creation, or archived locally only? - Should the batch abort on first failure, or continue and report all failures? - Is this a dry run (validate only)? 2. **Run the appropriate command**: ```bash # Package all plugins (archive only, no publish) aiwg package-all-plugins # Validate all plugins — no archives created aiwg package-all-plugins --dry-run # Package and publish all to marketplace aiwg package-all-plugins --publish # Continue on individual failures, report all at end aiwg package-all-plugins --continue-on-error # Specify output directory for all archives aiwg package-all-plugins --output dist/plugins/ # Bump all versions before packaging aiwg package-all-plugins --bump patch ``` 3. **Report the result** — list each plugin with its status (packaged, failed, skipped), total count, and any errors. ## Output Format ``` Packaging all plugins (4)... sdlc ✓ packaged dist/plugins/sdlc-2026.4.0.aiwg-plugin.tar.gz voice ✓ packaged dist/plugins/voice-2026.4.0.aiwg-plugin.tar.gz marketing ✓ packaged dist/plugins/marketing-2026.4.0.aiwg-plugin.tar.gz utils ✗ failed validate-metadata: 1 error in soul-blend/SKILL.md Packaged: 3 / 4 Failed: 1 (utils) ``` ## Failure Behavior By default (`--abort-on-error`), the batch stops at the first failure and reports the error. Use `--continue-on-error` to package all plugins and collect all errors for a single remediation pass. ## Relationship to `package-plugin` `package-all-plugins` is a thin loop over `package-plugin`. Each plugin runs through the same validation and packaging logic as a single `package-plugin` call. Flags like `--dry-run`, `--publish`, and `--bump` are forwarded to each plugin invocation. ## Examples ### Example 1: Release preparation **User**: "Package all plugins for the release" **Extraction**: Full batch, no publish **Action**: ```bash aiwg package-all-plugins ``` **Response**: "Packaged 4/4 plugins. Archives in dist/plugins/: sdlc-2026.4.0, voice-2026.4.0, marketing-2026.4.0, utils-2026.4.0. All metadata validation passed." ### Example 2: Validate everything before tagging **User**: "Validate all plugins before I tag the release" **Extraction**: Dry-run requested **Action**: ```bash aiwg package-all-plugins --dry-run ``` **Response**: "Dry run: 4 plugins validated. 3 passed. 1 error: utils plugin — soul-blend/SKILL.md missing required field `id`. Fix and re-run." ### Example 3: Package and publish in one step **User**: "Package and publish everything for the release" **Extraction**: Batch package and publish **Action**: ```bash aiwg package-all-plugins --publish ``` **Response**: "Packaged and published 4/4 plugins to the AIWG marketplace. sdlc, voice, marketing, utils — all at v2026.4.0." ### Example 4: Continue through failures **User**: "Package all plugins but don't stop if one fails — I want to see all the errors at once" **Extraction**: Batch with `--continue-on-error` **Action**: ```bash aiwg package-all-plugins --continue-on-error ``` **Response**: "Packaged 3/4 plugins. 1 failure: utils — validate-metadata error in soul-blend/SKILL.md line 4 (missing `id`). All other packages created in dist/plugins/." ## References - @$AIWG_ROOT/src/cli/handlers/utilities.ts — Command handler - @$AIWG_ROOT/docs/cli-reference.md — CLI reference - @$AIWG_ROOT/agentic/code/addons/aiwg-utils/skills/package-plugin/SKILL.md — Single-plugin packaging
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.