OEM Handoff Writer

Generate structured JSON handoff packages detailing site profiles and platform requirements.

Updated Dec 7, 2025
One-click install
npx skills add https://github.com/ognjhunt/BlueprintCapturePipeline --skill oem-handoff-writer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: OEM Handoff Writer
Source: https://github.com/ognjhunt/BlueprintCapturePipeline/tree/main/.agents/skills/oem_handoff_writer
Command: npx skills add https://github.com/ognjhunt/BlueprintCapturePipeline --skill oem-handoff-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that critical site and workflow information is clearly and comprehensively packaged for Original Equipment Manufacturers (OEMs) or integrators, enabling them to accurately assess platform suitability without ambiguity.

Core Features & Use Cases

  • Structured Handoff Package Generation: Creates a detailed JSON package outlining site profiles, platform requirements, open blockers, and evidence summaries.
  • Requirement Translation: Translates complex qualification findings into clear, actionable platform requirements (dimensions, manipulation, mobility, safety).
  • Blocker Ownership Clarification: Differentiates between site-owner-resolvable and OEM-resolvable issues.
  • Use Case: After a site has been qualified as 'ready' or 'risky', this Skill generates a handoff package for a specific robot manufacturer, detailing the exact reach, payload, and safety clearances required for their platform to operate successfully.

Quick Start

Use the OEM Handoff Writer skill to generate a handoff package for the specified opportunity.

Frequently Asked Questions about OEM Handoff Writer

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

FAQPage Schema
How do I package site readiness findings for OEM robotics review?

To package site readiness for OEM review, generate a structured handoff package translating qualification findings into concrete platform requirements, detailing site profiles, dimensions, safety clearances, and open blockers.

What is an OEM handoff package in robotics integration?

An OEM handoff package in robotics integration is a structured document detailing site profiles, platform requirements, open blockers with ownership, and evidence summaries, ensuring OEMs can assess platform suitability without ambiguity.

How do I separate site-owner responsibilities from OEM responsibilities during robot deployment?

You separate site-owner responsibilities from OEM responsibilities by generating a handoff package that clarifies blocker ownership, distinguishing between site-owner-resolvable and OEM-resolvable issues for clear accountability.

How do I translate site qualification findings into platform requirements for a robot manufacturer?

Translate site qualification findings into platform requirements by generating a handoff package detailing exact reach, payload, manipulation, mobility, and safety clearances required for a specific OEM platform to operate successfully.

What should be included in a site readiness assessment for robotics integrators?

A site readiness assessment for robotics integrators should include site profiles, platform requirements, open blockers with clear ownership, and evidence summaries to validate what the OEM must assess for successful platform operation.