agentleFS
Sign inStart free
JiamingShi-JsPhysJiamingShi-JsPhys/chelate-shell/skills/3d-modeler/SKILL.md

3d-modeler

Skill10 starsChanged 6 days agoMITView on GitHub

Pure-Python OBJ mesh work: generate a mesh from a JSON spec, merge several OBJ files, and audit an existing mesh (winding, degenerate faces, bounds). Runs inside the process sandbox.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run this exact form — do not read the source tree:

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

3d-modeler

Generates, merges and inspects OBJ meshes with no third-party geometry library. It does not render or slice.

  • Stage: domain_extensions · Sandbox: yes · Dependencies: stdlib only

Quick Execution

Run this exact form — do not read the source tree:

python scripts/run.py --root <WS> --action process --input spec.json
  • --spec is an alias of --input; --merge other.obj may be repeated.
  • Point --input at an .obj to audit or merge instead of generate.
  • Output lands under <WS>/process/; the gate in <WS>/process/gates/.

When to use

  • A mesh must be generated from a parameter spec.
  • Several OBJ files must be combined into one.
  • An existing mesh must be audited for defects.

When NOT to use

  • Rendering, slicing or 3D printing preparation.
  • Formats other than OBJ.

Actions

--actionDoesExtra arguments
processGenerate / merge / audit--input <spec.json|.obj> [--spec ...] [--merge other.obj ...]

Hard constraints

  • Never modify the input mesh in place.
  • Report defects, do not silently repair them.

Outputs

  • <WS>/process/<name>.obj — the generated or merged mesh.
  • <WS>/process/gates/3d-modeler_<ts>.json — the gate result and QC findings.

Failure handling

  • A malformed spec or OBJ exits non-zero with the offending line.
  • A merge with mismatched vertex layout is refused, not forced.

Limitations

  • OBJ only; no textured or animated formats.
  • Pure Python, so very large meshes are slow.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free