makerspace

Generates tiered packet scaffolds for jig and fixture design.

1|Updated May 9, 2026
One-click install
npx skills add https://github.com/tonykoop/claude-skills --skill makerspace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: makerspace
Source: https://github.com/tonykoop/claude-skills/tree/main/plugins/maker/skills/makerspace
Command: npx skills add https://github.com/tonykoop/claude-skills --skill makerspace

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires yaml, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Plan and enforce repeatable, verifiable shop packets for jig and fixture design, enabling consistent fabrication outcomes across spaces.

Core Features & Use Cases

  • Generates tiered packet scaffolds (design.md, BOM, cut-list.csv, op-sequence.md, safety-notes.md) and supports repo-backed handoffs.
  • Provides space-aware routing with machine, safety, and reference materials on demand.
  • Keeps outputs versioned and auditable to support cross-runtime deployment.

Quick Start

Provide a Tier 1 scaffold for a new project and let the orchestrator fill in the details.

Frequently Asked Questions about makerspace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create repeatable shop packets for jig and fixture design?

Shop packets for jig and fixture design are created by generating tiered scaffolds including design.md, BOM, cut-list.csv, op-sequence.md, and safety-notes.md to ensure verifiable fabrication outcomes across spaces.

What is a shop packet and when do I need one for fabrication workholding?

A shop packet is a versioned, modular handoff artifact for fabrication workholding that separates design intent, tool constraints, and safety checks to enable consistent, repeatable outcomes across different maker spaces.

Can I use this skill to plan jig fixtures for a home shop or Maker Nexus-style space?

Yes, this skill applies to both home shops and Maker Nexus-style spaces, providing space-aware routing with machine constraints, safety materials, and on-demand references tailored to each environment.

Do I need YAML to manage fabrication shop packet manifests and versioning?

Yes, YAML is required as a dependency to enforce frontmatter contracts, manage manifests, and maintain versioning for cross-space artifact generation during modular fabrication handoffs.

What's the best way to handle design intent separation and tool constraints for workholding jigs?

Design intent separation and tool constraints for workholding jigs are handled by enforcing frontmatter contracts within tiered packet scaffolds, keeping fabrication outputs versioned and auditable for cross-runtime deployment.

What are the limitations of using shop packets for cross-space fabrication handoffs?

Shop packets require strict adherence to frontmatter contracts and manifest schemas to function correctly, meaning any deviation from the enforced versioning or safety checks can disrupt cross-space artifact generation and modular handoffs.