Individual skill

explorer-pipeline

Use when asked to make an interactive 3D explorer of a topic from start to finish, go from a topic to a clickable 3D learning page, or run the whole 3D explorer process. Produces a staged run of explorer-interface-brief, model-prompt-pack and explorer-viewer-builder in order for one topic, with the hand-offs between them, and a build checklist that tracks every asset, source and test until the explorer ships.

plugins/pm-3d-explorer/skills/explorer-pipeline/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,540
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Explorer Pipeline

Topic in, interactive 3D explorer out. The three skills in this bundle each do one job: the interface brief decides what the learner sees and does, the model prompt pack produces the parts and their sourced labels, and the viewer builder turns both into a page. This skill runs them in order for one topic, carries each step's output into the next, and keeps a build checklist so nothing ships unsourced or untested.

## Required Inputs

Ask for these once, at the start, and reuse them in every stage:
- **Topic** and the object or system to explore
- **Audience and learning goal**
- **Devices** the explorer must work on
- **Trusted sources** the user has, or the curriculum or standard to follow
- **The image-to-3D tool** the user will use, or "not chosen yet"
- **Hosting** for the finished page
Back to top