원클릭으로 Manus에서 모든 스킬 실행

시작하기

fleet-status

스타1

포크0

업데이트2026년 4월 4일 21:48

Inspect OpenFleet agent health, tasks, jobs, and live session activity.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

twaldin

twaldin/openfleet

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Fleet Status

Use this skill when checking whether the OpenFleet control plane and agents are healthy.

Start with the top-level dashboard: node bin/openfleet status.
Check lifecycle health for session-level problems: node bin/openfleet lifecycle status.
Use node bin/ops summary for a concise fleet snapshot.
Use node bin/ops agents to list registered agents and metadata.
Inspect task backlog with node bin/ops tasks --json.
Inspect job state with node bin/ops jobs --json when work appears stuck.
Drill into one agent with node bin/ops inspect <agent>.
For live message flow, use node bin/ops tail <agent> or node bin/ops follow <agent>.
If messaging seems broken, verify sends with node bin/send <agent> "<message>" and confirm the event lands.

Useful state locations from this repo:

~/.openfleet/agents.json
~/.openfleet/registry.json
~/.openfleet/tasks.json
~/.openfleet/jobs.json
~/.openfleet/events.jsonl

Good diagnosis flow:

Confirm the fleet is up.
Identify which agent or task is unhealthy.
Check recent session output.
Check queued tasks and jobs.
Check the event log if state and UI disagree.

Report which agents are healthy, which are stale or broken, and the next operator action needed.

이 저장소의 다른 Skills

같은 저장소

api-client

twaldin/openfleet

Make HTTP requests carefully, inspect responses, and interact with APIs safely.

2026-04-041

code-review

twaldin/openfleet

Review diffs for bugs, security issues, regressions, and missing tests.

2026-04-041

docker-manager

twaldin/openfleet

Build, run, inspect, and clean up Docker images and containers safely.

2026-04-041

file-organizer

twaldin/openfleet

Reorganize files safely, update references, and leave the project easier to navigate.

2026-04-041

git-commit

twaldin/openfleet

Stage intended changes, write accurate commit messages, and push safely.

2026-04-041

market-scan

twaldin/openfleet

Review prediction markets, positions, catalysts, and mark-to-market P&L.

2026-04-041

name	fleet-status
description	Inspect OpenFleet agent health, tasks, jobs, and live session activity.

Fleet Status

Use this skill when checking whether the OpenFleet control plane and agents are healthy.

Start with the top-level dashboard: node bin/openfleet status.
Check lifecycle health for session-level problems: node bin/openfleet lifecycle status.
Use node bin/ops summary for a concise fleet snapshot.
Use node bin/ops agents to list registered agents and metadata.
Inspect task backlog with node bin/ops tasks --json.
Inspect job state with node bin/ops jobs --json when work appears stuck.
Drill into one agent with node bin/ops inspect <agent>.
For live message flow, use node bin/ops tail <agent> or node bin/ops follow <agent>.
If messaging seems broken, verify sends with node bin/send <agent> "<message>" and confirm the event lands.

Useful state locations from this repo:

~/.openfleet/agents.json
~/.openfleet/registry.json
~/.openfleet/tasks.json
~/.openfleet/jobs.json
~/.openfleet/events.jsonl

Good diagnosis flow:

Confirm the fleet is up.
Identify which agent or task is unhealthy.
Check recent session output.
Check queued tasks and jobs.
Check the event log if state and UI disagree.

Report which agents are healthy, which are stale or broken, and the next operator action needed.