本文へ移動
cccskills
無料GitHub で公開

luminarium

Print the localhost URL for The Luminarium — moflo's daemon dashboard — for the current project. Use when the user asks for "the luminarium link", "the moflo dashboard", "the daemon UI", or anything synonymous. Each project gets a deterministic port in 33000–33999; the actual bound port is recorded in `.moflo/daemon.lock`.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md3.0 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

/luminarium — Project Dashboard Link

Surface the URL for The Luminarium (the moflo daemon's localhost UI) for the project that this session is running in. No prompts, no confirmations — print the link and stop.

Procedure

  1. Find the project root. Walk up from process.cwd() looking for a .moflo/ directory. The session's cwd is almost always the project root, so check there first.

  2. Read .moflo/daemon.lock. It's a JSON file written by the daemon at bind time. The dashboard port is the port field:

    { "pid": 12345, "port": 33421, "startedAt": "...", ... }
    
    • If the file exists and port is a valid number → the daemon is running and bound. Use that port.
    • If the file is missing or port is absent/invalid → the daemon is not running. See step 4.
  3. Print the link in a single line, with the path verbatim — Claude Code renders it as clickable:

    The Luminarium: http://localhost:<port>
    

    Nothing else. No banner, no follow-up question, no "what would you like to do?".

  4. If the daemon isn't running (no lock file, or unparseable), say so in one line and offer the start command — don't run it:

    The moflo daemon isn't running for this project. Start it with: npx flo daemon start
    

Why read the lock, not compute the port

The port is project-deterministic (sha256(projectRoot) mapped into 33000–33999), but if the deterministic port was already taken at bind time the daemon scans forward and binds an alternate. The lock file is the only source of truth for what's actually bound. Do not compute the hash yourself — read the file.

Don't

  • Don't fall back to any hardcoded port — there is no project-agnostic dashboard port; a literal would route to a foreign daemon on a multi-project machine. If the lock is missing, report "not running".
  • Don't compute the deterministic port and report it as the link when the lock is missing — the daemon may be down, or bound to an alternate port. Report "not running" instead.
  • Don't run flo daemon start automatically — the user asked for a link, not for daemon management. Leave starting to /healer or the user.
  • Don't open a browser. Print the URL; let the user click.

Output

A single line. Examples:

The Luminarium: http://localhost:33421
The moflo daemon isn't running for this project. Start it with: npx flo daemon start

See Also

  • /healer — diagnoses and (with --fix) starts the daemon if it's not running.
  • src/cli/services/daemon-port.ts (and its JS twin bin/lib/daemon-port.mjs) — canonical port-resolution helpers; resolveClientPort() is what the rest of moflo uses.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

commune

無料

Turn a vague idea into a concrete, actionable spec through a short Socratic dialogue, then hand the result off to an existing moflo surface — a /flo ticket, a spell, or memory. Use BEFORE you have a defined unit of work, when the goal is still fuzzy.

日本語の概要は準備中です。原文の説明を表示しています。

eric-cielo/moflo182026年10月1日 更新

Scaffold new spell step commands and connectors. Use when building new step commands for spells or extending the spell engine with new capabilities. Connectors are for new I/O transport types OR platforms requiring complex multi-step interaction (e.g., browser-based automation).

日本語の概要は準備中です。原文の説明を表示しています。

eric-cielo/moflo182026年10月1日 更新

distill

無料

Alias for /flo-simplify — see that skill's description.

日本語の概要は準備中です。原文の説明を表示しています。

eric-cielo/moflo182026年10月1日 更新

divine

無料

Structured multi-hop web research with explicit confidence gating — plan the inquiry, search (WebSearch/WebFetch), score your own confidence, and keep digging until the answer is well-supported or a hop cap is hit, then emit a cited synthesis. Learns across sessions by storing each research case to memory and reusing prior strategies. Use when a question needs more than one search — comparisons, current-best-practice questions, anything where a single lookup leaves you unsure.

日本語の概要は準備中です。原文の説明を表示しています。

eric-cielo/moflo182026年10月1日 更新

eldar

無料

Consult the Eldar — audit a project's moflo + Claude Code setup for portable, high-leverage gaps and guide remediation. Default mode is read-only audit with severity-ranked findings; --fix presents an interactive triage menu and walks the user through each chosen fix (healer, missing CLAUDE.md, sparse guidance, hook/MCP wiring, empty memory namespaces, stack→guidance gaps). Use when starting in a new project, when Claude feels lost or inefficient, when guidance/CLAUDE.md is sparse, or as a periodic health check.

日本語の概要は準備中です。原文の説明を表示しています。

eric-cielo/moflo182026年10月1日 更新

flfl

無料

Run /fl on a ticket with moflo's three standing considerations loaded first — cross-platform (Rule

日本語の概要は準備中です。原文の説明を表示しています。

eric-cielo/moflo182026年10月1日 更新

eric-cielo のスキルをすべて見る

このスキルの問題を報告する