One catalog row, stated exactly
Wire an outlet: "Strip wires and land on terminals." The row is rated Hard, lists a multiview rig with handheld grippers and is Available on request.
Now recruiting capture teams worldwide. Get paid to record first-person video of real work.
Apply to captureHard task
Requirements
Wire an outlet: "Strip wires and land on terminals." The row is rated Hard, lists a multiview rig with handheld grippers and is Available on request.
Hand pose, contact events and per-frame instance masks are recorded on one clock, with a visibility flag on each joint for fingers that a wire or a device hides.
A calibrated stereo pair and an MCAP container are agreed in the skill spec. The row does not state either, and this page does not claim them.
Consent, anonymization and the license are stated below. This page makes no electrical-safety or compliance claim and gives no instructions.
Definition
Stereo outlet wiring data is first-person video of a person doing the work named in one catalog row: stripping wires and landing them on terminals to wire an outlet. It is recorded from the contributor’s own point of view with two calibrated cameras, and with synchronized sensor streams alongside, so the frames show what the hands are doing with the wire and the terminal rather than a distant view of a bench. Searchers also phrase it as stereo outlet wiring video, wire stripping and terminal landing robot data, an electrical bench dataset or custom trades data collection at scale. The data is the same, collected as a custom collection scoped to your task.
On this site the data is human capture: a paid, consented contributor performs the task from a written skill spec. It is not robot or teleoperation data, and the page makes no claim that any robot has been trained on it or that any robot wires an outlet. Stereo describes the capture and MCAP describes the container. They are separate choices, and neither is stated on the row itself.
Catalog row
One row sits in the Trades Workshop Bench environment, in the Construction & Trades sector. "Wire an outlet" reads: "Strip wires and land on terminals." It is rated Hard, its capture is Multiview rig + handheld grippers and its status is Available on request. The environment’s shared example line reads "Workshop bench with hand and power tools: wrenches, drivers, drill, saw, clamps, fasteners". It is one line for every row in that environment, so it is quoted here rather than assigned to this task.
Available on request means the work is scoped and recruited to spec when a buyer asks. It does not mean a stock of outlet wiring footage exists, and this page claims no volume, hours or delivered clips for the row. The row names wires, terminals and an outlet. It names no voltage, no wire gauge, no code, no tool or device model and no tester, so if your program needs any of them, it is written into the skill spec rather than assumed.
Other rows describe nearby work in other environments. Outlet & Fixture Wiring and a second strip-and-wire row sit in Trade Service Calls and are Ready to deploy, Electrical installation sits in Active Construction Site and is Active collection, and Electrical repair call sits in On-Site Home Repair and is Available on request. All are rated Hard. The first table below reproduces the bench row and these four neighbours exactly.
Why it is hard
The site’s answer is the Skill column. The catalog rates the row Hard, and that is all "Hard" means here. This page imports no outside rubric and states no failure rate, tolerance or claim about how skilled any worker is. What the site does say is in the row text. The task is two things in sequence: stripping wires, then landing them on terminals. The part that matters is a wire end meeting a terminal, and that is small, two-handed work. The site publishes no step list, no limit and no outcome definition for it.
The site’s electrical copy adds two things that bear on capture. The first is that the part that matters is often the part a hand is covering, which is why hand pose carries a per-joint visibility flag for hidden fingers. The second is that a stereo pair recovers depth from a calibrated frame pair, so the shape of the part sits in the same frame as the hands. The challenge table below maps each difficulty to the stream or label the site already states, and says Not stated where nothing is.
Capture
The catalog lists one capture mode for the row: Multiview rig + handheld grippers. The site describes it as a staged working set recorded by a multiview rig while the operator performs the task with handheld grippers, so demonstrations map onto a robot end effector. The row does not state stereo capture, and this page does not describe it as stereo or as head-mounted phone capture. Stereo reaches this row only through the site’s general stereo offer: a capture choice agreed in the skill spec and confirmed on a Spec Pilot.
The site describes two stereo setups and does not say which one a wiring order would use. The off-the-shelf stereo head rig, dataset 06, is dual fisheye cameras at 1080p per eye with a 62 mm baseline, per-unit calibration, a 9-axis IMU and hand-tracking output, shipped as MCAP. The hard-environments stack is a global-shutter 4K/60 head camera, two 1080p/60 wrist cameras, a depth sensor at 848×480 and 30 fps and 200 Hz 6-DoF IMUs. Which of these apply to a staged gripper setup, and how hand pose is recorded when the operator holds a gripper, is Not stated. Confirm both in the skill spec.
What stereo adds
The site states that a stereo pair at human-eye spacing makes depth recoverable from every frame pair, and that a calibrated pair measures disparity between two views at a fixed, known baseline rather than guessing depth from a single frame. For a wire and a terminal, that puts the stripped end, the terminal and the device in the same capture as the hands. The site gives no depth accuracy figure for these tasks and no connection-quality label, so what a buyer does with that depth is their pipeline’s question.
The site also notes that glare-heavy and low-texture scenes make single-frame depth worse, and that depth degrades on wet and reflective surfaces while confidence maps mask the low-confidence regions. How depth behaves on a bare conductor end or a metal terminal face is not stated, so this page promises no figure. Calibration is re-solved at the start and end of every session under a 0.28 px RMS reprojection gate, and streams are hardware-triggered onto one clock with a 2.0 ms cross-stream ceiling.
Episodes
Each attempt is delivered as one episode. The standard episode carries action segments, 3D hand pose for both hands with a per-joint visibility flag, contact events that mark when a hand meets an item, an objects list, and per-frame instance masks stored at the depth resolution of 848×480. Hand pose is 21 joints per hand, 3D, in metres in the head-camera frame. For this row an episode might cover one outlet or a run of several; where each episode starts and ends is written into the spec, because the site sets no episode length.
Action segments divide an episode into start- and end-timestamped spans, each carrying start_ns, end_ns, verb and noun, so stripping and landing can each be their own labeled span. Which verbs and nouns are used is set in the skill spec. The site lists no label for the outcome of a step, such as whether a wire sits on a terminal, no connection or termination label, and no torque, grip-force or tightness stream, so ask for any such label in the spec.
Neighbouring pages
Several pages touch the same work, and none has the Wire an outlet row as its main topic. The egocentric electrical work page covers five electrical rows across four environments: episode contents, labels, privacy and delivery. The stereo electrical installation page covers the same five rows on the stereo and MCAP side. The cable routing and wiring page covers routing, clipping, patching and outlet wiring across benches, racks and venues, and the stereo thermostat and control wiring page covers one heating and cooling control row.
This page takes the single bench row out of that group and gives it its own page, because the hub’s Hard-row table lists it separately. The comparison table below sets each page against this one. The egocentric stereo MCAP page is the format page for the container and is linked as the place to read about it in general.
MCAP
MCAP is an open source container file format for multimodal log data, supporting multiple channels of timestamped pre-serialized data. It is serialization-agnostic, so messages can be Protobuf, DDS (CDR), ROS, JSON and more. Its design is row-oriented and append-only, it stores schemas alongside the data, and it offers an optional index plus optional LZ4 or Zstandard chunk compression and optional CRC checksums. Those facts come from mcap.dev and the foxglove/mcap repository, both linked below. Firsthand is not affiliated with Foxglove or the MCAP maintainers.
Firsthand offers MCAP delivery, and dataset 06 is stated as shipping as MCAP. For this row the site states a stereo pair, depth with confidence maps, hand pose, IMU, contact events, action segments and calibration elsewhere. It does not state which of those are channels in an MCAP file, how they are named, what encoding they use or at what rate. No topic name, message schema or rate is stated on this page, and none should be assumed. Name the streams that matter in the skill spec and confirm them on a Spec Pilot batch. The stream map below sets each stream beside what the site states about it.
Delivery and license
Delivery is in the format your stack already reads: RLDS, LeRobot, WebDataset, HDF5, zarr or Rerun .rrd, or raw streams with metadata, with readable converter source alongside, and MCAP can ship alone or beside any of them. The episodes follow the same episode schema as every other Firsthand collection, so a loader that reads another Firsthand dataset reads this one without changes. Which container suits a lab depends on its reader and its training loop, and the site does not rank them.
The license is perpetual, irrevocable and worldwide, buyer-owned and non-exclusive by default, with exclusivity available as a separate term. The executed agreement controls. Official documentation for MCAP, RLDS, LeRobot and WebDataset is linked in the sources below.
Validation
Validation runs against signed accept criteria written into the spec before capture, and a reject log ships with each batch. Episodes are machine-checked against stated reject criteria, such as a sync breach, the manipulated object out of frame for more than 15 percent of the episode, or more than 35 percent of depth pixels in the manipulation region invalid, and a human reviewer then checks each one. Only footage that clears the criteria is billed as a validated hour.
For this row, the spec has to say which item counts as the manipulated object at each step and where the manipulation region is, because the wire, the terminal and the outlet are different items at different moments. What counts as a finished step is also written down, since the site states no outcome definition. Rejected items are recaptured at our cost, and the site states no accuracy figure for step labels, so what counts as a pass for a step boundary is set in the accept criteria.
Capture and privacy
Every contributor signs a written release, and each delivered episode links to it through consent artefact IDs. At ingest, automated detection finds faces, plates and screens and blurs them irreversibly, and speech is scrubbed of names, addresses and card numbers. A human reviewer confirms that no un-consented person is identifiable in any frame, footage with bystanders who cannot be de-identified is discarded, and the anonymization record ships with the data. Firsthand does not capture at a customer’s own facility, and which setting a program uses is agreed in the skill spec before capture begins.
This page makes no electrical-safety, licensing, qualification or compliance claim, because the site makes none for these rows, and it gives no instructions for any step. None of this is legal advice.
Speed and scale
From signed spec to first validated batch, the published timeline is a median of 48 hours where coverage is deep and three to four weeks where it is thin and contributors need to be recruited first. The row is Available on request, so the range that applies is confirmed when the spec is quoted rather than assumed. After a first batch, on-demand top-ups run against the same accept criteria, so you can add variation without rewriting the spec.
Outlet wiring is custom collection at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs. The site states no provider count, hours or throughput for this row, and none of its off-the-shelf dataset descriptions names it, so treat it as a custom collection. Only dataset 06, the stereo head rig, is stated as shipping as MCAP, and a lab can use that stock footage to check the rig and the format before commissioning the task.
Getting started
Describe the sequence your policy needs, where each step starts and ends, what you expect to see as the wire, the terminal and the outlet, what counts as a finished step and the variation your pipeline is missing. Then name the streams you want, whether stereo is part of the capture, and whether MCAP is the only delivery or sits beside RLDS, LeRobot or WebDataset. That becomes a written skill spec, quoted for reach, timeline and price before any capture begins.
Most programs begin with a Spec Pilot, a small, fast first batch that proves the spec and the accept criteria on real footage before volume scales. Collections are billed per validated hour. Counts of sites, episodes and hours are set in the skill spec. Our skill spec guide walks through how to write one.
Capture setup
| Part | As stated on this site |
|---|---|
| Capture mode (Wire an outlet) | Multiview rig + handheld grippers, as the catalog lists it |
| What that means | A staged working set recorded by a multiview rig while the operator performs the task with handheld grippers, so demonstrations map onto a robot end effector |
| Stereo head rig (dataset 06) | Dual fisheye, 1080p per eye, 62 mm baseline, per-unit calibration, 9-axis IMU, hand-tracking output; shipped as MCAP |
| Hard-environments stack | 4K/60 global-shutter head camera, 120° lens; two 1080p/60 wrist cameras; depth 848×480 at 30 fps; 200 Hz 6-DoF IMU |
| Sync | Hardware-triggered onto one clock; 2.0 ms cross-stream ceiling |
| Calibration | Re-solved at the start and end of every session; 0.28 px RMS gate |
| Hand pose | 21 joints per hand, 3D, in metres in the head-camera frame; per-joint visibility flag |
| Stereo on this row | Not stated; a separate offer, agreed in the skill spec and confirmed on a Spec Pilot |
| Which streams apply to the gripper setup | Not stated; confirmed in the skill spec |
Every collection runs through the same seven-stage end-to-end custom collection pipeline.
Live catalog rows
| Task | Description | Environment | Skill | Capture | Status |
|---|---|---|---|---|---|
| Wire an outlet | Strip wires and land on terminals. | Trades Workshop Bench | Hard | Multiview rig + handheld grippers | Available on request |
| Outlet & Fixture Wiring | Strip wires, connect outlets and fixtures and test with a voltage tester with power off. | Trade Service Calls (Plumbing / HVAC / Electrical) | Hard | Phone (head-mounted) / multiview rig | Ready to deploy |
| Strip and wire electrical outlets using wire strippers and a voltage tester | Strip and connect wires to the outlet terminals and verify with a voltage tester. | Trade Service Calls (Plumbing / HVAC / Electrical) | Hard | Phone (head-mounted) / multiview rig | Ready to deploy |
| Electrical installation | Run cable, mount boxes and wire outlets, switches and fixtures on a construction site. | Active Construction Site | Hard | Phone (head-mounted) / multiview rig | Active collection |
| Electrical repair call | Diagnose a fault in a client’s home, replace the failed switch, socket or breaker and test. | On-Site Home Repair | Hard | Phone (head-mounted) / multiview rig | Available on request |
Neighbouring pages
| Page | Main topic | Where Wire an outlet appears |
|---|---|---|
| This page | The Wire an outlet row, with stereo and MCAP as spec-level choices | The whole page |
| Egocentric electrical work video data | Five electrical rows across four environments, egocentric | One of five rows |
| Stereo electrical installation data | The same five rows on the stereo and MCAP side | One of five rows |
| Egocentric cable routing and wiring data | Routing, clipping, patching and outlet wiring across benches, racks and venues | Among the wiring rows |
| Stereo thermostat and control wiring data | One heating and cooling control row in Trade Service Calls | Not covered |
| Egocentric stereo data in MCAP | The MCAP delivery format for stereo capture in general | Not covered; format page |
| Hard-task data collection | The hub of rows the catalog rates Hard | The row is in the Hard-row table and links here |
Capture challenges
| Bench challenge | What goes wrong | Stated stream or label |
|---|---|---|
| Hands cover the wire or terminal | Fingers hide the part that matters | 3D hand pose with per-joint visibility flags; per-frame instance masks; a wrist view alongside the head camera; reject if the object is out of frame for more than 15% of an episode |
| Hand meets wire or device | The hand and the item touch in quick succession | Contact events mark when a hand meets an item; no finer contact label is stated |
| Glare and shiny surfaces | Depth readings degrade on a reflective surface | The site states that depth degrades on wet and reflective surfaces and that a confidence map is delivered to mask low-confidence regions; reject if more than 35% of depth pixels in the manipulation region are invalid |
| Stripping and landing as separate steps | It is unclear where one step ends and the next begins | Action segments, one per step as written in the spec; no accuracy figure for step labels is stated |
| Wire seated on the terminal | Whether a wire has landed is a visual state | Not stated: no connection, termination or seating label is listed |
| Motion blur and occlusion | Fast reaches between wire, tool and terminal | Global-shutter head camera avoids rolling-shutter skew; visibility flag for hidden joints |
| Grip and handling force | How hard a wire or device is held | Not stated: no force, torque or tactile stream is listed |
Stream map
| Stream or item | What the site states | In an MCAP delivery, as the site states it |
|---|---|---|
| Stereo pair | Dual fisheye, 1080p per eye, 62 mm baseline (dataset 06); for this row, agreed in the skill spec | Dataset 06 is stated as shipped as MCAP; channel layout not stated |
| Depth with confidence maps | Recovered from the calibrated stereo pair; confidence map masks low-confidence regions | Not stated |
| Hand pose | 21 joints per hand with a per-joint visibility flag | Channel layout and joint order not stated |
| Wrist views | Wrist camera available alongside the head camera | Not stated |
| IMU | 9-axis (dataset 06); 6-DoF at 200 Hz (hard-environments stack) | Channel layout and rate not stated |
| Contact events, action segments | Listed in the site’s episode schema; action segments carry start_ns, end_ns, verb and noun | Not stated |
| Calibration | Measured every session and shipped with the episode | Placement in the file not stated |
| Topic names, schemas, encoding, rates | Not stated | Agreed in the skill spec |
Delivered vs not stated
| Item | Status | Detail |
|---|---|---|
| Action segments | Delivered | start_ns, end_ns, verb, noun, one per step |
| 3D hand pose | Delivered | 21 joints per hand; per-joint visibility flag for occluded fingers |
| Contact events | Delivered | The moment a hand meets an item |
| Per-frame instance masks | Delivered | Stored at 848×480 |
| Consent and anonymization records | Delivered | Consent artefact IDs per episode; anonymization record shipped with the data |
| Formats | Delivered | MCAP, RLDS, LeRobot, WebDataset, HDF5, zarr, Rerun .rrd or raw streams with metadata |
| Voltages, wire gauges, codes, tool and device models | Not stated | Agreed in the skill spec |
| Connection, termination or test-result labels | Not stated | No such label is listed |
| MCAP topics, schemas and rates | Not stated | Agreed in the skill spec |
| Cycle times and throughput | Not stated | No such figure is listed |
| Number of sites, episodes and hours | Not stated | Set per program in the skill spec |
| Safety, qualification or compliance claims | Not stated | This page makes none |
Example footage
One real clip already published on this site. It is a format and rig example: a head-mounted stereo capture with hands in frame. It is not outlet wiring, electrical work or any task from this page.
No outlet wiring clip is published on the site, so this is the nearest stereo clip, labelled as a rig example. Request a sample to see delivered files. See stereo sample page, request an egocentric data sample.
FAQ
Sources
Tell us the sequence, where each step starts and ends, what you expect to see as the wire, the terminal and the outlet, whether stereo and MCAP are part of the delivery, and the angles you want. We will quote reach, timeline and price against a written spec.