claude-remote:verify

Verify Claude Code cloud session health by scanning setup scripts and running shell probes.

1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/fabn/claude-plugins --skill claude-remote-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-remote:verify
Source: https://github.com/fabn/claude-plugins/tree/main/plugins/claude-remote/skills/verify
Command: npx skills add https://github.com/fabn/claude-plugins --skill claude-remote-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The verify skill ensures a Claude Code cloud session is fully set up, with all required runtimes, services, and tools installed and running, before the user proceeds with development tasks, preventing wasted time on broken environments.

Core Features & Use Cases

  • Dynamic tool detection: Parses generated setup and session-start scripts to infer required dependencies for any project stack.
  • Fast health checks: Executes lightweight commands to confirm tool availability and service connectivity.
  • Automatic debugging offer: On failure, proposes chaining into the debug skill for deeper investigation.

Quick Start

Ask Claude to run the verify skill for your repository to ensure all tools and services are available before proceeding.

Frequently Asked Questions about claude-remote:verify

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

FAQPage Schema
How do I verify my Claude Code cloud session is ready for development tasks?

To verify a Claude Code cloud session is ready, run the verify skill to scan setup scripts, detect required runtimes and services, and execute fast health checks confirming tool availability and connectivity before you begin coding.

What does a remote session health check inspect before executing user tasks?

A remote session health check parses generated session-start scripts to infer required dependencies, then runs lightweight shell probes like command -v and service pings to confirm all required tools are installed and operational.

Do I need mise.toml to check if my cloud environment setup is complete?

You do not strictly need mise.toml to check environment setup, but the verify skill uses it optionally alongside .claude/scripts files to accurately infer and validate the required runtimes and services for your project stack.

How do I debug missing dependencies when environment verification fails?

When environment verification fails due to missing dependencies, the verify skill automatically proposes chaining into a dedicated debug skill, enabling deeper investigation of the broken cloud session setup and service connectivity issues.

What is the best way to prevent wasted time on broken cloud development environments?

The best way to prevent wasted time on broken cloud environments is to run a pre-task verification that dynamically detects required tools from setup scripts and executes fast health checks to ensure all services are running.