bp-gateway

Discover SKILL.md definitions and generate gateway artifacts with 3VL intent routing.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/hiivmind/hiivmind-blueprint --skill bp-gateway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bp-gateway
Source: https://github.com/hiivmind/hiivmind-blueprint/tree/main/skills/bp-gateway
Command: npx skills add https://github.com/hiivmind/hiivmind-blueprint --skill bp-gateway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unified gateway orchestration for multi-skill plugins by automatically discovering skills and routing user intents to the correct skill using 3VL. This eliminates manual wiring and inconsistency when scaling to multiple capabilities.

Core Features & Use Cases

  • Discover all skills by locating SKILL.md files and extracting their names and descriptions.
  • Extract keywords and design 3VL intents to route to the appropriate skill.
  • Generate gateway artifacts: gateway command markdown, intent-mapping.yaml, and workflow.yaml.
  • Validate skill coverage and handle ambiguity with a built-in menu when needed.
  • Use case: a plugin with 4+ skills auto-generates a gateway that routes to the correct skill based on user input.

Quick Start

Run the gateway tool on your plugin to generate the gateway command, intent-mapping, and workflow files.

Frequently Asked Questions about bp-gateway

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

FAQPage Schema
How do I route user intents to different skills in a multi-skill plugin?

A unified gateway routes user intents across multiple skills by discovering SKILL.md files and constructing a 3VL intent-mapping structure to direct input to the correct skill automatically.

What is the best way to orchestrate multiple plugin skills without manual wiring?

Automated gateway orchestration eliminates manual wiring by discovering skills, extracting keywords, and generating intent-mapping.yaml and workflow.yaml artifacts to manage routing across multiple capabilities.

How does 3VL intent mapping resolve ambiguity in skill routing?

3VL intent mapping resolves routing ambiguity by detecting keyword overlaps across discovered skills and triggering a built-in user menu to disambiguate the target intent when needed.

Do I need SKILL.md frontmatter to use automated skill discovery?

Yes, automated skill discovery requires SKILL.md frontmatter because the gateway extracts the name and description fields from the frontmatter to identify and map available capabilities.

What artifacts are generated when building a unified skill gateway?

Building a unified skill gateway generates gateway command markdown, intent-mapping.yaml, and workflow.yaml artifacts, which collectively define routing logic and validate skill reachability across the plugin.

Can I validate skill reachability after generating a gateway?

Yes, you can validate skill reachability after generating a gateway because the tooling checks that all discovered skills are accessible and validates coverage to prevent orphaned skills.