bp-intent-create

To auto-generate an intent-mapping.yaml for gateway routing, you can use a skill that discovers available skills, extracts trigger keywords from descriptions, detects overlaps, designs negative keywords, and outputs 3VL rules.

Keyword disambiguation for overlapping gateway skills works by detecting trigger keyword overlaps from skill descriptions and designing negative keywords to create precise 3VL routing rules.

The best way to route user input to the correct plugin skill is by generating a complete intent-mapping.yaml that derives triggers from skill descriptions and organizes 3VL keyword rules.

You extract trigger keywords from skill descriptions for intent mapping by using an automated tool that discovers all skills within a plugin and parses their text to identify relevant routing triggers.

The generated intent-mapping.yaml file should be placed at the destination path commands/{plugin-name}/intent-mapping.yaml within your gateway plugin directory structure.

Yes, intent mapping supports fallback handling for unmatched user input. The generated intent-mapping.yaml includes fallback handling configurations alongside the plugin template and 3VL rules.