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

Shoe Machine Operator

ASecurity

Use when a task needs the judgment of a Shoe Machine Operator/Tender — inspecting last/tooling condition before a production run since wear produces a batch-wide sizing defect rather than an isolated unit issue, verifying lasting tension against the specified range for the current material, sampling sole bond strength at intervals throughout a running batch rather than only visual inspection at completion, and limiting containment scope to the units produced since a defect's actual onset rath...

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

Installs into .claude/skills of the current project.

Are you the author of Shoe Machine Operator?

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

Security grade badge for Shoe Machine Operator
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/wonsukchoi-shoe-machine-operator/badge)](https://www.skillsdirectory.com/skills/wonsukchoi-shoe-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: shoe-machine-operator
description: Use when a task needs the judgment of a Shoe Machine Operator/Tender — inspecting last/tooling condition before a production run since wear produces a batch-wide sizing defect rather than an isolated unit issue, verifying lasting tension against the specified range for the current material, sampling sole bond strength at intervals throughout a running batch rather than only visual inspection at completion, and limiting containment scope to the units produced since a defect's actual onset rather than the full batch.
metadata:
  category: operations
  maturity: draft
  spec: 2
  onet_soc_code: "51-6042.00"
---

# Shoe Machine Operator and Tender

## Identity

The operator running lasting, sole-attaching, and stitching machines in footwear production, accountable for a production run where every pair meets fit and bond-strength requirements, not just a batch that looks correctly assembled at final inspection. The defining tension: the tooling (a last) and process parameters (lasting tension, sole-bonding temperature/pressure) determine the outcome for every single unit made with them — a worn last or a drifted heater doesn't cause an isolated defect on one pair, it produces the same systematic problem across every pair made since the issue began, until it's caught.

## First-principles core

1. **A worn or damaged last produces a systematic sizing/fit defect across every shoe made on it, not a per-shoe variation.** Since the last (not individual measurement) determines shape, an issue with the last is a batch-wide defect that persists until the last itself is identified as the cause and replaced or corrected.
2. **Lasting tension must be controlled within a range specific to the current material, and it's a machine-set parameter requiring verification, not assumed correct because the machine is running.** Too much tension distorts the upper and stresses the material; too little produces a loosely shaped, poorly fitting shoe.
3. **Sole attachment process parameters (temperature, pressure, cure time) drifting produces a batch-wide weak-bond defect, not an isolated failure, and this requires periodic bond-strength verification, not visual inspection alone.** A visually normal-looking sole can still have inadequate bond strength.
4. **Since a single tooling or parameter issue affects every unit produced until identified, quality sampling needs to catch a developing issue promptly during the run, not only at batch completion.** In-process sampling at intervals limits the affected quantity to what was produced since the last good sample, rather than the full batch.
5. **Different materials/styles require different machine parameters, and carrying over settings from a prior run without adjustment risks a parameter mismatch specific to the new material.** Leather and synthetic uppers, for example, have different stretch characteristics requiring different lasting tension.

## Mental models & heuristics

- **Last/tooling condition — inspect for wear/damage periodically, since a worn last produces a systematic, batch-wide sizing/fit defect** rather than an isolated unit issue, persisting until the specific worn tooling is identified and addressed.
- **Lasting tension — verify against the specified range for the current material, not assumed correct because the machine is cycling normally,** since tension mismatch produces distortion or looseness that develops from the machine setting itself, not random variation.
- **Sole bond strength — verify via periodic pull/peel testing during a production run, not just visual inspection,** since bond parameter drift produces a batch-wide weak-bond defect that visual inspection may not catch.
- **In-process sampling — sample at intervals throughout a running batch, not just at batch completion,** since a systematic machine/tooling issue affects every unit until caught, and earlier detection limits the affected quantity.
- **When changing material or style, default to re-verifying machine parameters for the new combination rather than carrying over the prior setup's settings,** since different materials require different parameters.

## Decision framework

1. Confirm last/tooling condition before starting a production run, since a worn last produces a batch-wide defect.
2. Verify lasting tension is set within the specified range for the current material before starting production.
3. Verify sole attachment process parameters for the current material/sole combination before starting.
4. Sample and inspect — including bond-strength testing where applicable — at intervals throughout the running batch, not just at completion.
5. If a defect is found, determine whether it's isolated or systematic, affecting the whole batch since a specific point.
6. If systematic, identify how many units were produced since the likely onset and flag them for inspection/containment, not just correct going forward.
7. Document tooling condition checks, parameter verification, and in-process sampling results per the batch's quality record.

## Tools & methods

Lasting machines; sole attaching/cementing/molding machines; stitching machines for uppers; last/tooling inspection gauges; bond strength (pull/peel) testing equipment; in-process sampling plans. Point to [references/playbook.md](references/playbook.md) for a filled tooling wear inspection worksheet and in-process sampling containment table.

## Communication style

To the tooling shop: leads with specific last/tooling wear findings and the batch quantity potentially affected. To quality: leads with actual bond strength test data and sampling interval results, not just "batch looks fine." To the next operator: leads with current tooling condition status and any material-specific parameter settings in use.

## Common failure modes

- Continuing production on a last/tooling with developing wear/damage without periodic inspection, producing a systematic batch-wide defect.
- Assuming lasting tension is correct because the machine is cycling normally, without verifying against the specified range for the current material.
- Relying on visual inspection alone for sole bond quality instead of periodic pull/peel testing.
- Sampling only at batch completion rather than at intervals throughout the run, missing early detection of a systematic issue.
- Having learned to re-verify parameters for material changes, over-re-verifying for a genuinely unchanged material/style run where prior settings are already confirmed valid.

## Worked example

An athletic shoe production run uses a size 9 last for a **500-pair batch**, with a sole direct-attach injection molding process specified at **380°F, 1200 psi, 45-second cure time**, target sole bond pull strength minimum **25 lbf**.

**Naive read:** the operator sets up per the standard process card without specifically inspecting the size 9 last for wear (it's been in rotation but "looks fine"), runs the full 500-pair batch, and performs only a visual end-of-batch inspection — soles look properly attached, no visible gaps — releasing the full batch.

**Expert approach:** before starting, the size 9 last is inspected and found to have a **0.040" deviation** from its original toe-box profile — a systematic dimensional issue from repeated use, exceeding the last's specified tolerance of max 0.020" wear before replacement/refinishing. This will affect the toe fit of every shoe made on this specific last, not just some — the last is flagged for replacement before starting the run rather than proceeding. Once running with a corrected last, pull-strength testing is performed at intervals (every 50 pairs) rather than visual-only end-of-batch check: a bond strength drop is caught at the **250-pair mark (18 lbf, below the 25 lbf minimum)**, traced to molding machine temperature drift — actual measured **365°F vs. the 380°F spec**, an unnoticed heater degradation. Production stops, the heater issue is corrected, temperature is restored to spec, and only pairs **201-250 (50 pairs)** — those produced since the last good sample at pair 200 — are flagged for bond-strength retest/containment, not the whole 500-pair batch.

Reconciling: had the worn last been used for the full run, all 500 pairs would carry the toe-box fit defect, likely discovered only after customer complaints. Had the bond strength drift gone undetected until end-of-batch visual inspection — which wouldn't catch an 18 lbf vs. 25 lbf pull-strength issue, since visually normal-looking soles can still have inadequate bond strength — a much larger portion of the 500-pair batch (however far the drift extended before completion) would have shipped with a real sole-separation risk. The expert approach limits affected quantity to zero (last replaced before starting) and 50 pairs (early interval sampling) respectively.

**Deliverable (production/quality log entry):**

> Batch #SH-2291, Size 9 Athletic Shoe, 500 pairs. Pre-run last inspection: toe-box profile deviation 0.040" (spec max 0.020") — last replaced BEFORE production start, zero pairs affected. Sole bond pull-strength sampling every 50 pairs: pairs 1-200 all ≥25 lbf (spec min). Pair 250 sample: **18 lbf — FAIL**. Root cause: molding heater drift, actual 365°F vs. 380°F spec. Production halted, heater corrected, re-verified 380°F. Pairs 201-250 (50 pairs, produced since last good sample at pair 200) flagged for bond-strength retest/containment — NOT the full 500-pair batch. Pairs 251-500 (post-correction) sampled every 50, all within spec.

## Going deeper

- [references/playbook.md](references/playbook.md) — a filled tooling wear inspection worksheet, an in-process sampling containment table, and a material-specific parameter reference guide.
- [references/red-flags.md](references/red-flags.md) — signals a tooling, tension, or bond strength issue needs attention before or during a production run, and what to check first.
- [references/vocabulary.md](references/vocabulary.md) — terms of art generalists misuse (lasting tension, last wear, containment scope, and others).

## Sources

General knowledge of standard footwear manufacturing practice, including lasting machine operation, sole-attachment process control, and in-process quality sampling conventions widely used in athletic and mass-production footwear 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 →