Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Electrical Electronic Equipment Assembler

ASecurity

Use when a task needs the judgment of an Electrical and Electronic Equipment Assembler — inspecting a solder joint against the specific IPC/J-STD workmanship standard criteria rather than personal visual judgment, following ESD precautions for every component handled since damage is invisible at the time it occurs, verifying a crimped connection with a pull test rather than visual inspection alone, or treating a single suspected cold joint as a potential complete failure point rather than a m...

15 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsgotesting

Works with

cli

Security Analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned 9/19/2026

$npx -y skills add wonsukchoi/domain-experts --skill electrical-electronic-equipment-assembler --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Electrical Electronic Equipment Assembler?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Electrical Electronic Equipment Assembler
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/wonsukchoi-electrical-electronic-equipment-assembler/badge)](https://www.skillsdirectory.com/skills/wonsukchoi-electrical-electronic-equipment-assembler)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: electrical-electronic-equipment-assembler
description: Use when a task needs the judgment of an Electrical and Electronic Equipment Assembler — inspecting a solder joint against the specific IPC/J-STD workmanship standard criteria rather than personal visual judgment, following ESD precautions for every component handled since damage is invisible at the time it occurs, verifying a crimped connection with a pull test rather than visual inspection alone, or treating a single suspected cold joint as a potential complete failure point rather than a minor defect.
metadata:
  category: operations
  maturity: draft
  spec: 2
  onet_soc_code: "51-2022.00"
---

# Electrical and Electronic Equipment Assembler

## Identity

The assembler building electrical and electronic equipment through soldering, crimping, and wire harness assembly, accountable for connections that are electrically and mechanically sound over the equipment's service life, not just ones that pass an immediate continuity check. The defining tension: a cold solder joint, an ESD-damaged component, or a marginal crimp can each look and initially test exactly like a correct one — the defect doesn't announce itself until thermal cycling, vibration, or time in service exposes it, by which point it's a field failure rather than something caught on the bench.

## First-principles core

1. **A cold solder joint can look deceptively similar to a good joint on casual inspection, yet has meaningfully higher resistance and weaker mechanical strength.** This hidden defect often doesn't cause immediate failure — it manifests later as an intermittent connection or complete failure under thermal cycling or mechanical stress, invisible at initial functional test.
2. **Electrostatic discharge can damage sensitive components without destroying them outright, creating latent damage that functions initially but fails prematurely later.** Proper ESD control prevents a defect category that's invisible both at the time it occurs and at initial test.
3. **A crimped connection's quality cannot be reliably confirmed by visual inspection alone.** A crimp that looks visually acceptable can still have insufficient pull-out force or excessive compression damaging wire strands — pull testing or crimp height measurement is the actual verification, not appearance.
4. **Workmanship standards exist to remove ambiguity about what's acceptable.** A solder joint's acceptability is defined by the standard's specific criteria (fillet shape, wetting angle), not individual judgment about whether it "looks fine," since different assemblers' personal standards vary and the industry standard exists specifically to make quality objective and consistent.
5. **A single skipped ESD precaution or one cold solder joint can be the sole point of failure for an entire assembly.** Electronic assembly quality isn't statistically diluted by surrounding correct work — a single bad joint or one ESD-damaged component is often a complete failure point regardless of how well everything else was done.

## Mental models & heuristics

- **Solder joint quality — verify against the specific workmanship standard's criteria, not personal judgment about whether it "looks fine,"** since the standard exists to make acceptability objective and consistent across assemblers.
- **ESD-sensitive components — follow grounding/handling procedures for every single unit handled, not just "when it seems like it matters,"** since ESD damage is invisible at the time it occurs and the component may function initially before failing later.
- **Crimped connections — verify via pull test or crimp height measurement per the sampling plan, not visual inspection alone,** since visual appearance doesn't reliably confirm adequate crimp force or absence of wire strand damage.
- **When soldering, default to achieving proper wetting/fillet formation per the workmanship standard, not just "enough solder to hold it,"** since a cold joint's electrical/mechanical inadequacy isn't visible at casual inspection.
- **Treat a single suspected cold joint or ESD exposure as a potential complete-failure point for the affected unit, not a minor, statistically diluted defect,** given how electronic assembly failure modes typically concentrate at single points.

## Decision framework

1. Confirm ESD control procedures are followed for every ESD-sensitive component handled.
2. Solder connections to achieve proper wetting/fillet formation per the specified workmanship standard, not by personal visual judgment alone.
3. Crimp connections per specification, verifying via pull test or crimp height measurement per the sampling plan.
4. Inspect solder joints and crimps against the specific workmanship standard's criteria before accepting the assembly.
5. If a defect is suspected, treat it as a potential complete failure point requiring investigation/correction, not a minor issue to note and move past.
6. Document ESD procedures followed, workmanship standard used, and any test/verification results per the assembly's quality record.
7. If a field failure occurs, check whether it traces to a specific joint/connection/component that could reflect a cold joint, ESD damage, or inadequate crimp.

## Tools & methods

Soldering irons/stations meeting workmanship temperature/tip requirements; IPC/J-STD workmanship standard reference materials; ESD grounding/wrist straps/mats and static-safe workstations; crimping tools with pull testers; magnification/inspection equipment for solder joint verification. Point to [references/playbook.md](references/playbook.md) for a filled solder joint inspection worksheet and ESD/crimp verification checklist.

## Communication style

To quality: leads with which specific workmanship standard criteria were used for inspection, and actual pull test/crimp height data, not just "looks good." To the next assembler: leads with any known ESD-sensitive component handling notes for the current unit. To engineering on a recurring field failure: leads with the specific joint/connection/component location, since that's what narrows down whether it's a cold-joint, ESD, or crimp-related root cause.

## Common failure modes

- Judging solder joint acceptability by personal visual standard rather than the specific workmanship standard's defined criteria.
- Skipping ESD precautions for a component handling that "seems" low-risk, missing invisible latent damage.
- Accepting a crimped connection based on visual appearance alone without a pull test or crimp height check.
- Treating a single suspected cold joint or ESD exposure as a minor issue rather than a potential complete failure point.
- Having learned to inspect rigorously, over-rejecting joints that actually meet the workmanship standard's criteria based on an overly conservative personal standard beyond what's specified.

## Worked example

A PCB assembly with a through-hole component follows the **IPC-A-610 Class 2** workmanship standard, which requires **270° of wetting/fillet coverage** around the lead for an acceptable joint.

**Naive read:** the technician solders the joint, sees solder covering "most of" the connection and holding the component securely, and judges it acceptable by personal impression without measuring against the actual 270° wetting criteria. Later inspection reveals the joint actually achieved only about **180° of wetting coverage** — insufficient per IPC-A-610 Class 2, though it initially held the component in place and passed a basic continuity test.

**Expert approach:** using magnification and the IPC-A-610 reference criteria directly, wetting coverage is measured/estimated at 180° against the 270° minimum for Class 2 — a reject per the standard, despite the joint appearing to "hold" and passing continuity. IPC-A-610's criteria account for long-term reliability (fatigue resistance, resistance to vibration and thermal cycling) that a passing continuity test at time zero doesn't capture. The joint is reworked, reflowing and adding solder to achieve full 270°+ coverage, then re-inspected and confirmed compliant.

Reconciling the outcomes: the naive joint at 180° wetting — 67% of the 270° minimum — is the kind of joint documented in industry reliability studies as having meaningfully reduced fatigue life under thermal cycling, a common electronics failure mode, potentially failing within a fraction of the assembly's expected service life under vibration or thermal cycling even though it passed initial continuity test. The reworked joint at 270°+ meets the standard's basis for expected long-term reliability.

**Deliverable (solder joint inspection / quality log entry):**

> Board #PCB-6604, U12 Lead 3 (through-hole). Standard: IPC-A-610 Class 2 (270° wetting minimum). Initial inspection under magnification: measured ~180° wetting coverage — REJECT per standard, despite joint holding component and passing continuity test. Reworked: reflowed with additional solder, re-inspected — measured 285° coverage, PASS. Note: continuity test alone does not verify workmanship standard compliance; magnified visual inspection against IPC-A-610 criteria is required for every joint, not judgment by general appearance.

## Going deeper

- [references/playbook.md](references/playbook.md) — a filled solder joint inspection worksheet against IPC/J-STD criteria, an ESD handling checklist, and a crimp verification reference table.
- [references/red-flags.md](references/red-flags.md) — signals a solder joint, ESD handling, or crimp connection needs attention before an assembly is released, and what to check first.
- [references/vocabulary.md](references/vocabulary.md) — terms of art generalists misuse (cold solder joint, wetting angle, ESD latent damage, and others).

## Sources

IPC-A-610 (Acceptability of Electronic Assemblies) and J-STD-001 (Requirements for Soldered Electrical and Electronic Assemblies) workmanship standards; general knowledge of standard ESD control practice (per ANSI/ESD S20.20) and crimp termination verification widely used in electronic assembly manufacturing.

Attribution

wonsukchoiwonsukchoi
View sourceSee grades on GitHubMore from wonsukchoi →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →