Shared Traffic Reviewer

Classify traffic types and verify clearance in shared robot-human environments.

Updated Dec 7, 2025
One-click install
npx skills add https://github.com/ognjhunt/BlueprintCapturePipeline --skill shared-traffic-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Shared Traffic Reviewer
Source: https://github.com/ognjhunt/BlueprintCapturePipeline/tree/main/.agents/skills/shared_traffic_reviewer
Command: npx skills add https://github.com/ognjhunt/BlueprintCapturePipeline --skill shared-traffic-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical safety challenge of ensuring robots and humans can safely share operational spaces, preventing accidents in environments with mixed traffic like warehouses and manufacturing floors.

Core Features & Use Cases

  • Traffic Classification: Categorizes every route segment by its traffic type (humanoid-only, shared pedestrian, shared forklift, shared AGV, shared mixed).
  • Clearance Verification: Applies specific minimum width requirements based on traffic type to ensure safe passage.
  • Intersection Safety: Checks for visibility aids and clear sightlines at intersections.
  • Speed Governance: Flags potential issues with operating speeds in shared zones.
  • Risk Assessment: Identifies high-risk traffic patterns and assesses the presence of traffic management protocols.
  • Use Case: A robot is being deployed in a busy warehouse. This Skill analyzes the planned routes, identifies aisles shared with forklifts, verifies sufficient clearance, and flags any blind corners or lack of safety protocols, ensuring the robot's operation is safe.

Quick Start

Analyze the provided site intake and route graph data to classify traffic types and verify clearance for all shared zones.

Frequently Asked Questions about Shared Traffic Reviewer

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

FAQPage Schema
How do I assess robot safety in shared traffic warehouse environments?

To assess robot safety in shared traffic environments, you classify route segments by traffic type and apply clearance checks. This mitigates risks by verifying sufficient width, intersection visibility, and speed compatibility against OSHA guidelines and ISO 3691-4.

What is needed to verify clearance and visibility for automated route graphs?

Verifying clearance and visibility for route graphs requires detailed input artifacts including site intake data, geometry evidence, and blocker registers. These inputs allow the system to evaluate intersection sightlines and apply minimum width requirements for shared pedestrian or forklift zones.

How do I classify traffic types for manufacturing floor route segments?

Classifying traffic types for route segments involves categorizing each path as humanoid-only, shared pedestrian, shared forklift, shared AGV, or shared mixed. This classification determines the specific minimum clearance and speed governance rules applied to ensure safe passage.

Does this traffic analysis tool check speed compatibility in shared AGV zones?

Yes, this traffic analysis tool checks speed compatibility in shared AGV zones. It flags potential operating speed issues and assesses traffic management protocols to ensure speed governance is maintained in mixed traffic manufacturing areas.

Can I use this for warehouse dock areas with shared forklift traffic?

Yes, you can use this for warehouse dock areas with shared forklift traffic. It evaluates route segments, intersection visibility, and clearance requirements specifically designed for safety-critical scenarios involving mixed forklift and AGV traffic.

What are the limitations of using route graph data for intersection safety checks?

A limitation of using route graph data for intersection safety checks is the strict requirement for comprehensive input artifacts. Without complete geometry evidence, site intake details, and blocker registers, the system cannot accurately assess visibility aids or clear sightlines.