Run any Skill in Manus with one click

dev-launch-file-browser

Stars18

Forks3

UpdatedJuly 11, 2026 at 10:37

Manual invocation only; use only when the user explicitly requests `dev-launch-file-browser` by exact name or asks to launch, start, stop, verify, or reset the in-repo Filestash file browser under `dockers/dev-helpers/filestash/` so they can browse repository files and generated artifacts through the local web UI.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

igamenovoer

igamenovoer/houmao

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Network and Computer Systems AdministratorsComputer and Mathematical Occupations·SOC 15-1244

File Explorer

2 files

SKILL.md

readonly

name	dev-launch-file-browser
description	Manual invocation only; use only when the user explicitly requests `dev-launch-file-browser` by exact name or asks to launch, start, stop, verify, or reset the in-repo Filestash file browser under `dockers/dev-helpers/filestash/` so they can browse repository files and generated artifacts through the local web UI.

Dev Launch File Browser

Use the repo-owned Filestash helper for repository file browsing. Do not replace it with ad hoc docker run commands or a separate compose stack.

Workflow

Check the repo-owned helper files when you need current settings.

Read dockers/dev-helpers/filestash/.env for the current port, connection label, and password.
Read dockers/dev-helpers/filestash/README.md only when you need the documented prerequisites or reset procedure.

Use the repo-owned wrapper scripts.

Start or ensure the helper is running with ./dockers/dev-helpers/filestash/up.sh.
Verify the running helper with ./dockers/dev-helpers/filestash/verify.sh when the user asks for confirmation or the startup output looks suspicious.
Stop the helper with ./dockers/dev-helpers/filestash/down.sh.
Reset the helper by stopping it, removing dockers/dev-helpers/filestash/.data, then starting it again.

Report access details from .env, not from stale memory.

URL: http://127.0.0.1:${FILESTASH_HTTP_PORT}/login
Connection label: FILESTASH_CONNECTION_LABEL
Password: FILESTASH_DEFAULT_PASSWORD

Surface prerequisite failures directly.

If the image is missing, tell the user the helper expects machines/filestash:latest to already exist locally.
If up.sh fails because node or jq is missing, report that clearly and stop.
If the container starts but verification fails, report the failing step and prefer verify.sh output over guessing.

Guardrails

Do not edit the helper stack just to launch it unless the user explicitly asks for changes.
Do not invent alternate ports, passwords, or image names. Read the current values from .env and the compose file.
Do not claim the browser is ready unless up.sh succeeds. Use verify.sh when the user asks for confidence or when the state is unclear.

More from this repository

same repository

houmao-dev-behavior-testing

igamenovoer/houmao

Use when a Houmao maintainer explicitly needs to qualify whether packaged system skills activate, remain inactive, select the correct actor route, preserve identity and target posture, or enforce their contracts in real admin or managed-agent contexts.

2026-07-2518

houmao-shared-routines

igamenovoer/houmao

Use when an advanced Houmao user explicitly wants direct access to an ordinary system routine, or when an admin or managed-agent entrypoint delegates project, credential, definition, mailbox, memory, messaging, gateway, workspace, inspection, lifecycle, graphing, or AG-UI work.

2026-07-2518

swe-critic-review

igamenovoer/houmao

Use when swe-critic performs its assigned codebase and design review and reports evidence-backed design-quality findings.

2026-07-2518

houmao-dev-install

igamenovoer/houmao

Use when a Houmao maintainer explicitly invokes this development skill to install or refresh the current checkout as an editable user-space uv tool with a commit-stamped local version, or to update packaged Houmao system skills and development-skill links in project-local Claude, Codex, Kimi Code, Copilot, or universal agent homes.

2026-07-2418

houmao-admin-entrypoint

igamenovoer/houmao

Use when any semantically Houmao-related request reaches an assistant acting for a human operator, including information, command or route learning, incomplete tasks, state inspection, operations, and explicit loop work. Do not trigger for an incidental Houmao token in otherwise unrelated material; explicit $houmao-* handles take precedence.

2026-07-2418

houmao-admin-welcome

igamenovoer/houmao

Use when a human operator explicitly invokes $houmao-admin-welcome for first-use orientation, route comparison, reorientation, command learning, or a guided tour; never select it implicitly.

2026-07-2418

name	dev-launch-file-browser
description	Manual invocation only; use only when the user explicitly requests `dev-launch-file-browser` by exact name or asks to launch, start, stop, verify, or reset the in-repo Filestash file browser under `dockers/dev-helpers/filestash/` so they can browse repository files and generated artifacts through the local web UI.

Dev Launch File Browser

Use the repo-owned Filestash helper for repository file browsing. Do not replace it with ad hoc docker run commands or a separate compose stack.

Workflow

Check the repo-owned helper files when you need current settings.

Read dockers/dev-helpers/filestash/.env for the current port, connection label, and password.
Read dockers/dev-helpers/filestash/README.md only when you need the documented prerequisites or reset procedure.

Use the repo-owned wrapper scripts.

Start or ensure the helper is running with ./dockers/dev-helpers/filestash/up.sh.
Verify the running helper with ./dockers/dev-helpers/filestash/verify.sh when the user asks for confirmation or the startup output looks suspicious.
Stop the helper with ./dockers/dev-helpers/filestash/down.sh.
Reset the helper by stopping it, removing dockers/dev-helpers/filestash/.data, then starting it again.

Report access details from .env, not from stale memory.

URL: http://127.0.0.1:${FILESTASH_HTTP_PORT}/login
Connection label: FILESTASH_CONNECTION_LABEL
Password: FILESTASH_DEFAULT_PASSWORD

Surface prerequisite failures directly.

If the image is missing, tell the user the helper expects machines/filestash:latest to already exist locally.
If up.sh fails because node or jq is missing, report that clearly and stop.
If the container starts but verification fails, report the failing step and prefer verify.sh output over guessing.

Guardrails

Do not edit the helper stack just to launch it unless the user explicitly asks for changes.
Do not invent alternate ports, passwords, or image names. Read the current values from .env and the compose file.
Do not claim the browser is ready unless up.sh succeeds. Use verify.sh when the user asks for confidence or when the state is unclear.