modly Skill
What it does
Desktop app to generate 3D models from images or prompt using local AI — runs entirely on your GPU
- Connects Instruction files the AI reads; connects to nothing
- Account or key No key needed
- Category Other
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/lightningpixel-modly)Similar Skills
Same kind of work, ordered like the Skills list
| This one modly | llmfit | claude-video | VideoCaptioner | patent-disclosure-skill | |
|---|---|---|---|---|---|
| Maker | lightningpixel | AlexsJones | bradautomates | WEIFENG2333 | handsomestWei |
| Skills | 1 | 1 | 1 | 1 | 1 |
| GitHub stars | 8,665 | 39,004 | 20,889 | 16,539 | 13,468 |
| Last code change | Nov 15, 2026 | Nov 12, 2026 | Sep 25, 2026 | Sep 12, 2026 | Nov 15, 2026 |
| License | – | MIT | MIT | GPL-3.0 | MIT |
1 skills (instruction sets) by lightningpixel that an AI reads and follows · not an MCP server
How a Skill differs from MCP
MCP = the hands
Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.
Skill = the manual
A text file that teaches the AI how to do a task. It connects to nothing.
Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.
Works with
Not stated by the maker · SKILL.md skills work in apps that support Agent Skills, such as Claude Code, Codex and Cursor
Install
Is it safe?
- Who made it
GitHub account lightningpixel (person), 6 years old
- Use and upkeep
★ 8,665 stars · code last changed Nov 15, 2026
- Any scripts?
2 scripts that can run on a computer: agent.py, test_agent.py
- Uses the internet?
Scripts that go online: agent.py
- Changes machine-wide settings?
No hooks or writes to machine settings found
Checked automatically from the repo files at commit a471509 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
First: which AI do you use?
Pick your app and this page shows only how to install it there
Option 1Upload to claude.ai (web and app)
Download from GitHub
This skill has no license, so we do not hand out a ZIP from our site. Download it from GitHub and arrange the folder yourself, or use "Let the AI install it" above, which is easier
Download from GitHub (whole repo) ↗
Unzip it, then zip only the tools/modly-cli folder again. The ZIP must have a modly-cli folder with SKILL.md at the top level, no loose files
Open Skills on claude.ai and upload
+Create skillUpload a skillpick modly-cli.zip
No Upload button? Turn on file creation first
SettingsCapabilitiesCode execution and file creation
Turn on Code execution and file creation first (newer menus: Create and edit files) · personal plans: Settings → Capabilities · Team/Enterprise: an admin turns it on under Organization settings → Plugins & skills · every plan, including Free
Upload once; it works in claude.ai and Claude Desktop, and in recent Claude Code signed in with a Claude account (not with an API key)
Cowork and cloud sessions use the skills turned on in your claude.ai account, not ~/.claude/skills on your computer (Claude Desktop scheduled tasks run locally and still load it)
Checked against official docs Nov 12, 2026 · Source: support.claude.com, support.claude.com, code.claude.com
Option 1Let Claude Code install it
Copy this sentence and paste it into a Claude Code chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Restart Claude Code, then type /modly-cli or ask for a matching task and Claude picks it up
Checked against official docs Nov 12, 2026 · Source: code.claude.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.claude/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/lightningpixel/modly.git /tmp/popnx-skill-lightningpixel-modly-a471509 && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-lightningpixel-modly-a471509/tools/modly-cli' ~/.claude/skills/modly-cliRestart Claude Code, then type /modly-cli or ask for a matching task and Claude picks it up
ChatGPT desktop app
The ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills
Option 1Let ChatGPT install it
Open Codex in the ChatGPT desktop app and paste this sentence into the chat
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Option 2Put the folder there yourself
Put the modly-cli folder at ~/.agents/skills/modly-cli
~ is your home folder ($HOME)
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/lightningpixel/modly.git /tmp/popnx-skill-lightningpixel-modly-a471509 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-lightningpixel-modly-a471509/tools/modly-cli' ~/.agents/skills/modly-cli
After installing
- ChatGPT desktop app: open Skills in the sidebar to see that the skill is there
- To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
- Codex picks up newly installed skills by itself; if one does not show up, restart Codex
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
ChatGPT on the web and mobile
Skills you install yourself do not work here; only skills that come with a plugin from the directory
To use this skill with ChatGPT, use the ChatGPT desktop app as above
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Option 1Let Codex install it
Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/lightningpixel/modly.git /tmp/popnx-skill-lightningpixel-modly-a471509 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-lightningpixel-modly-a471509/tools/modly-cli' ~/.agents/skills/modly-cliRestart Codex, then ask for a matching task; Codex lists the skill
Option 1Let Cursor install it
Copy this sentence and paste it into a Cursor chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
In Cursor’s Agent chat, type / and pick modly-cli
Checked against official docs Nov 12, 2026 · Source: cursor.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.cursor/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/lightningpixel/modly.git /tmp/popnx-skill-lightningpixel-modly-a471509 && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-lightningpixel-modly-a471509/tools/modly-cli' ~/.cursor/skills/modly-cliIn Cursor’s Agent chat, type / and pick modly-cli
Option 1Let the AI install it
For other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.
Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026
✓ Commands checked Nov 16, 2026
View the original SKILL.md
The text below comes from the maker’s repo, not from PopNx MCP
6,956 characters · Open the full file on GitHub
---
name: modly-cli
description: Use when an agent needs to call a running Modly desktop instance from the terminal to generate/export image-to-3D assets through canonical JSON-first automation commands.
version: 1.2.0
author: Modly
license: MIT
metadata:
hermes:
tags: [modly, image-to-3d, cli, automation, agents]
related_skills: []
---
# Modly CLI
## Overview
Modly exposes a local API at `http://127.0.0.1:8765` while the official desktop app is running. The stdlib-only CLI at `tools/modly-cli/agent.py` is an agent helper over the canonical automation contract:
- `health`
- `model`
- `workflow-run`
- `capability`
- `process-run`
Final machine-readable JSON is printed to stdout. Progress JSON lines, when requested, are printed to stderr.
## Prerequisites
Launch the official Modly desktop app first, then check readiness:
```bash
python tools/modly-cli/agent.py health
```
Use `--compact` when another agent needs single-line JSON:
```bash
python tools/modly-cli/agent.py --compact health
```
`GET /health` is checked before business operations. If the app is unavailable, failures are structured:
```json
{
"ok": false,
"code": "API_UNAVAILABLE",
"message": "Cannot reach Modly API at ..."
}
```
## Canonical Commands
Inspect models through `/model/*`:
```bash
python tools/modly-cli/agent.py model list
python tools/modly-cli/agent.py model status
python tools/modly-cli/agent.py model params --model active
```
Start or resume workflow runs:
```bash
python tools/modly-cli/agent.py workflow-run start --image ./input.png --wait
python tools/modly-cli/agent.py workflow-run status <run_id>
python tools/modly-cli/agent.py workflow-run cancel <run_id>
```
Generate from an image and export the finished mesh:
```bash
python tools/modly-cli/agent.py generate \
--image ./input.png \
--output ./export.glb \
--progress
```
`generate` is a friendly wrapper around `POST /workflow-runs/from-image` and `GET /workflow-runs/{run_id}`. It does not silently fall back to `/generate/*`. The JSON includes recovery metadata:
```json
{
"ok": true,
"run": {"kind": "workflowRun", "id": "..."},
"workspace_path": "Default/model.glb",
"export_path": "/absolute/path/to/export.glb",
"meta": {
"status_command": "python tools/modly-cli/agent.py workflow-run status ...",
"cancel_command": "python tools/modly-cli/agent.py workflow-run cancel ...",
"legacy": false
}
}
```
Use `--no-export` when the caller only needs the workspace path. The hidden `export` helper remains available to download an existing workspace mesh, but it is not part of the canonical root command set:
```bash
python tools/modly-cli/agent.py export --path Default/model.glb --output ./model.glb
```
Discover capabilities or process runs only when the running server exposes the canonical contract:
```bash
python tools/modly-cli/agent.py capability list
python tools/modly-cli/agent.py process-run status <run_id>
```
If the contract is absent, the CLI fails closed:
```json
{
"ok": false,
"code": "UNSUPPORTED_PROCESS",
"message": "This process is not available through the canonical process-run contract."
}
```
## Model Selection
`--model auto` uses the active model reported by `/model/status`, then validates that id against `/model/all`. Explicit `--model` values are also validated against `/model/all`. The CLI does not infer hidden capabilities from model names, labels, or string fragments.
## Legacy Compatibility
The old `/generate/*` endpoints are explicit compatibility commands:
```bash
python tools/modly-cli/agent.py legacy job <job_id>
python tools/modly-cli/agent.py legacy cancel <job_id>
python tools/modly-cli/agent.py legacy generate --image ./input.png --output ./legacy.glb
```
Legacy responses include `meta.legacy: true`. Top-level `job`, `cancel`, `models`, and `params` aliases may still parse for older scripts, but they are not the documented canonical surface.
## Developer-Only API Helpers
Headless startup helpers live under `dev`:
```bash
python tools/modly-cli/agent.py dev serve-api --print-command
python tools/modly-cli/agent.py dev ensure-server
python tools/modly-cli/agent.py dev ensure-server --start --detach
```
These commands start or inspect only the FastAPI backend. They do not imply Electron/Desktop bridge readiness, scene operation readiness, extension process execution readiness, or full workflow support. Prefer launching the official desktop app for real agent workflows.
## Experimental ComfyUI Helpers
ComfyUI orchestration is outside the canonical Modly contract and lives under `experimental`:
```bash
python tools/modly-cli/agent.py experimental comfy-image \
--workflow Trellis2Workflow \
--prompt "clean object render, isolated on white" \
--comfy-output ./source.png
python tools/modly-cli/agent.py experimental generate-from-workflow \
--workflow Trellis2-Full \
--prompt "clean orthographic product render of a stylized robot toy" \
--output ./export.glb
```
`experimental generate-from-workflow --workflow <name> --output <path>` treats `--output` as the final artifact location. If the ComfyUI history contains a downloadable `.glb`, `.gltf`, `.obj`, `.stl`, or `.ply`, the CLI downloads that asset directly and does not call Modly health or generation. If the workflow only produces an image, the CLI downloads that image and falls back through the canonical Modly workflow-run generation path. If no supported asset or image is found, it fails with `code: "NO_WORKFLOW_OUTPUT"`.
## Hidden Helper Aliases
The top-level `status`, `export`, and `batch` helpers remain parseable for older scripts and agent ergonomics, but root help does not present them as canonical automation primitives. Prefer `health`, `model`, `workflow-run`, `capability`, and `process-run` when documenting the supported contract.
## Batch Workflow
The hidden `batch` helper generates meshes sequentially from a directory or manifest JSON through the canonical `generate` path:
```bash
python tools/modly-cli/agent.py batch \
--input-dir ./images \
--output-dir ./meshes \
--continue-on-error
python tools/modly-cli/agent.py batch \
--manifest ./jobs.json \
--output-dir ./meshes
```
Manifest files may be a JSON list, or an object with `jobs` or `images`. Each entry can be a string image path or an object with `image`, optional `output`, and optional `format`.
## Verification Checklist
- [ ] `python tools/modly-cli/agent.py health` returns `ok: true`.
- [ ] `python tools/modly-cli/agent.py model list` returns model entries.
- [ ] `python tools/modly-cli/agent.py generate --image <image> --output <mesh>` returns `ok: true`, `run.kind: workflowRun`, and recovery metadata.
- [ ] The reported `export_path` exists and has non-zero size when export is enabled.
- [ ] `python tools/modly-cli/agent.py workflow-run status <run_id>` can resume polling from metadata.
- [ ] `python tools/modly-cli/test_agent.py` passes.
Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
From GitHub
- GitHub stars
- 8,665
- Maker
- lightningpixel
- License
- Not stated
- Last code change
- Nov 15, 2026
- SKILL.md files in the repo (including translated copies and templates)
- 1
- Topics
- 3d, ai-local, ai-tools, desktop-app, modly, open-source, self-hosted