bomb-ecom-os-commander

Route user intents to specialist sub-skills via REGISTRY.md without executing pipeline operations.

1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/williamsforeal/Cyclone-SS --skill bomb-ecom-os-commander
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bomb-ecom-os-commander
Source: https://github.com/williamsforeal/Cyclone-SS/tree/main/global-skills/bomb-ecom-os-commander
Command: npx skills add https://github.com/williamsforeal/Cyclone-SS --skill bomb-ecom-os-commander

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the coordination problem of running a multi-system BOMB ECOM ad automation stack by routing each user request to the correct specialist sub-skill without executing actions itself.

Core Features & Use Cases

  • Cross-skill dispatch for the 4-layer ad pipeline: Routes requests across Brand Brain, static/UGC generators, Airtable operations, and n8n workflows, including cross-skill operations.
  • Brand-aware safety gating: Confirms active brand context before routing and prevents proceeding without required context.
  • Registry-driven sub-skill selection: Reads REGISTRY.md at session start to determine which sub-skills are active vs deferred, then routes accordingly.
  • Operational guardrails: Avoids fabricating Airtable record IDs, n8n workflow IDs, or execution counts, and ensures routing rather than direct execution.

Quick Start

Ask: "Generate ads for my brand" and ensure the brand is specified (Abundria/Palm Aura, Pit Smith Co., or williamsforeal) so the commander can route the request to the right sub-skill after reading REGISTRY.md.

Frequently Asked Questions about bomb-ecom-os-commander

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

FAQPage Schema
How do I route ad generation requests across multiple automation sub-skills?▼

Ad generation requests are routed by reading a registry file to determine active sub-skills, confirming brand context, and delegating the intent to the appropriate specialist dispatcher without directly executing pipeline operations.

What is cross-skill dispatch for an n8n and Airtable ad pipeline?▼

Cross-skill dispatch is a coordination mechanism that routes user intents across a multi-layer ad automation stack, triggering n8n workflows and Airtable ops by delegating to specialist sub-skills rather than executing actions directly.

Do I need to specify a brand before triggering Airtable operations and n8n workflows?▼

Yes, you must specify an active brand context before proceeding. The commander enforces brand-aware safety gating to prevent routing ad generation or pipeline operations without required brand confirmation.

Can I use this dispatcher to directly execute Airtable record creation and n8n workflow triggering?▼

No, you cannot use this dispatcher to directly execute operations. It applies operational guardrails to avoid fabricating Airtable record IDs or n8n workflow IDs, ensuring it routes tasks to sub-skills instead of acting directly.

What's the best way to manage a multi-layer ad automation stack with deferred sub-skills?▼

The best way to manage a multi-layer ad automation stack is using a registry-driven selection process that reads REGISTRY.md at session start to identify which sub-skills are active versus deferred, then routes intents accordingly.