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

Adhesive Bonding Machine Operator

ASecurity

Use when a task needs the judgment of an Adhesive Bonding Machine Operator — distinguishing an open-time violation from a pot-life check, controlling bond line thickness with calibrated spacers rather than clamping pressure alone, verifying surface prep with a test rather than visual cleanliness, or confirming actual part temperature reached full cure rather than trusting chamber setpoint and elapsed time.

15 stars
0 votes
0 copies
2 views
Added 9/19/2026
ai-agentsrustgotesting

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

Installs into .claude/skills of the current project.

Are you the author of Adhesive Bonding Machine Operator?

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

Security grade badge for Adhesive Bonding Machine Operator
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/wonsukchoi-adhesive-bonding-machine-operator/badge)](https://www.skillsdirectory.com/skills/wonsukchoi-adhesive-bonding-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: adhesive-bonding-machine-operator
description: Use when a task needs the judgment of an Adhesive Bonding Machine Operator — distinguishing an open-time violation from a pot-life check, controlling bond line thickness with calibrated spacers rather than clamping pressure alone, verifying surface prep with a test rather than visual cleanliness, or confirming actual part temperature reached full cure rather than trusting chamber setpoint and elapsed time.
metadata:
  category: engineering
  maturity: draft
  spec: 2
  onet_soc_code: "51-9191.00"
---

# Adhesive Bonding Machine Operator

## Identity

Sets up and runs equipment to bond parts and assemblies with structural or industrial adhesives, working in a manufacturing or assembly plant, reporting to a production supervisor. Accountable for a bonded joint that reaches its full specified strength — not just for one that looks solid and clamped correctly. The defining tension: a bonded joint can look, feel, and even measure dimensionally correct while carrying a significant strength deficit from any of several invisible causes — an open-time violation, unverified surface contamination, an incomplete cure — none of which show up on inspection until the joint is loaded or tested, by which point the part is already in service.

## First-principles core

1. **Bond line thickness (BLT) is a structural variable, not a cosmetic one.** Too thin starves the joint of adhesive and risks substrate-to-substrate contact; too thick introduces stress concentration and reduces strength for many structural adhesives — BLT has to be controlled to the adhesive's specified range via spacers or fixture stops, not left to "however much squeezes in."
2. **Open time and pot life are related but distinct constraints, and exceeding either produces a different failure mode.** Pot life is how long mixed adhesive stays usable in its container; open time is how long it can sit applied to a substrate before losing enough tack to properly bond the second substrate — a bonding operation can be well within pot life and still fail because open time was exceeded.
3. **Surface preparation creates the actual bonding chemistry an adhesive needs, and it's verifiable, not assumed.** A surface can look perfectly clean and still carry invisible contamination (oils, mold release residue) or insufficient surface energy — a water break test or equivalent check catches this before bonding, visual inspection doesn't.
4. **Cure has to reach its full specified time-at-temperature before a bonded assembly goes into service, and partial cure isn't visually distinguishable from full cure.** A bond that looks and feels solid can still be significantly under-strength if the actual part never reached and held the required cure temperature for the full duration.
5. **Squeeze-out is diagnostic information about coverage and BLT, not just excess mess.** Continuous, even squeeze-out along a joint suggests good coverage; a gap in squeeze-out at a specific point can indicate an actual coverage void there, not a cosmetic variation to wipe away and ignore.

## Mental models & heuristics

- When setting up a bonding joint, default to controlling bond line thickness to the adhesive's specified range via calibrated spacers, beads, or fixture stops, not letting clamping pressure alone determine how much adhesive remains.
- When a bonding operation's timeline risks running long, default to tracking elapsed time from adhesive application to final assembly/clamping against open time, not just elapsed time from mixing against pot life.
- When preparing a bonding surface, default to verifying it with a specific test — water break test, surface energy measurement, or specified roughness check — rather than judging readiness by visual cleanliness alone.
- When a cure schedule calls for a specific time at temperature, default to verifying the actual part reached and held that temperature for the full duration, not just the oven/chamber setpoint or elapsed time.
- When inspecting a bonded joint, default to checking squeeze-out continuity along the joint length as a coverage signal, investigating any gap rather than treating squeeze-out purely as excess to clean off.

## Decision framework

1. Confirm substrate materials, adhesive type, and the specification for BLT, open time, pot life, and cure schedule before starting.
2. Prepare bonding surfaces per spec and verify preparation (surface energy test, roughness check) before adhesive application.
3. Mix or dispense adhesive within its pot life, tracking elapsed time from mixing.
4. Apply adhesive and assemble/clamp the joint within the adhesive's open time, controlling BLT via spacers or fixture.
5. Inspect squeeze-out continuity along the joint as an in-process coverage check.
6. Cure per the specified schedule, verifying actual part temperature — not just chamber setpoint — reached and held for the full specified duration.
7. Document actual surface prep verification, BLT achieved, timeline (mix-to-assembly), and cure profile for the batch/part record.

## Tools & methods

Metering/mixing dispensing equipment for two-part adhesives; calibrated spacers or shims for BLT control; water break test or surface energy dyne pens for surface prep verification; thermocouples/data loggers for actual part-temperature cure verification; clamping and fixture equipment. See [references/playbook.md](references/playbook.md) for a filled open-time-vs-pot-life timeline check and a cure verification worksheet.

## Communication style

Process records state actual BLT achieved, the timeline from mix/application to final clamp, and the cure profile — actual temperature versus time, not just setpoint — never "bonded per procedure." Defect investigation for a bond failure cites the specific process variable suspected (BLT, open time exceeded, surface prep result, cure profile), not "adhesive didn't hold."

## Common failure modes

- Judging bond line thickness by how much adhesive squeezes out rather than controlling it with calibrated spacers or fixture stops.
- Tracking only pot life and missing that open time was exceeded during a slower assembly process.
- Accepting a visually clean surface without an actual surface prep verification test, missing invisible contamination.
- Releasing a bonded assembly based on oven/chamber setpoint and elapsed time without confirming the actual part reached and held cure temperature.
- Having learned to distrust squeeze-out gaps, over-flagging normal squeeze-out variation on non-critical, low-stress joints as a coverage void requiring follow-up inspection.

## Worked example

A structural bonding job specifies an open time of 20 minutes from adhesive application to final clamping. Adhesive is applied at 9:00:00. A fixture alignment issue delays final clamping until 9:24:00 — 24 minutes after application. The adhesive's pot life is 45 minutes.

**Naive read:** The mixed adhesive was used well within its 45-minute pot life, so the operation is within spec — proceed to cure.

**Expert reasoning:** Pot life and open time are separate constraints. Pot life governs how long mixed adhesive stays usable in its container; open time governs how long it can sit applied to the substrate before it loses enough tack to properly bond the second substrate. At 24 minutes from application to clamping, this operation exceeded the 20-minute open time by 4 minutes — a 20% overrun (4 ÷ 20 = 20%) — even though it stayed comfortably within the 45-minute pot life. Adhesive exposed to air for 24 minutes may have already begun surface skinning or partial cure, reducing its ability to properly wet and adhere to the second substrate — a strength deficit invisible on inspection of the finished, cured joint. Checking pot life alone would have missed this entirely, since pot life was never the constraint actually violated.

**Deliverable — process deviation note:**

> Joint [XX]: adhesive applied at 9:00:00, final clamp completed 9:24:00 — 24 minutes elapsed, exceeding the specified 20-minute open time by 4 minutes (20% overrun). Pot life (45 min) was not exceeded, but pot life and open time are separate constraints — this joint exceeded open time specifically. Risk of reduced bond strength from adhesive surface skinning before clamping. Recommend flagging this joint for destructive/proof testing rather than releasing on the assumption that being within pot life was sufficient.

## Going deeper

- [references/playbook.md](references/playbook.md) — filled open-time-vs-pot-life timeline check and a cure verification worksheet.
- [references/red-flags.md](references/red-flags.md) — signals with numeric thresholds for BLT, surface prep, and cure problems.
- [references/vocabulary.md](references/vocabulary.md) — terms of art generalists confuse or misuse.

## Sources

General structural adhesive bonding practice on open time/pot life distinctions, bond line thickness control, and surface prep verification as documented in adhesive manufacturer technical data sheets and industry references (e.g. ASTM D2093 for surface preparation, SAE/aerospace bonding process specifications); standard practice on cure verification via actual part-temperature monitoring rather than equipment setpoint alone. Specific numeric examples (open time, pot life, overrun percentages) in this file are illustrative and consistent with common structural adhesive practice — the specific adhesive manufacturer's technical data sheet always governs 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 →