Deploy
cyanfish-x/tellux
Deploy tellux examples/docs sites via project scripts — one local command (pnpm run deploy) rclone-syncs to the self-hosted site then Wrangler Direct Uploads to Cloudflare Pages.
Guides building browser apps with the @manycore/aholo-viewer npm package to render 3D Gaussian Splatting and mesh content from TypeScript.
$ npx skills add manycoretech/aholo-viewer --skill use-aholo-viewer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install manycoretech/aholo-viewer use-aholo-viewer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/manycoretech/aholo-viewer.git skills-src && mkdir -p .claude/skills && cp -r skills-src/docs/ai/skills/use-aholo-viewer .claude/skills/use-aholo-viewer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "use-aholo-viewer" agent skill from https://github.com/manycoretech/aholo-viewer/tree/master/docs/ai/skills/use-aholo-viewer into .claude/skills/use-aholo-viewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "use-aholo-viewer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/manycoretech/aholo-viewer/tree/master/docs/ai/skills/use-aholo-viewerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add manycoretech/aholo-viewer --skill use-aholo-viewer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install manycoretech/aholo-viewer use-aholo-viewer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/manycoretech/aholo-viewer.git skills-src && mkdir -p .agents/skills && cp -r skills-src/docs/ai/skills/use-aholo-viewer .agents/skills/use-aholo-viewer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "use-aholo-viewer" agent skill from https://github.com/manycoretech/aholo-viewer/tree/master/docs/ai/skills/use-aholo-viewer into .agents/skills/use-aholo-viewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "use-aholo-viewer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add manycoretech/aholo-viewer --skill use-aholo-viewer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install manycoretech/aholo-viewer use-aholo-viewer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/manycoretech/aholo-viewer.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/docs/ai/skills/use-aholo-viewer .cursor/skills/use-aholo-viewer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "use-aholo-viewer" agent skill from https://github.com/manycoretech/aholo-viewer/tree/master/docs/ai/skills/use-aholo-viewer into .cursor/skills/use-aholo-viewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "use-aholo-viewer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/manycoretech/aholo-viewer.git --path docs/ai/skills/use-aholo-viewer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add manycoretech/aholo-viewer --skill use-aholo-viewer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install manycoretech/aholo-viewer use-aholo-viewer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/manycoretech/aholo-viewer.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/docs/ai/skills/use-aholo-viewer .gemini/skills/use-aholo-viewer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "use-aholo-viewer" agent skill from https://github.com/manycoretech/aholo-viewer/tree/master/docs/ai/skills/use-aholo-viewer into .gemini/skills/use-aholo-viewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "use-aholo-viewer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install manycoretech/aholo-viewer use-aholo-viewerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add manycoretech/aholo-viewer --skill use-aholo-viewer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/manycoretech/aholo-viewer.git skills-src && mkdir -p .github/skills && cp -r skills-src/docs/ai/skills/use-aholo-viewer .github/skills/use-aholo-viewer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "use-aholo-viewer" agent skill from https://github.com/manycoretech/aholo-viewer/tree/master/docs/ai/skills/use-aholo-viewer into .github/skills/use-aholo-viewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "use-aholo-viewer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add manycoretech/aholo-viewer --skill use-aholo-viewer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install manycoretech/aholo-viewer use-aholo-viewer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/manycoretech/aholo-viewer.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/docs/ai/skills/use-aholo-viewer .opencode/skills/use-aholo-viewer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "use-aholo-viewer" agent skill from https://github.com/manycoretech/aholo-viewer/tree/master/docs/ai/skills/use-aholo-viewer into .opencode/skills/use-aholo-viewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "use-aholo-viewer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
use-aholo-viewerGuides building browser apps with the @manycore/aholo-viewer npm package to render 3D Gaussian Splatting and mesh content from TypeScript.
This skill guides an agent writing browser applications that use the public @manycore/aholo-viewer npm package, a renderer for 3D Gaussian Splatting and mesh content. It treats the package as a finished library rather than the repository's internal renderer, imports only public exports, and tells the agent to read the Markdown docs written for AI use and advertised at aholojs.dev (getting started, basic concepts, API index and examples) instead of scraping rendered pages.
The integration workflow installs the package with Vite and TypeScript, creates a DOM container with stable dimensions before calling createViewer, attaches event listeners to that container rather than the canvas, builds a camera with lookAt, adds objects to the viewer's scene and sets the camera, configures the pipeline with setViewerConfig, renders explicitly or through a requestRenderHandler tied to requestAnimationFrame, and releases GPU resources on cleanup. A minimal splat example and a list of public exports cover cameras, math types, scene objects, lights, geometry and materials.
7 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 068962b. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).
From the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
aholojs.devholo-cos.aholo3d.cnFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Aholo Viewer Integration loads about 2.2k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 853 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from manycoretech/aholo-viewer at commit 068962b, republished under its MIT licence (© manycoretech). 853 words, ~2,210 tokens.
.claude/skills/use-aholo-viewer/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.Use this skill to build or modify user applications that consume the public @manycore/aholo-viewer npm package. Treat it as a full-featured browser rendering package, not as this repository's internal renderer source.
Before generating non-trivial code, read the AI-oriented docs advertised by https://aholojs.dev/llms.txt:
https://aholojs.dev/llm/manual/getting-started.md for installation and the minimal Vite setup.https://aholojs.dev/llm/manual/basic-concepts.md for scenes, objects, cameras, viewports, and the render flow.https://aholojs.dev/llm/api/index.md to confirm public exports.https://aholojs.dev/llm/examples/index.md for runnable TypeScript patterns.Prefer these Markdown docs over scraping rendered HTML pages.
Install the package in a browser app:
npm install --save @manycore/aholo-viewer
npm install --save-dev vite typescriptImport only public package exports from @manycore/aholo-viewer.
Create a real DOM container with stable dimensions before calling createViewer. Attach application DOM event listeners to this container, not to the engine canvas.
Create a camera, position it, call lookAt, add objects to viewer.getScene(), then call viewer.setCamera(camera).
Configure rendering with setViewerConfig(viewer, { pipeline: ... }).
Render explicitly with viewer.render(). If the app relies on viewer-triggered invalidation, set viewer.requestRenderHandler to schedule another render with requestAnimationFrame.
Clean up when removing content: detach scene objects, stop render/update loops that still reference them, then release GPU resources or owned resources according to the cleanup rules below.
Use this pattern for a Vite/TypeScript browser entry:
import {
BackgroundMode,
Color,
PerspectiveCamera,
SplatLoader,
SplatUtils,
Vector3,
createViewer,
setViewerConfig,
} from '@manycore/aholo-viewer';
const SPLAT_URL = 'https://holo-cos.aholo3d.cn/aholo-opensource/gs_file/bear/bear.3d71a266.sog';
const container = document.createElement('div');
container.style.width = '500px';
container.style.height = '500px';
document.body.appendChild(container);
async function main() {
const viewer = createViewer('example-viewer', container, {});
const camera = new PerspectiveCamera(60, 1, 0.1, 2000);
const response = await fetch(SPLAT_URL);
const buffer = await response.arrayBuffer();
const data = await SplatLoader.parseSplatData(
SplatLoader.SplatFileType.SOG,
new Uint8Array(buffer),
SplatLoader.SplatPackType.Compressed,
);
const splat = await SplatUtils.createSplat(data);
camera.up.set(0, -1, 0);
camera.position.set(-1.5, -0.5, 0);
camera.lookAt(new Vector3(0, 0, 0));
viewer.getScene().add(splat);
viewer.setCamera(camera);
setViewerConfig(viewer, {
pipeline: {
Background: {
background: {
active: BackgroundMode.BasicBackground,
basic: { color: new Color(0, 0, 0) },
},
ground: { enabled: false },
},
Splatting: { enabled: true },
TAA: { enabled: false },
},
});
const render = () => viewer.render();
viewer.requestRenderHandler = () => requestAnimationFrame(render);
requestAnimationFrame(render);
}
main();createViewer, setViewerConfig, Viewer, Viewport.PerspectiveCamera, OrthographicCamera, Vector2, Vector3, Vector4, Color, Matrix4, Quaternion.Object3D, Scene3D, Mesh, Splat, AmbientLight, DirectionalLight, PointLight, SpotLight.BufferGeometry, BufferAttribute, MeshBasicMaterial, MeshPhongMaterial, Side, downloadTexture.SplatLoader, SplatUtils, CompressedSplat, SuperCompressedSplat, SogSplat.GLTFLoader, DracoLoader, Animation, Events.Confirm exact symbols in /llm/api/index.md when using less common APIs.
For 3DGS content:
SplatLoader.parseSplatData(...) to parse supported splat formats.SplatUtils.createSplat(data) to create a renderable splat.pipeline.Splatting.camera.up.set(0, -1, 0).For mesh content:
BufferGeometry, BufferAttribute, and optional indices.MeshPhongMaterial with lights for shaded meshes, or MeshBasicMaterial for unlit objects.AmbientLight, DirectionalLight, or PointLight before rendering lit materials.For interactive apps:
viewer.render().Treat the container as the stable application boundary:
container passed to createViewer(...), or on another element owned by the application.Use the lightest cleanup method that matches ownership and lifecycle:
freeGPU() when the goal is to release GPU memory while keeping the object instance logically reusable. The object may upload GPU resources again if it is rendered or updated later.freeAllGpuResourceOwned() when the object owns related GPU resources that should also be released. For example, geometry.freeAllGpuResourceOwned() releases the geometry GPU resource plus its attribute and index GPU resources; drawable.freeAllGpuResourceOwned() releases its materials, geometry, and drawable GPU resources.destroy() only when the object is permanently retired. Before calling destroy(), ensure the object is removed from the scene, no frame callback, async load, event listener, control, viewport, material, geometry, or app state will use it again, and it is not currently participating in a render/update pass.freeGPU() or freeAllGpuResourceOwned() for memory-pressure cleanup. Prefer destroy() for final teardown after references are severed.Splat directly. Use loader and utility APIs.destroy() on resources that shared objects, cached data, render callbacks, or pending async work may still reference.destroy() as the default GPU-memory cleanup method. Use freeGPU() for the object's own GPU state, or freeAllGpuResourceOwned() when owned child resources should also release GPU state.© manycoretech, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 2 other files in docs/ai/skills/use-aholo-viewer of manycoretech/aholo-viewer.
Open the folder on GitHubat commit 068962b
Aholo Viewer Integration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Aholo Viewer Integration this skillmanycoretech/aholo-viewer | 1.1k | — | ~2.2k | Automated safety check: Pass | MIT | |
| Deploycyanfish-x/tellux | 207 | — | ~1.1k | Automated safety check: Notes | MIT | |
| Threejs Gameplay Systemsvalkor-ai/loom | 1.2k | 1 repos | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Vuetify Skilldlogue/vite-vuetify-ts-starter | 181 | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Uni-app-x Components and APIsfeige996/unibest | 2.3k | — | ~788 | Automated safety check: Pass | MIT | |
| Threejs Gameplay Systemscorosolto/client | 257 | — | ~1.5k | Automated safety check: Pass | AGPL-3.0 |
cyanfish-x/tellux
Deploy tellux examples/docs sites via project scripts — one local command (pnpm run deploy) rclone-syncs to the self-hosted site then Wrangler Direct Uploads to Cloudflare Pages.
valkor-ai/loom
Build and iterate playable Three.js game systems: starter scaffold, architecture, design briefs, core loops, level and encounter design, entities, input, camera, collision and physics, scoring…
logue/vite-vuetify-ts-starter
Vue Material Component Framework. An agent skill from logue/vite-vuetify-ts-starter.
feige996/unibest
Reference for using uni-app-x's built-in components and APIs, with one example file per item, official doc links and platform compatibility notes.
corosolto/client
Build and iterate playable Three.js game systems. An agent skill from corosolto/client.
pmndrs/viverse
A skill your agent uses when an AI agent needs to inspect, verify, debug, or profile a live Vite app by running temporary snippets inside the browser page and reading browser logs or captured…
manycoretech/aholo-viewer
Owns the paired JSON metadata and TypeScript runner files that define the Aholo Viewer's example and Playground content.
manycoretech/aholo-viewer
Owns the Aholo Viewer Astro website shell and Playground integration, covering routes, layouts, i18n copy and scoped CSS, while leaving the renderer and example content to other skills.
manycoretech/aholo-viewer
Guides writing and maintaining Aholo Viewer documentation: README, AGENTS.md, architecture notes, bilingual manual pages and AI collaboration guides.
manycoretech/aholo-viewer
Coordinate Aholo Viewer monorepo work. Use for cross-module tasks, workspace scripts, generated docs/build flow, validation routing, cleanup boundaries, or…
manycoretech/aholo-viewer
Guides visual design and polish for the Aholo Viewer website and Playground, staying inside the existing Astro site and scoped CSS layers with a restrained technical tone.
manycoretech/aholo-viewer
Work on the @manycore/aholo-viewer package. Use only when the user explicitly asks for renderer source, package build, public exports, JSDoc/API docs…
Works with
Categories
Guides building browser apps with the @manycore/aholo-viewer npm package to render 3D Gaussian Splatting and mesh content from TypeScript. This skill guides an agent writing browser applications that use the public @manycore/aholo-viewer npm package, a renderer for 3D Gaussian Splatting and mesh content.dev (getting started, basic concepts, API index and examples) instead of scraping rendered pages.
Aholo Viewer Integration fits situations like: installing and bootstrapping @manycore/aholo-viewer in a Vite app; rendering a Gaussian splat scene in the browser; setting up cameras, lights and the render loop for the viewer; cleaning up scene objects and GPU resources when content is removed.
Run `npx skills add manycoretech/aholo-viewer --skill use-aholo-viewer -a claude-code`. Or copy the skill folder (docs/ai/skills/use-aholo-viewer in manycoretech/aholo-viewer) into .claude/skills/use-aholo-viewer in your project. Claude Code loads it when a task matches its description.
Run `npx skills add manycoretech/aholo-viewer --skill use-aholo-viewer -a codex`. Or copy the skill folder (docs/ai/skills/use-aholo-viewer in manycoretech/aholo-viewer) into .agents/skills/use-aholo-viewer in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add manycoretech/aholo-viewer --skill use-aholo-viewer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/use-aholo-viewer, .gemini/skills/use-aholo-viewer, .github/skills/use-aholo-viewer and .opencode/skills/use-aholo-viewer in your project.
SKILL.md names no scripts, command-line tools or credentials: Aholo Viewer Integration is instructions for the agent only. Our summary lists: A browser app, for example Vite with TypeScript; Network access to the aholojs.dev docs.
SKILL.md names 2 domains. In commands or code: aholojs.dev and holo-cos.aholo3d.cn; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Aholo Viewer Integration is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.2k tokens (SKILL.md is roughly 8.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Aholo Viewer Integration: Deploy (cyanfish-x/tellux, 207 stars), Threejs Gameplay Systems (valkor-ai/loom, 1.2k stars), Vuetify Skilld (logue/vite-vuetify-ts-starter, 181 stars) and Uni-app-x Components and APIs (feige996/unibest, 2.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
manycoretech (a GitHub organization) maintains it in manycoretech/aholo-viewer, which has 1,085 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 8, 2026.
Source: manycoretech/aholo-viewer on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.