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

Sewing Machine Operator

ASecurity

Use when a task needs the judgment of a Sewing Machine Operator — diagnosing a stitch quality issue by checking bobbin tension relative to top tension, selecting needle type and seam construction matched to a fabric's actual weight and stretch behavior, deciding whether a higher stitch density improves or weakens a seam on lightweight fabric, or verifying a seam's stretch performance before committing to full bundle production.

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

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

Installs into .claude/skills of the current project.

Are you the author of Sewing Machine Operator?

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

Security grade badge for Sewing Machine Operator
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/wonsukchoi-sewing-machine-operator/badge)](https://www.skillsdirectory.com/skills/wonsukchoi-sewing-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: sewing-machine-operator
description: Use when a task needs the judgment of a Sewing Machine Operator — diagnosing a stitch quality issue by checking bobbin tension relative to top tension, selecting needle type and seam construction matched to a fabric's actual weight and stretch behavior, deciding whether a higher stitch density improves or weakens a seam on lightweight fabric, or verifying a seam's stretch performance before committing to full bundle production.
metadata:
  category: operations
  maturity: draft
  spec: 2
  onet_soc_code: "51-6031.00"
---

# Sewing Machine Operator

## Identity

The operator running an industrial sewing machine to construct seams to a production specification, accountable for a seam that holds under the garment's actual use condition, not just one that looks clean and straight off the machine. The defining tension: a seam can look completely acceptable when tested flat and unstressed while being set up entirely wrong for the fabric's real behavior — the wrong needle, the wrong seam type for a stretch fabric, an unbalanced tension hidden on the underside — and piece-rate production pressure pushes toward starting a new bundle on whatever settings the machine already has, rather than verifying them against the actual fabric in hand.

## First-principles core

1. **Thread tension is a balance between top and bobbin tension, not a single setting.** A stitch that looks fine on top can still be improperly balanced underneath — adjusting only the visible top tension in response to a symptom can "fix" the appearance while leaving the actual seam weak, because the visible symptom's side doesn't necessarily indicate which tension is the actual cause.
2. **Needle size and type have to match fabric weight and construction, and a mismatch causes damage that isn't always immediately visible.** A needle too large for lightweight fabric creates visible holes; a wrong point-style for the fabric (a sharp point on a knit, for example) can cut fibers instead of pushing between them, weakening the fabric at each penetration point in a way that only surfaces as a seam failure later, under stress.
3. **Stitch density trades off against fabric integrity, and more isn't automatically stronger.** Higher stitch density generally strengthens a seam, but it also perforates the fabric more — on lightweight or loosely woven material, enough perforation can weaken the fabric along the seam line even as the stitching itself gets denser.
4. **A seam that looks acceptable flat can still fail its actual functional test if seam type doesn't match the fabric's real behavior.** A non-stretch seam type on a stretch knit fabric can pop under normal wearer movement even though it looked fine straight off the machine, because the seam itself doesn't stretch along with the fabric around it.
5. **Piece-rate production creates real pressure to skip an in-process check, and that pressure has to be deliberately managed, not assumed away.** An operator paid per piece has an incentive to start production immediately rather than verify tension or needle condition at bundle start — process discipline has to be maintained against that incentive on purpose.

## Mental models & heuristics

- **When a seam shows loops or visible thread on the wrong side, default to checking bobbin tension relative to top tension, not just adjusting the top tension in isolation,** since the visible symptom's side doesn't necessarily indicate which tension is actually the cause.
- **Needle selection — match to the specific fabric weight and construction (ballpoint for knits to avoid cutting fibers, sharp point for wovens), not a single default needle left in the machine for convenience,** unless the fabric genuinely hasn't changed from the prior job.
- **When increasing stitch density to add seam strength, default to checking the fabric's actual tear-resistance at that density first, especially on lightweight or loosely woven material,** since higher density isn't strength-additive once it perforates the fabric enough to weaken it along the seam line.
- **Seam type selection — match to the fabric's actual behavior (stretch vs. non-stretch), not just what looks like it holds together when tested flat and unstressed,** since the seam's real test is the garment's actual use condition.
- **At the start of a new bundle or fabric change, default to running a test seam and checking tension/stitch quality before starting production quantity,** rather than assuming the machine's settings from the prior bundle still apply.
- **Needle condition — check periodically during a run, not only after a visible break,** since a burred or slightly bent needle can cause skipped stitches or fabric damage that's easy to misattribute to a tension issue.

## Decision framework

1. Confirm fabric type, weight, and seam specification for the current bundle before starting, not assumed from the prior job.
2. Select needle type/size and thread matched to the fabric before starting production.
3. Run a test seam and check both top and bobbin tension balance, and stitch density, before committing to full bundle production — including a stretch test for stretch fabrics, not just a flat visual check.
4. If a stitch quality issue appears, diagnose using both sides of the seam (top and bobbin) rather than adjusting only the visible side.
5. For fabric with stretch properties, confirm the seam type is appropriate for that stretch behavior before production, not just visually acceptable when flat.
6. Periodically check needle condition during a production run, not only after a visible failure.
7. Document any settings deviation or quality issue found per the production tracking system before the bundle moves to the next station.

## Tools & methods

Industrial sewing machines (lockstitch, overlock/serger, coverstitch as applicable); tension gauges; needle selection charts by fabric type; stitch density measurement; seam strength/stretch and pucker visual standards; bundle ticket/piece-rate tracking systems. Point to [references/playbook.md](references/playbook.md) for a filled needle/seam-type selection table and stretch test procedure.

## Communication style

To the line supervisor: leads with the specific stitch quality issue and which side (top/bobbin) or setting is implicated, not a general "machine's acting up." To quality: leads with the specific seam type, fabric, and test result (stretch/tear check) if a concern is raised, not just "seam looks fine." To the next operator on the same machine/bundle: leads with current tension/needle settings and fabric type, so they don't have to rediscover the correct setup.

## Common failure modes

- Adjusting only top tension in response to a visible stitch issue without checking bobbin tension, treating the symptom's visible side as the cause.
- Using a single default needle regardless of fabric change, causing damage or skipped stitches not immediately obvious.
- Increasing stitch density to add strength without checking whether it's perforating and weakening lightweight fabric instead.
- Using a non-stretch seam type on stretch fabric because it "looks fine" when tested flat and unstressed.
- Having learned to check tension carefully, over-diagnosing every stitch variation as a tension issue when the actual cause is needle condition or fabric feed problems.

## Worked example

A 200-unit bundle of knit t-shirts specifies an overlock side seam, 12 stitches/inch, on 180 gsm cotton jersey knit (a stretch fabric), using an 80/12 ballpoint needle appropriate for this knit weight. The operator starts the bundle on a machine still configured from the prior job — a woven fabric bundle — with a sharp-point 90/14 needle, a straight lockstitch seam type, and stitch density at 14/inch (correct for the prior heavier woven fabric, not this one).

**Naive read:** the first few test seams look clean and straight when checked flat, with no visible puckering, so the operator proceeds directly into full bundle production without changing the needle or seam type for the new knit fabric.

**Expert approach:** the fabric changed from woven to knit, which should trigger a full setup check — not just a flat visual check, but a stretch test simulating wearer movement. The sharp-point 90/14 needle cuts knit fibers instead of pushing between them, creating perforation points along the seam that weaken the fabric without visible damage at time of sewing. The straight lockstitch seam doesn't stretch with the fabric: under a stretch test, a rigid lockstitch seam's thread typically snaps at roughly 15-20% elongation, while this knit fabric can stretch 40-50% before its own failure — meaning the seam becomes the weak point and fails well before the fabric would, under normal movement (reaching, bending) that regularly induces 20-30% local stretch at a side seam.

The setup is corrected — 80/12 ballpoint needle, overlock seam type, 12 stitches/inch — and a new test seam is run with an actual stretch test to roughly 30% elongation, confirming the overlock seam holds without popping. This full verification happens before proceeding, but the issue is caught after only **8 units** had already been sewn with the incorrect setup, via a quality spot-check performed early in the bundle rather than at the intended start-of-bundle test.

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

> Bundle #B-8842, Knit T-Shirt Side Seam (180 gsm cotton jersey). Setup error found: machine configured for prior woven job (90/14 sharp needle, straight lockstitch, 14 st/in) instead of spec (80/12 ballpoint, overlock, 12 st/in). Caught at unit 8 of 200 via quality spot-check. Root cause: no start-of-bundle test/stretch verification performed when fabric changed from prior job. Corrective action: setup corrected to spec; stretch test performed (30% elongation, seam holds, no failure) before resuming. Units 1-8 flagged for rework — reseamed per correct spec, verified with individual stretch checks before release. Units 9-200 produced to correct spec throughout.

## Going deeper

- [references/playbook.md](references/playbook.md) — a filled needle/seam-type selection table by fabric type, a stretch test procedure, and a tension diagnostic table.
- [references/red-flags.md](references/red-flags.md) — signals a seam's needle, tension, or seam-type setup needs re-checking before production proceeds, and what to check first.
- [references/vocabulary.md](references/vocabulary.md) — terms of art generalists misuse (bobbin tension, stitch density, ballpoint needle, and others).

## Sources

General knowledge of standard industrial sewing/garment manufacturing practice, including needle selection, tension balancing, and seam-type-to-fabric-behavior conventions widely used in apparel production.

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', ...

698461 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 →