skills.rest
LIMITLESS-LONGEVITY
LIMITLESS-LONGEVITYOFFICIAL
Explore all skills by this author →
WebsiteGitHub

status

Generate a read-only status report of the current agent environment.

Updated Apr 2, 2026
Search Tags:#mcp#workspace#diagnostics#status#container#health-check
One-click install
npx skills add https://github.com/LIMITLESS-LONGEVITY/limitless --skill status-limitless-longevity
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: status
Source: https://github.com/LIMITLESS-LONGEVITY/limitless/tree/main/apps/nanoclaw/container/skills/status
Command: npx skills add https://github.com/LIMITLESS-LONGEVITY/limitless --skill status-limitless-longevity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a concise, read-only health check of the current agent environment so users can quickly verify session context, workspace mounts, tool availability, container utilities, and scheduled tasks without performing invasive diagnostics.

Core Features & Use Cases

  • Main-channel enforcement: Detects whether the command is being run in the main chat where /workspace/project is mounted and halts if not.
  • Workspace & mount visibility: Lists workspace root, group folder contents, extra mounts, and IPC visibility to confirm accessible files and mounts.
  • Tool and container checks: Reports availability of core tools and container utilities such as agent-browser, Node, and Claude CLI.
  • Task snapshot via MCP: Calls the mcp__nanoclaw__list_tasks endpoint to enumerate scheduled tasks and report whether any tasks are present.
  • Use Case: Use this to quickly validate an execution environment before running development, orchestration, or long-running tasks.

Quick Start

Run /status in your main chat to get a concise environment health summary including mounts, tool availability, container versions, and scheduled tasks.

Frequently Asked Questions about status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check workspace mounts and container health in an agent environment?▼

To check workspace mounts and container health, you can run a read-only status report that verifies your session context, accessible group folders, IPC visibility, and available container utilities without performing invasive diagnostics.

What is a read-only system health snapshot for agent sessions?▼

A read-only system health snapshot is a concise diagnostic report that lists workspace roots, extra mounts, tool availability, and scheduled MCP tasks to quickly validate an execution environment before running development workflows.

Can I verify scheduled MCP tasks and container versions from the main chat channel?▼

Yes, you can verify scheduled MCP tasks and container versions from the main chat by calling the mcp__nanoclaw__list_tasks endpoint to enumerate tasks and running basic version commands for tools like Node and Claude CLI.

Does the environment health check require write access to the /workspace paths?▼

No, the environment health check does not require write access; it explicitly requires only read-only shell access to /workspace paths to confirm accessible files and mounts safely.

Why does my workspace status report halt when run outside the main channel?▼

The workspace status report halts when run outside the main channel because it enforces main-channel detection to ensure /workspace/project is properly mounted before attempting to read mounts and container utilities.

Related Skills

Explore More Software Engineering Skills→
jboothomasjboothomas
1

status

Generate a read-only overview of Auggie environment status, mounts, tools, and tasks.

Community
Intermediate
filipexyzfilipexyz
1

claude-code-cli

Develop autonomous agents and orchestrate multi-agent systems with Claude Code CLI.

Community
Advanced
Kevin-Liu-01Kevin-Liu-01
16

agent-browser

Automate browser tasks with persistent sessions and element references.

Community
Intermediate
0-CYBERDYNE-SYSTEMS-00-CYBERDYNE-SYSTEMS-0
3

debug

Diagnose container agent issues in FFT_nano via logs, env vars, mounts, and authentication.

Community
Advanced