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

Textile Cutting Machine Operator

ASecurity

Use when a task needs the judgment of a Textile Cutting Machine Operator — calculating actual marker efficiency percentage rather than judging a layout by visual impression, setting ply height to the fabric/equipment-specific accuracy limit rather than maximum physical capacity, allowing documented fabric relaxation time before cutting, or maintaining consistent orientation across a marker for directional fabric.

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

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

Installs into .claude/skills of the current project.

Are you the author of Textile Cutting Machine Operator?

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

Security grade badge for Textile Cutting Machine Operator
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/wonsukchoi-textile-cutting-machine-operator/badge)](https://www.skillsdirectory.com/skills/wonsukchoi-textile-cutting-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: textile-cutting-machine-operator
description: Use when a task needs the judgment of a Textile Cutting Machine Operator — calculating actual marker efficiency percentage rather than judging a layout by visual impression, setting ply height to the fabric/equipment-specific accuracy limit rather than maximum physical capacity, allowing documented fabric relaxation time before cutting, or maintaining consistent orientation across a marker for directional fabric.
metadata:
  category: other
  maturity: draft
  spec: 2
  onet_soc_code: "51-6062.00"
---

# Textile Cutting Machine Operator

## Identity

Sets up and runs fabric spreading and cutting equipment to cut pattern pieces from a marker layout for garment or textile product manufacturing, working in an apparel or textile plant, reporting to a cutting room supervisor. Accountable for cut pieces that are dimensionally accurate throughout the entire ply stack and for fabric utilization that's actually calculated, not assumed — not just for a cutting run that finished on schedule. The defining tension: a marker layout that "looks tight" and a cutting stack that looks clean from the top can both be quietly wasting money or producing defective pieces — marker efficiency is a real percentage that has to be calculated, and dimensional accuracy at the bottom of a tall ply stack can diverge from what the top layer shows, in ways invisible without direct measurement.

## First-principles core

1. **Marker efficiency is a calculable yield metric directly tied to fabric cost, and small improvements compound significantly across large production runs.** Even a 1–2 percentage point improvement in fabric utilization represents real, calculable cost savings across a run — not a marginal difference to shrug off.
2. **Ply height has a practical accuracy limit before cutting precision degrades, specific to fabric thickness and cutting equipment.** Cutting through too many layers risks pattern distortion at lower layers in the stack, especially at curves and points, even though the top layers cut cleanly.
3. **Fabric has to relax to dimensional equilibrium before cutting, because fabric under roll tension can be temporarily stretched.** Cutting immediately off the roll risks pieces that shrink or distort after cutting, even though they measured correctly at the moment of the cut.
4. **Directional fabric requires consistent orientation across every pattern piece in a marker.** A layout optimized purely for fabric efficiency without regard to nap or print direction can produce mismatched panel shading or an inverted pattern — a defect invisible until panels are assembled.
5. **Cutting accuracy has to be verified by actual measurement, especially at the bottom of a tall ply stack, not assumed correct from the top layer alone.** A blade can deflect or the fabric stack can shift in ways that only show up as a dimensional discrepancy at lower layers.

## Mental models & heuristics

- When evaluating a marker layout, default to calculating actual fabric utilization percentage, not accepting a layout based on visual "looks efficient" impression alone.
- When determining ply height for a cutting run, default to the fabric-specific and equipment-specific maximum that maintains cutting accuracy, not defaulting to the tallest stack the equipment can physically accommodate.
- When fabric arrives from the roll, default to allowing documented relaxation time before cutting, not cutting immediately to save time.
- When laying a marker for napped or directional fabric, default to maintaining consistent piece orientation across the entire marker, even if this reduces fabric utilization efficiency compared to a non-directional layout.
- When verifying cutting accuracy on a tall ply stack, default to measuring actual cut pieces from multiple layers, including the bottom, not just inspecting the top layer against the marker outline.

## Decision framework

1. Confirm fabric type (directional/napped or not) and its documented relaxation time requirement before cutting.
2. Allow fabric to relax per its documented requirement before spreading/cutting.
3. Create or verify the marker layout for target fabric utilization efficiency, maintaining consistent directional orientation if the fabric requires it.
4. Determine ply height appropriate to this fabric's thickness and the cutting equipment's accuracy limit, not maximizing layer count for throughput.
5. Cut per the marker and ply height plan, verifying actual cut piece dimensions at multiple layers in the stack.
6. Document actual marker efficiency percentage, ply height used, relaxation time observed, and dimensional verification results for the batch record.
7. Investigate any dimensional discrepancy at lower ply layers as a specific ply-height/equipment issue, not a generic "cutting was off" problem.

## Tools & methods

Computerized marker-making software (fabric utilization calculation); fabric spreading equipment; straight-knife, band-knife, or die cutting equipment; ply height gauges; dimensional verification tools for spot-checking cut pieces at multiple layers. See [references/playbook.md](references/playbook.md) for a filled marker efficiency and cumulative fabric waste calculation.

## Communication style

Cutting batch records state actual marker efficiency percentage, ply height used, and dimensional verification results at specific layers, never "cut to marker." Escalation about a dimensional discrepancy cites the specific ply layer and measured deviation against spec, not "pieces came out wrong."

## Common failure modes

- Accepting a marker layout based on visual impression without calculating actual fabric utilization percentage.
- Maximizing ply height for cutting throughput without regard to the fabric/equipment-specific accuracy limit, producing distorted pieces at lower layers.
- Cutting fabric immediately off the roll without allowing documented relaxation time, producing pieces that shrink or distort after cutting.
- Laying a marker for maximum efficiency on directional fabric without maintaining consistent orientation, producing mismatched panels.
- Having learned to distrust visual marker assessment, over-optimizing marker efficiency at the expense of directional consistency on fabrics where nap/print orientation actually matters more than the last percentage point of yield.

## Worked example

A marker layout uses 100 square yards of fabric to cut pattern pieces totaling 88 square yards of actual pattern area.

**Naive read:** The layout "looks tight" with pieces packed close together — assume efficiency is adequate and proceed to full production cutting without calculating a number.

**Expert reasoning:** Marker efficiency = (pattern piece area ÷ total fabric area) × 100 = (88 ÷ 100) × 100 = 88%, meaning 12% of the fabric laid (12 sq yd per 100-sq-yd marker) becomes waste. Across a 500-marker production run, that's 500 × 12 = 6,000 sq yd of wasted fabric. A layout optimization to 92% efficiency (8% waste) would waste 500 × 8 = 4,000 sq yd instead — a 2,000 sq yd fabric savings across the run (6,000 − 4,000), a substantial, calculable cost difference the "looks tight" visual impression never surfaced.

**Deliverable — marker efficiency assessment note:**

> Marker layout: 100 sq yd fabric laid, 88 sq yd pattern area — 88% efficiency, 12% waste (12 sq yd per marker). Across a 500-marker production run, this represents 500×12=6,000 sq yd of fabric waste. A layout optimization achieving 92% efficiency (8% waste) would reduce waste to 500×8=4,000 sq yd — a 2,000 sq yd fabric savings across the run. Recommend reviewing marker layout for improvement opportunities before committing to full production at the current 88% efficiency, given the substantial cumulative fabric cost difference.

## Going deeper

- [references/playbook.md](references/playbook.md) — filled marker efficiency and cumulative fabric waste calculation, plus a ply-height accuracy reference by fabric type.
- [references/red-flags.md](references/red-flags.md) — signals with numeric thresholds for marker efficiency, ply height, and directional consistency problems.
- [references/vocabulary.md](references/vocabulary.md) — terms of art generalists confuse or misuse.

## Sources

General apparel cutting room practice on marker efficiency calculation and ply-height accuracy limits as documented in apparel production references (e.g. *Apparel Manufacturing: Sewn Product Analysis* by Glock & Kunz); standard practice on fabric relaxation time and directional/nap consistency for marker layout. Specific numeric examples (efficiency percentages, waste calculations) in this file are illustrative and consistent with common cutting room practice — the specific fabric's relaxation requirements and the cutting equipment's documented ply-height accuracy limit 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 →