New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Openhome3d Start

by yuyou-dev in yuyou-dev/OpenHome3D

Open the OpenHome3D Community Hub or install, update, uninstall, verify, start, and introduce OpenHome3D and its Companion.

MITAuto-check passed

Install Openhome3d Start

skills CLI
$ npx skills add yuyou-dev/OpenHome3D --skill openhome3d-start -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install yuyou-dev/OpenHome3D openhome3d-start --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/yuyou-dev/OpenHome3D.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/openhome3d-companion/skills/openhome3d-start .claude/skills/openhome3d-start && rm -rf skills-src

Use ~/.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/

Facts

Skill name
openhome3d-start
GitHub stars
164
Token cost
~921 tokens
SKILL.md length
484 words
Files
3 (incl. references)
Skills in repo
3
Repo updated
First seen
Licence
MIT

At a glance

Open the OpenHome3D Community Hub or install, update, uninstall, verify, start, and introduce OpenHome3D and its Companion.

  • Works in 6 steps: If the current workspace is OpenHome3D,… → Before pulling an existing clone,… → Check Node.js, npm, Codex CLI, and Codex… → …
  • The user asks for the OpenHome3D community center/hub
  • SKILL.md covers Outcome, Workflow, Community hub and Lifecycle requests, plus 1 more section
  • Calls npm and git

What it does

Openhome3d Start is an agent skill from yuyou-dev/OpenHome3D. Open the OpenHome3D Community Hub or install, update, uninstall, verify, start, and introduce OpenHome3D and its Companion. Use whenever the user asks for the OpenHome3D community center/hub, Companion UI, or to try, open, run, set up, upgrade, remove, or learn the project. Use for local application and plugin lifecycle work plus the visual community entry, not for publishing GitHub contributions.

Its SKILL.md is about 920 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/installation.md`).

It works with GitHub and npm. The repository describes itself as: A cartoon-style 3D home designer that runs entirely in your browser — seeded procedural layouts, cel-shaded toon rendering, Neo-Brutalism UI, 337 CC0 furniture models. No… The licence is MIT.

When your agent uses it

  • The user asks for the OpenHome3D community center/hub
  • Learn the project
  • Local application and plugin lifecycle work plus the visual community entry
  • Not for publishing GitHub contributions

Example prompts

  • “/openhome3d-start”

Requirements

  • Node.js

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. If the current workspace is OpenHome3D, use it. Otherwise look for an existing nearby OpenHome3D clone before creating one. Never…
  2. Before pulling an existing clone, inspect git status --short. Preserve user changes; use git pull --ff-only only when it is safe.
  3. Check Node.js, npm, Codex CLI, and Codex login. Do not read credential files. Ask before installing system-level software.
  4. Run npm install, npm run doctor, and npm run build. A failed Codex login blocks only optional AI features; the browser-only designer can…
  5. Start npm run dev in a persistent terminal/session. Read the actual printed URL rather than assuming a port.
  6. Verify the page returns HTTP 200. Open it in the in-app browser if available.

What it can do on your machine

Read from SKILL.md and the folder at commit cb52afc. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    Shell commands in SKILL.md call:

    • npm
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm and git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Openhome3d Start loads about 921 tokens when it runs, and up to ~1.3k if it reads all its reference files. Until then it costs about 104 tokens; SKILL.md has 484 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~104
When it runs · the whole SKILL.md, loaded when a task matches
~921
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.3k

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from yuyou-dev/OpenHome3D at commit cb52afc, republished under its MIT licence (© yuyou-dev). 484 words, ~921 tokens.

Download SKILL.mdSave it as .claude/skills/openhome3d-start/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
openhome3d-start
description
Open the OpenHome3D Community Hub or install, update, uninstall, verify, start, and introduce OpenHome3D and its Companion. Use whenever the user asks for the OpenHome3D community center/hub, Companion UI, or to try, open, run, set up, upgrade, remove, or learn the project. Use for local application and plugin lifecycle work plus the visual community entry, not for publishing GitHub contributions.

OpenHome3D Start

Bring the user to an observable running OpenHome3D session with the least manual setup.

Outcome

  • An existing clone is updated safely, or a new clone is created.
  • Node.js 20+ dependencies are installed and the project passes npm run doctor and npm run build.
  • The dev server remains running on its printed random loopback port.
  • Open the URL in Codex's in-app browser when that capability is available; otherwise return the clickable URL.
  • Briefly point out whole-home editing, furniture editing, floor-plan import, AI repaint, and the Companion community hub.

Workflow

  1. If the current workspace is OpenHome3D, use it. Otherwise look for an existing nearby OpenHome3D clone before creating one. Never overwrite a non-empty directory.
  2. Before pulling an existing clone, inspect git status --short. Preserve user changes; use git pull --ff-only only when it is safe.
  3. Check Node.js, npm, Codex CLI, and Codex login. Do not read credential files. Ask before installing system-level software.
  4. Run npm install, npm run doctor, and npm run build. A failed Codex login blocks only optional AI features; the browser-only designer can still run.
  5. Start npm run dev in a persistent terminal/session. Read the actual printed URL rather than assuming a port.
  6. Verify the page returns HTTP 200. Open it in the in-app browser if available.

Community hub

When the user asks to open the OpenHome3D community center, resolve and call the Companion MCP tool open_openhome3d_hub. Its ui://openhome3d/community-hub/v2.html value is an internal MCP Apps resource identifier, not a browser URL.

The tool may be deferred even when the plugin is loaded. If it is not in the initial visible tool list, use the host's tool-search mechanism to discover the exact registered name and call it. Do not switch to oss-inbox, Chrome, GitHub Discussions, or another community route merely because the tool was deferred.

Show full SKILL.md (181 more words)Show less

Only after exact-name discovery confirms the tool is absent should you explain the install boundary: completely quit and reopen the Codex desktop app, create a new task, and select OpenHome3D Companion through Sources → Use plugins. You may offer the normal HTTPS Discussions page as an explicitly labeled temporary fallback, but never send a ui:// URI to the browser and never claim the interactive hub opened unless the tool call completed.

Use installation details only when handling a missing prerequisite or installing the Companion plugin itself.

Lifecycle requests

For a request to install, upgrade, or uninstall the Companion itself, follow the plugin root LIFECYCLE.md. Keep the app and plugin scopes independent. An uninstall must preview the effect and obtain confirmation before optionally removing the openhome3d marketplace. After any plugin catalog change, explain the full Codex desktop restart and new-task activation boundary.

Boundaries

  • Never pipe remote scripts into a shell.
  • Never expose GitHub, Codex, or npm credentials.
  • Installing/running the designer does not require a GitHub account.
  • Do not publish, push, fork, or create a PR unless the user separately requests a contribution workflow.

© yuyou-dev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in plugins/openhome3d-companion/skills/openhome3d-start of yuyou-dev/OpenHome3D.

  • SKILL.md
  • agents/openai.yaml
  • references/installation.md

Open the folder on GitHubat commit cb52afc

Compare with similar skills

Openhome3d Start 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.

Openhome3d Start compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Openhome3d Start this skillyuyou-dev/OpenHome3D164—~921Automated safety check: PassMIT
Proxychains Network Fallback2025Emma/vibe-coding-cn23k1 repos~1.1kAutomated safety check: NotesMIT
Cutting A ReleaseTriliumNext/Trilium38k—~3.2kAutomated safety check: PassAGPL-3.0
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT
Update .NET Supported OS Matrixdotnet/core22k—~4.1kAutomated safety check: PassMIT
Version ReleaseNG-ZORRO/ng-zorro-antd9.2k—~3.1kAutomated safety check: PassMIT

Similar skills

  • Proxychains Network Fallback

    2025Emma/vibe-coding-cn

    Retries failed network commands through proxychains4 and a local proxy when it sees timeouts, DNS failures or blocked access.

    23k GitHub starsUsed in 1 repo~1.1k tokens
    DevOps & CloudAuto-check: notes

  • Cutting A Release

    TriliumNext/Trilium

    A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.

    38k GitHub stars~3.2k tokensUpdated today
    DevelopmentAuto-check passed

  • Verdaccio Pull Request Workflow

    verdaccio/verdaccio

    Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Update .NET Supported OS Matrix

    dotnet/core

    Official

    Audits and updates the supported-os.json files for .NET releases, checking them against upstream lifecycle data and regenerating the markdown with the release-notes tool.

    22k GitHub stars~4.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Version Release

    NG-ZORRO/ng-zorro-antd

    NG-ZORRO/ng-zorro-antd repository release workflow. An agent skill from NG-ZORRO/ng-zorro-antd.

    9.2k GitHub stars~3.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Ant Design Mobile Release

    ant-design/ant-design-mobile

    Prepares an npm release of ant-design-mobile up to the version commit, then tags and publishes the GitHub Release after you run the publish command yourself.

    12k GitHub stars~497 tokensUpdated 24 days ago
    DevelopmentAuto-check passed

More from yuyou-dev/OpenHome3D

  • Openhome3d Contribute

    yuyou-dev/OpenHome3D

    Help non-coders and developers contribute to OpenHome3D through GitHub Discussions, Issues, or Pull Requests.

    164 GitHub stars~801 tokensUpdated 1 mo ago
    Auto-check passed

  • Openhome3d Maintain

    yuyou-dev/OpenHome3D

    Triage and maintain the OpenHome3D GitHub community across Discussions, Issues, and Pull Requests.

    164 GitHub stars~540 tokensUpdated 1 mo ago
    Auto-check passed

Works with

Questions about Openhome3d Start

What does Openhome3d Start do?

Open the OpenHome3D Community Hub or install, update, uninstall, verify, start, and introduce OpenHome3D and its Companion. Openhome3d Start is an agent skill from yuyou-dev/OpenHome3D. Open the OpenHome3D Community Hub or install, update, uninstall, verify, start, and introduce OpenHome3D and its Companion.

When should I use Openhome3d Start?

Openhome3d Start fits situations like: the user asks for the OpenHome3D community center/hub; learn the project; local application and plugin lifecycle work plus the visual community entry; not for publishing GitHub contributions.

How do I install Openhome3d Start in Claude Code?

Run `npx skills add yuyou-dev/OpenHome3D --skill openhome3d-start -a claude-code`. Or copy the skill folder (plugins/openhome3d-companion/skills/openhome3d-start in yuyou-dev/OpenHome3D) into .claude/skills/openhome3d-start in your project. Claude Code loads it when a task matches its description.

How do I install Openhome3d Start in Codex?

Run `npx skills add yuyou-dev/OpenHome3D --skill openhome3d-start -a codex`. Or copy the skill folder (plugins/openhome3d-companion/skills/openhome3d-start in yuyou-dev/OpenHome3D) into .agents/skills/openhome3d-start in your project. Codex loads it when a task matches its description.

Can I use Openhome3d Start in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add yuyou-dev/OpenHome3D --skill openhome3d-start -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/openhome3d-start, .gemini/skills/openhome3d-start, .github/skills/openhome3d-start and .opencode/skills/openhome3d-start in your project.

What does Openhome3d Start need to run?

Going by SKILL.md and its folder, Openhome3d Start needs the command-line tools its instructions call (npm and git). Our summary lists: Node.js.

Does Openhome3d Start access the network?

SKILL.md contains no URLs. Its commands use npm and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Openhome3d Start safe to install?

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.

What licence does Openhome3d Start use?

Openhome3d Start is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Openhome3d Start use?

About 921 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 403 tokens, read only when the agent opens those files.

What are the alternatives to Openhome3d Start?

Skills that share tags, products or a category with Openhome3d Start: Proxychains Network Fallback (2025Emma/vibe-coding-cn, 23k stars), Cutting A Release (TriliumNext/Trilium, 38k stars), Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars) and Update .NET Supported OS Matrix (dotnet/core, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Openhome3d Start?

yuyou-dev (a GitHub user) maintains it in yuyou-dev/OpenHome3D, which has 164 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on September 5, 2026.

Source: yuyou-dev/OpenHome3D on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.