Skip to content
Skills Library
Other · Planning

integration

/integration

Robot-dog integration, bring-up, HIL planning, prototype readiness, hardware gate, assembly test, first power-on checklist, data capture, and physical test safety validation. Use this skill when the user asks whether a prototype is ready for assembly, power-on, HIL, bring-up, hardware testing, or real-world data collection after digital-twin gates.

Licence
Apache-2.0
Last repository change
08.06.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
20
Scripts
7
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 08.06.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What to check before installing
  • 7 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/check_bringup_readiness.py, scripts/integration_common.py, scripts/write_hil_plan.py, tests/conftest.py, tests/test_bringup_readiness.py, tests/test_hil_plan.py, tests/test_smoke.py

What it does and when to use it

Robot-dog integration, bring-up, HIL planning, prototype readiness, hardware gate, assembly test, first power-on checklist, data capture, and physical test safety validation. Use this skill when the user asks whether a prototype is ready for assembly, power-on, HIL, bring-up, hardware testing, or real-world data collection after digital-twin gates.

Original author description

Robot-dog integration, bring-up, HIL planning, prototype readiness, hardware gate, assembly test, first power-on checklist, data capture, and physical test safety validation. Use this skill when the user asks whether a prototype is ready for assembly, power-on, HIL, bring-up, hardware testing, or real-world data collection after digital-twin gates.

How it works

  1. When To Use
  2. Workflow
  3. Commands
  4. Rules
  5. References
Original SKILL.md headings · 47 lines, 211 words
SKILL.md preview
---
name: integration
description: |
  Robot-dog integration, bring-up, HIL planning, prototype readiness, hardware
  gate, assembly test, first power-on checklist, data capture, and physical test
  safety validation. Use this skill when the user asks whether a prototype is
  ready for assembly, power-on, HIL, bring-up, hardware testing, or real-world
  data collection after digital-twin gates.
---

# integration

This skill checks whether a robot-dog project is ready for safe physical
integration. The MVP is a dry-run gate: it writes bring-up/HIL checklists and
blocks unsafe first power-on conditions. It does not power hardware, flash
firmware, move actuators, or collect real logs.

## When To Use

Use this skill for:

- Physical prototype readiness checks after digital-twin validation.
- First power-on and bring-up checklists.
- HIL/test bench planning.
- Required human gates before assembly, power, firmware flash, and motor motion.
- Data-capture plan for sim2real calibration.

## Workflow

1. Read `<project>/integration_plan.yaml`.
2. Check digital-twin, manufacturing, safety, firmware, assembly, and testbench prerequisites.
3. Generate bring-up report, HIL plan, and data-capture checklist.
4. Return non-zero when any required human or safety gate is missing.

## Commands

```bash
python skills/integration/scripts/check_bringup_readiness.py skills/integration/examples/quadruped_mvp
python skills/integration/scripts/write_hil_plan.py skills/integration/examples/quadruped_mvp
```

## Rules

- Never execute physical actions. This skill only reports readiness.
- Treat missing emergency stop, current-limited supply, fire-safe test area, firmware dry-run, or human approval as blockers.
- Physical motor motion requires a separate explicit human gate.
- Do not import sibling subskill code. Read files only.

## References

- `references/input-contract.md` for `integration_plan.yaml` fields.
- `references/bringup-gates.md` for safety gates.
- `references/data-capture.md` for sim2real logs.
- `references/output-contract.md` for report fields.
- `references/examples.md` for sample project layout.
Files in this package (20)
  • README.md 1 KB
  • SKILL.md 2 KB
  • examples/quadruped_mvp/integration_plan.yaml 1 KB
  • examples/quadruped_mvp/reports/bringup_report.md 1 KB
  • examples/quadruped_mvp/reports/data_capture_checklist.md 1 KB
  • examples/quadruped_mvp/reports/hil_plan.md 1 KB
  • examples/quadruped_mvp/reports/integration_checklist.json 1 KB
  • references/bringup-gates.md 1 KB
  • references/data-capture.md 1 KB
  • references/examples.md 1 KB
  • references/input-contract.md 1 KB
  • references/module-handoff.md 1 KB
  • references/output-contract.md 1 KB
  • scripts/check_bringup_readiness.py 1 KB
  • scripts/integration_common.py 8 KB
  • scripts/write_hil_plan.py 1 KB
  • tests/conftest.py 1 KB
  • tests/test_bringup_readiness.py 2 KB
  • tests/test_hil_plan.py 1 KB
  • tests/test_smoke.py 1 KB

Versions

RepositoryScoreLicence
This page · baibai2013/build123d-cad100Apache-2.0
Alejo2075/claude-code-aws100MIT
arbazkhan971/godmode100MIT
chrishuffman5/domain-expert90MIT

Database snapshot: 13.11.2026 · package version 2c6e60485fe3 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100robot-dog-digital-twin
    Mechanical dog digital-twin orchestrator. Use this skill whenever the user mentions robot dog digital twins, virtual prototypes, design gates before physical builds, multi-domain validation across CAD/PCB/circuit/simulation/gait, design scoring, failure reports, or iteration…
  • 100requirements-verification
    Requirement contract and verification matrix authoring for hardware and robot-dog digital-twin projects. Use when the user needs requirements.yaml, verification_matrix.yaml, architecture.yaml, risk_register.md, measurable gates, blocker thresholds, or validation readiness before…
  • 85esp32-fault-injection-hil
    Use when creating hardware-in-the-loop tests, fault injection, soak tests or regression rigs for ESP32 industrial devices.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.