Agent skill

Cut Ready

by elithrar in elithrar/dotfiles

Prepare or review CAD and vector artwork for physical fabrication, cutting, printing, or machining.

MITAuto-check passed

Install Cut Ready

skills CLI
$ npx skills add elithrar/dotfiles --skill cut-ready -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install elithrar/dotfiles cut-ready --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/elithrar/dotfiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/cut-ready .claude/skills/cut-ready && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
cut-ready
GitHub stars
202
Token cost
~1.9k tokens
SKILL.md length
932 words
Files
10 (incl. references)
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

Prepare or review CAD and vector artwork for physical fabrication, cutting, printing, or machining.

  • Works in 8 steps: Classify the production job. Identify… → Build an evidence ledger. Classify… → Freeze accepted work. Before a revision,… → …
  • Production files
  • SKILL.md covers Load the required references, Required outcomes, Guardrails and Readiness labels
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Cut Ready is an agent skill from elithrar/dotfiles. Prepare or review CAD and vector artwork for physical fabrication, cutting, printing, or machining. Use for production files, scale, contours, fit, bends, and vendor handoff; not digital-only graphics, 3D-print meshes, or CAD explanation without a production artifact.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including reference files (for example `agents/openai.yaml`, `evals/evals.json` and `references/2d-preflight.md`).

The repository describes itself as: dotfiles for my macOS & Linux environments ⌨️. The licence is MIT.

When your agent uses it

  • Production files
  • Not digital-only graphics
  • 3D-print meshes
  • CAD explanation without a production artifact

Example prompts

  • “/cut-ready”

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Classify the production job. Identify flat profile cutting, cut vinyl or stencil, printed contour-cut artwork, production vector drawing…
  2. Build an evidence ledger. Classify controlling dimensions using the intake reference, keeping measured and specified values separate from…
  3. Freeze accepted work. Before a revision, record the baseline, frozen elements, editable elements, invariants, and acceptance checks…
  4. Maintain one authoritative model. For new work, establish a base model and shared dimensional specification; for accepted work, reuse…
  5. Run technical preflight. Apply every relevant reference. Open the exported file in a second compatible tool or independent import path…
  6. Run visual and semantic review. Render the actual production export at actual size and useful magnifications. Inventory every visible…
  7. Verify the manufacturing handoff. When the vendor is named, use its current official design rules. If authorized and available, upload the…
  8. Package the result. Return the requested production files with the source and preview needed to use or verify them. Summarize relevant…

What it can do on your machine

Read from SKILL.md and the folder at commit e007b24. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cut Ready loads about 1.9k tokens when it runs, and up to ~13k if it reads all its reference files. Until then it costs about 70 tokens; SKILL.md has 932 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~70
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~13k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from elithrar/dotfiles at commit e007b24, republished under its MIT licence (© elithrar). 932 words, ~1,856 tokens.

Download SKILL.mdSave it as .claude/skills/cut-ready/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.
name
cut-ready
description
Prepare or review CAD and vector artwork for physical fabrication, cutting, printing, or machining. Use for production files, scale, contours, fit, bends, and vendor handoff; not digital-only graphics, 3D-print meshes, or CAD explanation without a production artifact.

Cut-ready fabrication

Treat cut-ready as a verified status, not a synonym for "file created." Do not claim it until the applicable evidence, geometry, readback, visual, and vendor gates pass. For an audit-only request, report findings and readiness without modifying or uploading files.

Load the required references

WorkReference
Establish dimensions, source confidence, and a revision contractintake-and-revision
Create or review 2D cut geometry2d-preflight
Create stickers, decals, masks, gauge faces, or annotated vector drawingsgraphics-and-diagrams
Lay out engineering sheets, dimensioned views, or fabrication letteringengineering-drawings
Generate CAD, revise a base model, or add an output formatcad-generation
Create or review STEP/STP geometry3d-preflight
Prepare a vendor handoff or SendCutSend uploadvendor-handoff

Read a reference when its manufacturing decision or validation step is needed; do not load every file for a narrow revision. Re-check the named vendor's current official requirements when material, thickness, minimum-feature, tolerance, bend, or file-format rules could have changed.

Required outcomes

Satisfy each outcome that applies to the requested job. Adapt the working order while preserving dependencies: resolve controlling inputs before modeling, and validate exports before claiming readiness.

  1. Classify the production job. Identify flat profile cutting, cut vinyl or stencil, printed contour-cut artwork, production vector drawing, formed sheet material, or machined 3D solid. Record the process, physical substrate or stock, thickness when relevant, units, finished size, quantity, finish, critical dimensions, tolerances, application face, handed or mirrored variants, and target vendor when known. Ask one focused question only when a missing answer changes geometry, output, fit, or safety.
  2. Build an evidence ledger. Classify controlling dimensions using the intake reference, keeping measured and specified values separate from assumptions. Never turn a photo estimate into an exact historical or physical dimension. State the scale anchor, perspective limits, and uncertainty for reconstructions.
  3. Freeze accepted work. Before a revision, record the baseline, frozen elements, editable elements, invariants, and acceptance checks. Create a new revision unless the user explicitly asks to replace the baseline. Treat "change nothing else" literally.
  4. Maintain one authoritative model. For new work, establish a base model and shared dimensional specification; for accepted work, reuse them. Derive every revision, variant, drawing, preview, and new format from that source. Prefer native CAD, a parametric model, or a checked-in generator over hand-edited exports. Reuse accepted components and canonical assets; encode controlling dimensions and expected features as assertions. Follow the CAD-generation reference for lineage and cross-format checks.
  5. Run technical preflight. Apply every relevant reference. Open the exported file in a second compatible tool or independent import path. Compare units, physical bounds, layers, bodies, contours, features, orientation, and critical dimensions with the source. Treat unexpected counts or importer healing as failures to diagnose.
  6. Run visual and semantic review. Render the actual production export at actual size and useful magnifications. Inventory every visible object and inspect negative space, alignment, z-order, occlusion, overlaps, arrow and leader termination, mirrored text, cut direction, feature placement, and installed orientation. Reconcile labels with measured geometry and the current variant. Compare with source references and the accepted baseline. After a correction, regenerate dependent outputs and repeat affected numeric and visible checks; a parser-only check is insufficient.
  7. Verify the manufacturing handoff. When the vendor is named, use its current official design rules. If authorized and available, upload the file without ordering and inspect the vendor preview. Confirm displayed size, material, thickness, services, bend directions, and feature count. Never place an order or approve production without explicit authorization.
  8. Package the result. Return the requested production files with the source and preview needed to use or verify them. Summarize relevant process, units, assumptions, checks, and gaps in the handoff. Add a separate README or validation report only for a requested package or when manufacturing details would otherwise be lost.
Show full SKILL.md (310 more words)Show less

Guardrails

  • Resolve missing inputs before the geometry decision they control. Complete independent edits and checks first; a color-only revision of accepted artwork need not re-open unchanged material or dimensional decisions. Preserve prior authorization and the user's requested scope. Explain any actual blocking instruction and the affected decision.
  • Do not invent vendor limits, tolerances, bend radii, K factors, kerf values, historical dimensions, or missing geometry. Retrieve current primary-source rules or report the blocker.
  • Do not compensate for kerf, bend allowance, or finishing unless the manufacturing workflow explicitly requires it.
  • Do not describe ordinary PVC or automotive vinyl as laser-safe. Default to a drag-knife or plotter unless the exact material manufacturer and machine operator explicitly approve laser processing.
  • Do not silently simplify, redraw, rescale, mirror, repair, or convert accepted geometry. Explain any required manufacturing change and preserve the original.
  • Do not use a vendor-specific cutline name, spot color, bleed, safe area, resolution, or color mode as a universal rule. Retrieve the named vendor's current specification.
  • Do not call a STEP file valid merely because it has a .step extension, or a DXF valid merely because it opens. Require geometry and readback checks.
  • Do not treat a vendor's successful upload as proof that scale, bend direction, or design intent is correct. Inspect the preview and configuration.

Readiness labels

Use exactly one status in the final handoff:

  • Cut-ready: All applicable local preflight, independent readback, visual review, and named-vendor preview checks passed.
  • Locally preflighted: Local and independent checks passed, but vendor import or physical proof remains unverified.
  • Draft / reconstruction: Geometry depends on unconfirmed dimensions, photo inference, or unresolved aesthetic approval.
  • Blocked: A missing manufacturing input or failed check can materially change the part.

Complete authorized corrections and affected checks before the final handoff. Report the status first, followed by the production files, intended process and material, exact passed checks, remaining proof step, and any uncertainty.

© elithrar, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 9 other files (references) in .agents/skills/cut-ready of elithrar/dotfiles.

  • SKILL.md
  • agents/openai.yaml
  • evals/evals.json
  • references/2d-preflight.md
  • references/3d-preflight.md
  • references/cad-generation.md
  • references/engineering-drawings.md
  • references/graphics-and-diagrams.md
  • references/intake-and-revision.md
  • references/vendor-handoff.md

Open the folder on GitHubat commit e007b24

Compare with similar skills

Cut Ready next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cut Ready compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cut Ready this skillelithrar/dotfiles202—~1.9kAutomated safety check: PassMIT
Vector Searchruvnet/ruflo74k—~1.5kAutomated safety check: NotesMIT
Hunt RAG Vectorsickn33/agentic-awesome-skills47k1 repos~3kAutomated safety check: PassMIT
Parametric CAD Modelingearthtojake/text-to-cad19k—~2.8kAutomated safety check: PassMIT
Cutting A ReleaseTriliumNext/Trilium38k—~3.2kAutomated safety check: PassAGPL-3.0
Vector Database Opssickn33/agentic-awesome-skills47k2 repos~2.2kAutomated safety check: PassMIT

Similar skills

  • Vector Search

    ruvnet/ruflo

    Vector search via embeddings (large-scale HNSW) and ruvllmhnsw (WASM router for ≤11 hot patterns), with RaBitQ 1-bit quantization for 32× memory reduction

    74k GitHub stars~1.5k tokensUpdated today
    AI & LLM EngineeringAuto-check: notes
  • Hunt RAG Vector

    sickn33/agentic-awesome-skills

    Hunt vector-store / embedding-layer weaknesses in RAG pipelines (OWASP LLM08 Vector and Embedding Weaknesses)

    47k GitHub starsUsed in 1 repo~3k tokens
    AI & LLM EngineeringAuto-check passed
  • Parametric CAD Modeling

    earthtojake/text-to-cad

    Creates and edits parametric CAD parts in Python, organizes multi-model projects, exports to STEP, STL, 3MF or GLB, and opens existing CAD files for visual review.

    19k GitHub stars~2.8k tokensUpdated today
    DevelopmentAuto-check passed
  • Cutting A Release

    TriliumNext/Trilium

    A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.

    38k GitHub stars~3.2k tokensUpdated today
    DevelopmentAuto-check passed
  • Vector Database Ops

    sickn33/agentic-awesome-skills

    Deploy, manage, and optimize vector databases for AI applications.

    47k GitHub starsUsed in 2 repos~2.2k tokens
    DatabasesAuto-check passed
  • Vector Embed

    ruvnet/ruflo

    Generate embeddings via npx ruvector@0.2.25 embed text (ONNX all-MiniLM-L6-v2, 384-dim), normalize, and store in HNSW index

    74k GitHub stars~591 tokensUpdated today
    AI & LLM EngineeringAuto-check: notes

More from elithrar/dotfiles

All 12 skills in this repo
  • Prompt Engineer

    elithrar/dotfiles

    Audit and revise system prompts, developer instructions, tool descriptions, and reusable LLM prompt templates.

    202 GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Code Reviewer

    elithrar/dotfiles

    Review a specified code change for actionable defects. An agent skill from elithrar/dotfiles.

    202 GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Logging Sucks

    elithrar/dotfiles

    Design or review structured application logging, canonical request events, correlation, redaction, and sampling.

    202 GitHub stars~720 tokensUpdated today
    Auto-check passed
  • Motronic

    elithrar/dotfiles

    Diagnose Porsche Carrera 3.2 Bosch Motronic faults and interpret DME ROMs or calibration changes.

    202 GitHub stars~753 tokensUpdated today
    Auto-check passed
  • Neo Industrial Design

    elithrar/dotfiles

    Design or restyle web interfaces in the user's neo-industrial or editorial-brutalist style.

    202 GitHub stars~940 tokensUpdated today
    Auto-check passed
  • Web Perf

    elithrar/dotfiles

    Diagnose page-load and interaction performance using browser traces, network evidence, and source code.

    202 GitHub stars~721 tokensUpdated today
    Auto-check passed

Questions about Cut Ready

What does Cut Ready do?

Prepare or review CAD and vector artwork for physical fabrication, cutting, printing, or machining. Cut Ready is an agent skill from elithrar/dotfiles. Prepare or review CAD and vector artwork for physical fabrication, cutting, printing, or machining.

When should I use Cut Ready?

Cut Ready fits situations like: production files; not digital-only graphics; 3D-print meshes; CAD explanation without a production artifact.

How do I install Cut Ready in Claude Code?

Run `npx skills add elithrar/dotfiles --skill cut-ready -a claude-code`. Or copy the skill folder (.agents/skills/cut-ready in elithrar/dotfiles) into .claude/skills/cut-ready in your project. Claude Code loads it when a task matches its description.

How do I install Cut Ready in Codex?

Run `npx skills add elithrar/dotfiles --skill cut-ready -a codex`. Or copy the skill folder (.agents/skills/cut-ready in elithrar/dotfiles) into .agents/skills/cut-ready in your project. Codex loads it when a task matches its description.

Can I use Cut Ready in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add elithrar/dotfiles --skill cut-ready -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cut-ready, .gemini/skills/cut-ready, .github/skills/cut-ready and .opencode/skills/cut-ready in your project.

What does Cut Ready need to run?

SKILL.md names no scripts, command-line tools or credentials: Cut Ready is instructions for the agent only.

Does Cut Ready access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Cut Ready safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Cut Ready use?

Cut Ready is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cut Ready use?

About 1.9k tokens (SKILL.md is roughly 7.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 11k tokens, read only when the agent opens those files.

What are the alternatives to Cut Ready?

Skills that share tags, products or a category with Cut Ready: Vector Search (ruvnet/ruflo, 74k stars), Hunt RAG Vector (sickn33/agentic-awesome-skills, 47k stars), Parametric CAD Modeling (earthtojake/text-to-cad, 19k stars) and Cutting A Release (TriliumNext/Trilium, 38k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cut Ready?

elithrar (a GitHub user) maintains it in elithrar/dotfiles, which has 202 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 8, 2026.

Source: elithrar/dotfiles on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.