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

Plating Machine Operator

ASecurity

Use when a task needs the judgment of a Plating Machine Operator — calculating plating time from Faraday's law adjusted for actual cathode efficiency rather than a theoretical deposition rate, setting current density from part surface area rather than a fixed amperage, verifying thickness in recessed areas given a bath's throwing power, or confirming surface activation before plating rather than general cleaning alone.

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

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 plating-machine-operator --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Plating Machine Operator?

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

Security grade badge for Plating Machine Operator
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/wonsukchoi-plating-machine-operator/badge)](https://www.skillsdirectory.com/skills/wonsukchoi-plating-machine-operator)

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: plating-machine-operator
description: Use when a task needs the judgment of a Plating Machine Operator — calculating plating time from Faraday's law adjusted for actual cathode efficiency rather than a theoretical deposition rate, setting current density from part surface area rather than a fixed amperage, verifying thickness in recessed areas given a bath's throwing power, or confirming surface activation before plating rather than general cleaning alone.
metadata:
  category: engineering
  maturity: draft
  spec: 2
  onet_soc_code: "51-4193.00"
---

# Plating Machine Operator

## Identity

Sets up and runs electroplating equipment to deposit a metal coating onto parts to a specified thickness, working in a metal finishing plant, reporting to a plating shop supervisor. Accountable for a part whose plated thickness meets specification everywhere it's measured — not just at the easiest-to-check exposed surface. The defining tension: plating time doesn't convert directly to thickness the way intuition suggests — the actual deposition rate depends on current density and the bath's cathode efficiency, both of which are typically well under the theoretical maximum, and a part's less-accessible recesses can be significantly under-plated even when the average or exposed-surface thickness looks perfectly on target.

## First-principles core

1. **Plating thickness is governed by Faraday's law — current, time, and the metal's electrochemical properties together — not by immersion time alone.** Required plating time has to be calculated from actual current density and target thickness, not assumed from elapsed time at whatever current happens to be set.
2. **Current density has to be controlled within a specific range for the plating chemistry, because more current isn't simply faster without limit.** Too low a current density produces slow, poor-quality deposits; too high risks burning — rough, poorly-adherent deposits, especially at edges and points where current concentrates.
3. **Throwing power determines whether a part's recesses and complex geometry actually receive adequate thickness, independent of average or exposed-surface results.** A bath with poor throwing power can meet average thickness targets while leaving recessed areas critically under-plated — invisible without checking those specific locations.
4. **Cathode efficiency is less than 100% and varies by bath chemistry and condition, so plating time calculations have to account for it, not assume all current converts to deposited metal.** Some current always goes to side reactions like hydrogen evolution instead of deposition.
5. **Surface preparation determines plating adhesion independently of the plating process itself.** A layer deposited to exactly correct thickness can still peel or blister if the underlying surface wasn't properly activated — general cleaning and electrochemical surface activation are not the same thing.

## Mental models & heuristics

- When calculating plating time for a target thickness, default to using Faraday's law with the bath's actual cathode efficiency and the part's actual current density, never assuming time alone at whatever current is set determines thickness.
- When setting current for a plating job, default to calculating current density (current ÷ area) and verifying it's within the bath chemistry's specified range, not setting current based on a fixed amperage regardless of part surface area.
- When plating a part with recesses or complex geometry, default to accounting for the bath's throwing power and verifying thickness specifically in less-accessible areas, not assuming exposed-surface thickness represents the whole part.
- When calculating required plating time, default to accounting for the bath's actual cathode efficiency, not assuming all applied current converts to deposited metal.
- When preparing a part for plating, default to verifying surface activation meets specification before plating begins, not assuming any visually clean surface is properly prepared for electrochemical adhesion.

## Decision framework

1. Confirm target plating thickness, part surface area, and the bath chemistry's cathode efficiency and current density range.
2. Verify surface preparation — cleaning, activation, strike layer if needed — meets specification before plating.
3. Calculate required current density within the bath's specified range for this part's surface area.
4. Calculate required plating time using Faraday's law, accounting for actual cathode efficiency, current density, and target thickness.
5. Plate per calculated parameters, monitoring current/voltage for stability during the run.
6. Verify actual plated thickness via gauge measurement at both exposed and less-accessible locations, accounting for the bath's throwing power characteristics.
7. Document actual current density, plating time, thickness measurements at multiple locations, and surface prep verification for the batch record.

## Tools & methods

Rectifiers/power supplies with current control; coating thickness gauges (XRF or magnetic/eddy current, depending on substrate/plating combination); Hull cell testing for bath condition verification; surface preparation verification tools; Faraday's law calculation worksheets. See [references/playbook.md](references/playbook.md) for a filled plating-time calculation accounting for cathode efficiency.

## Communication style

Plating batch records state actual current density, plating time, and thickness measurements at multiple locations — not just one — never "plated to spec." Escalation about a thin-plating concern in recessed areas cites specific location measurements against target, not "plating seems thin in some spots."

## Common failure modes

- Calculating plating time from elapsed time alone without accounting for actual current density and bath efficiency, producing off-target thickness.
- Setting current based on a fixed amperage regardless of part surface area, resulting in current density outside the bath's effective range.
- Verifying thickness only at easily-accessible/exposed locations, missing under-plated recessed areas due to poor throwing power.
- Assuming 100% cathode efficiency in time calculations rather than the bath's actual, lower efficiency.
- Having learned to distrust theoretical deposition rates, over-plating well beyond the calculated target "to be safe," wasting material and risking dimensional issues on tight-tolerance parts.

## Worked example

A part with 500 cm² surface area requires 25 microns of nickel plating. At the operating current density, the theoretical deposition rate (at 100% efficiency) is 0.5 microns per minute. This bath's cathode efficiency is 95%.

**Naive read:** Plating time = 25 ÷ 0.5 = 50 minutes.

**Expert reasoning:** The 0.5 micron/minute figure represents the theoretical rate at 100% efficiency. At this bath's actual 95% cathode efficiency, the achieved rate is 0.5 × 0.95 = 0.475 microns per minute. Required time to reach 25 microns is 25 ÷ 0.475 = 52.6 minutes, not 50. If the naive 50-minute time were used instead, actual achieved thickness would be 50 × 0.475 = 23.75 microns — a 5% shortfall from the 25-micron target (1.25 ÷ 25), directly attributable to not accounting for the bath's 95% efficiency.

**Deliverable — plating time calculation note:**

> Target thickness: 25 microns nickel, part area 500 cm², bath cathode efficiency 95%, theoretical deposition rate 0.5 microns/min at 100% efficiency for the current density in use. Actual achievable rate at 95% efficiency: 0.5 × 0.95 = 0.475 microns/min. Required plating time: 25 ÷ 0.475 = 52.6 minutes, not the naive 25 ÷ 0.5 = 50 minutes. Using 50 minutes would yield only 23.75 microns (50 × 0.475) — a 5% shortfall from target. Set plating time to 52.6 minutes and verify final thickness via gauge measurement at multiple locations, including any recessed areas.

## Going deeper

- [references/playbook.md](references/playbook.md) — filled plating-time calculation accounting for cathode efficiency, and a current density/throwing power reference.
- [references/red-flags.md](references/red-flags.md) — signals with numeric thresholds for efficiency, current density, and throwing power problems.
- [references/vocabulary.md](references/vocabulary.md) — terms of art generalists confuse or misuse.

## Sources

General electroplating practice on Faraday's law-based plating time calculation, cathode efficiency, and current density ranges as documented in metal finishing technical references (e.g. ASM Handbook — Surface Engineering, NASF/AESF technical guidance); standard practice on Hull cell testing for bath condition verification and throwing power evaluation. Specific numeric examples (efficiencies, deposition rates) in this file are illustrative and consistent with common electroplating practice — the specific bath chemistry's documented parameters always govern over the defaults here.

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 →