SkillAgentSearch skills...

build-wireframe-scan-reveal

Reveal Three.js geometry with an expanding world-space scan whose wire cage leads the solid surface, then burns away. Use for wireframe scanning, radial mesh reveals, survey pulses, holographic assembly, topology intros, and 3D model entrances where a plain opacity wipe does not explain the form.

Install / Use

npx skills add MengTo/Skills --skill build-wireframe-scan-reveal

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

93/100

Category

Marketing

Supported Platforms

Universal

Tags

Our assessment of build-wireframe-scan-reveal

build-wireframe-scan-reveal scores 93/100 on our quality scale, 127th of 642 Marketing skills we index (top 20%).

Its SKILL.md is 6.2 KB long, well organised into 8 sections with 3 code examples: a thorough specification that gives an agent plenty to work with.

With 6,252 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
29/30
Structure
18/20
Description
15/15
Adoption
16/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so build-wireframe-scan-reveal is actively maintained.
  • Our last check on 2026-10-26 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-02. Automated pattern scan on 2026-10-02. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

build-wireframe-scan-reveal compared with similar skills

All 4 of these similar skills score higher than build-wireframe-scan-reveal; compare them before choosing.

SkillScoreStarsUpdatedFormat
build-wireframe-scan-reveal (this skill)by MengTo936.3k54d agoSKILL.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md
designby nextlevelbuilder100149.0k6d agoSKILL.md

Frequently asked questions

How do I install build-wireframe-scan-reveal?
Run npx skills add MengTo/Skills --skill build-wireframe-scan-reveal. The install tabs above show the steps for each supported agent.
Which AI agents does build-wireframe-scan-reveal work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is build-wireframe-scan-reveal safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is build-wireframe-scan-reveal still maintained?
The repository was last updated about 2 months ago, so build-wireframe-scan-reveal is actively maintained.

name: build-wireframe-scan-reveal description: Reveal Three.js geometry with an expanding world-space scan whose wire cage leads the solid surface, then burns away. Use for wireframe scanning, radial mesh reveals, survey pulses, holographic assembly, topology intros, and 3D model entrances where a plain opacity wipe does not explain the form.

Build a Wireframe Scan Reveal

Make one world-space wavefront conduct both representations: draw topology at the front, hold the solid behind it, then remove the temporary cage. Reach for technical-wireframe-info-layout when wireframe is the page's permanent visual language; reach for animation-on-scroll when the conductor is DOM scroll rather than a 3D wave.

Extracted from inner-green-3d.html, where a survey pulse had to grow a procedural moss root through cards and type without reading as a circular mask.

Pair two representations

Create the solid mesh and a temporary LineSegments cage from the same source geometry. Share uScanOrigin, uScanRadius, and time between their materials. Keep both in world space; local-space distance changes when a group is scaled or nested and tears the two fronts apart.

Discard the solid beyond the front, with a lag that leaves the cage visible first:

uniform vec3 uScanOrigin;
uniform float uScanRadius;
uniform float uScanEnabled;

bool unscanned(vec3 worldPosition, float lag) {
  if (uScanEnabled < 0.5) return false;
  float wobble =
      sin(worldPosition.y * 0.011 + worldPosition.x * 0.007) * 36.0
    + sin(worldPosition.z * 0.021 + worldPosition.y * 0.013) * 17.0;
  return distance(worldPosition, uScanOrigin)
       > uScanRadius - lag + wobble;
}

// In the solid fragment shader:
if (unscanned(vWorldPosition, 520.0)) discard;

Use one origin outside the silhouette, usually low and left. A centered origin reads as a loading ring. Keep the two long sine terms; a perfectly circular front reads as a clip-path, while high-frequency noise makes the edge sparkle.

Make the cage ride the front

Measure each line fragment against the same radius:

float distanceFromOrigin = distance(vWorldPosition, uScanOrigin);
float rim = exp(-pow((distanceFromOrigin - uScanRadius) / 135.0, 2.0));
float trail = smoothstep(uScanRadius, uScanRadius - 950.0, distanceFromOrigin);
float alpha = (rim * 1.60 + trail * 0.34) * uWireOpacity;

Use additive blending, transparent: true, depthWrite: false, and a pale version of the scene accent. Keep depth testing on unless the cage must read through the object. Turning depth test off exposes the back half of dense topology and produces a bright unreadable ball.

Animate one conductor

Use the landed timing as a starting point:

| parameter | default | failure prevented | | --- | ---: | --- | | duration | 3.4 s | a fast reveal reads as a flash | | radius easing | 1 - (1 - t)^1.35 | linear travel stalls visually near the far corner | | solid lag | 520 world units | zero lag makes wire and fill arrive as one wipe | | rim width | 135 units | a narrow rim aliases; a wide rim becomes fog | | wire trail | 950 units | no trail hides topology before it can be read | | wire fade | smoothstep(.72, 1, t) | persistent cage competes with the finished surface | | radius reach | scene diagonal × 1.3 + 900 | the far corner remains clipped after completion |

Snap the cage on over the first 6% of the timeline, then fade it during the final 28%:

const e = Math.min(1, elapsed / 3.4);
scanRadius.value = easeOutPow(e) * maxRadius;
wireOpacity.value = Math.min(1, e / 0.06) * (1 - smoothstep(0.72, 1, e));

At completion, disable the discard branch, remove the cage, and dispose its geometry and material. Hiding it with opacity leaves duplicate geometry and shader work alive for the rest of the page.

Stage and size the scan

Resolve maxRadius after layout and after parent matrices update. Use a ResizeObserver, guard zero-sized roots, update the camera projection, then recompute the origin and farthest reach. A one-time measurement before fonts or layout settle leaves the last corner unrevealed.

Keep the demo's scene recognisable: grey-green field, bottom light pool, white editorial type, pale cards, and the root-shaped form. The staging belongs in the demo; the reusable skill is only the paired representations and shared conductor.

Respect motion and lifecycle

  • Under prefers-reduced-motion: reduce, render a designed diagnostic still at about 62% radius with both cage and solid visible. Let the replay control recompose that still and announce the state; do not hide the scene.
  • Clamp dt to 1/30 s. Reset the time base after a hidden tab or offscreen section resumes.
  • Pause on document.hidden and when an IntersectionObserver says the section is offscreen.
  • Cap device pixel ratio at 2.
  • Expose replay as a real button with visible focus and an aria-live status. Keep the canvas aria-hidden when it is decorative.
  • On teardown, cancel the frame, disconnect observers, remove listeners, and dispose geometry, materials, textures, and the renderer.

State the cost honestly

The temporary second representation and its line coverage are the real cost. Topology density and overdraw matter more than the radius math. Build the wire cage only for the entrance, use the coarsest edge graph that preserves the silhouette, and dispose it as soon as the scan finishes. Do not claim a performance gain without profiling GPU frame time before and during the cage pass.

Verify

  • Compare the opening, midpoint, and completed states with the source at 1440×900.
  • Confirm the cage leads the solid everywhere, including scaled child groups.
  • Fast-forward across completion and verify no clipped islands remain.
  • Replay twice and confirm only one frame loop and one cage survive.
  • Resize during the scan at 390×844 and 1440×900.
  • Tab to replay and confirm visible focus and a live status update.
  • Test ?reduced=1 or system reduced motion: composed still, no advancing radius.
  • Hide/show the tab and leave/re-enter the viewport; confirm no time jump.
  • Confirm a clean console and disposed cage resources after completion.

Use demo/index.html as the working proof and demo/PROMPT.md to recreate or remix it.

Related Skills

View on GitHub
GitHub Stars6.3k
CategoryMarketing
Updated1mo ago
Forks741

Languages

HTML

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions