AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Thorlabs Blender Optical Path

skill-k-telux-opticalmodeler-thorlabs-blender-optical-path · by k-telux

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.

No reviews yet
0 installs
19 views
0.0% view→install

Install

$ agentstack add skill-k-telux-opticalmodeler-thorlabs-blender-optical-path

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-k-telux-opticalmodeler-thorlabs-blender-optical-path)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
26d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Thorlabs Blender Optical Path? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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

Authority and revision rules

  1. 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.
  2. Freeze an accepted package. Start a new revision for every correction; never overwrite the prior evidence package.
  3. 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.
  4. Translate every correction into object families, world-space geometry, a measurable gate, and required evidence before editing.
  5. 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

  1. Build a machine-readable map: schematic node -> experimental role -> real asset -> optical/fiber/electrical ports -> support path.
  2. Inventory every branch, component, beam segment, beam height, aperture, connector, and required detector endpoint.
  3. 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.
  4. Solve optical constraints first: centers, surface normals, reflection, splitting planes, branch endpoints, and zero-radius clearance.
  5. Solve mechanics post-first from verified table holes through real fasteners, clamps, holders, posts, mount faces, and device interfaces.
  6. Fix the shared placement or transform root cause. Prove one representative repeated assembly before propagation, then reopen and recheck every copy.
  7. Render bright audit views before beauty views. Use cutaways or transparency only to expose hidden, already-measured interfaces.
  8. 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.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.