mcpbeat Sign in

Thorlabs Blender Optical Path Agent Skill

Build, audit, and revise physically plausible Blender optical-table figures from 2D schematics and manufacturer CAD. Use for Thorlabs-compatible mirrors, lens mounts, beamsplitters, posts, fiber launches, apertures, detectors, optical topology, fail-closed evidence, or Nature-style photonics renders.

5k tokens
context cost
the whole folder, loaded on every use
6
files
instructions only
0
copies elsewhere
how many repositories repackaged it
212
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/k-telux/OpticalModeler --skill thorlabs-blender-optical-path

The instruction itself

7 sections, as written by the author

Thorlabs Blender Optical Path

Convert a 2D optical schematic into a physically explainable, independently auditable Blender scene.

Load the relevant references

  • Read physical-gates.md before geometry, CAD placement, or mechanical review.
  • Read evidence-contract.md before declaring any PASS or preparing a release.
  • Read history-derived-rules.md when revising an existing scene or when old fixes may have regressed.
  • Read project-case-study.md for the complete G1/G2 2D-to-3D example.

Authority and revision rules

  • Apply system constraints first, then the newest explicit user wording or annotated screenshot, then active project rules, then this general skill, and only then older artifacts or PASS labels.
  • Freeze an accepted package. Start a new revision for every correction; never overwrite the prior evidence package.
  • Keep one writer for the shared Blender generator. Use helpers as read-only optical, mechanical, CAD, evidence, and visual reviewers unless an isolated write scope is explicit.
  • Translate every correction into object families, world-space geometry, a measurable gate, and required evidence before editing.
  • Use BLOCKED or UNVERIFIED when real geometry or evidence is missing. File existence, imported CAD, process success, labels, AABB contact, and self-reported text are not proof.

Core workflow

  • Build a machine-readable map: schematic node -> experimental role -> real asset -> optical/fiber/electrical ports -> support path.
  • Inventory every branch, component, beam segment, beam height, aperture, connector, and required detector endpoint.
  • Acquire official CAD when licensing permits. Record part number, source URL, SHA-256, unit scale, bbox, local optical axis, surface normal, aperture, and provenance. Mark modeled or surrogate parts explicitly.
  • Solve optical constraints first: centers, surface normals, reflection, splitting planes, branch endpoints, and zero-radius clearance.
  • Solve mechanics post-first from verified table holes through real fasteners, clamps, holders, posts, mount faces, and device interfaces.
  • Fix the shared placement or transform root cause. Prove one representative repeated assembly before propagation, then reopen and recheck every copy.
  • Render bright audit views before beauty views. Use cutaways or transparency only to expose hidden, already-measured interfaces.
  • Complete the saved-scene, visual, export, document, hash, and rule-compliance gates in the evidence contract.

Required semantic separation

  • Treat free-space optical rays, guided fiber, and electrical/coaxial cables as different object families, materials, ports, and audit records.
  • Terminate free-space light at the physical coupling surface; continue only the guided fiber from the ferrule/FC interface.
  • Use open geometry for apertures and slits. A centered ray through an opaque disk is a collision, not a PASS.
  • Remove duplicate surrogates and unexplained placeholders after the real or declared modeled assembly exists.

Publication rendering

After physical gates pass, produce a clean editorial scene with restrained metals, readable black-anodized edges, physically modest glass, thin emissive beam cores, soft halos, and uncluttered labels. Preserve topology and geometry while changing camera, lighting, materials, or presentation. Nature-style appearance never replaces mechanical evidence.

Completion language

  • PASS: every applicable active gate has fresh evidence.
  • PARTIAL/SCOPED: only a declared subset was audited.
  • UNVERIFIED: required evidence is missing or cannot distinguish the claim.
  • BLOCKED: a known requirement fails.

Never promote PARTIAL/SCOPED to whole-system PASS.

Other skills for the same job

different authors, same section of the catalogue
Protocolsio Integration
by christophacham
×4

Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.

16k tokens
Tailored Resume Generator
by frostant
×4

Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances

3k tokens
Excalidraw Diagram Generator
by github
vendor ×3

Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.

36k tokens scripts
Expo Dev Client
by openai
vendor ×3

Build and distribute Expo development clients locally or via TestFlight

961 tokens
Executing Plans
by ZhanlinCui
×3

Use when you have a written implementation plan to execute in a separate session with review checkpoints

542 tokens
Anndata
by christophacham
×3

Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.

16k tokens
Benchling Integration
by christophacham
×3

Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.

14k tokens
Biopython
by christophacham
×3

Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.

24k tokens

How to use it

Copy the folder

Take k-telux/thorlabs-blender-optical-path from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.